From owner-freebsd-questions@freebsd.org Fri Feb 2 20:53:11 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id AFCF0EC96E0 for ; Fri, 2 Feb 2018 20:53:11 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from vps349.pairvps.com (vps349.pairvps.com [216.92.231.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 61D907FDCD for ; Fri, 2 Feb 2018 20:53:10 +0000 (UTC) (envelope-from frankfenderbender@council124.org) Received: from [192.168.0.100] (unknown [104.220.39.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by vps349.pairvps.com (Postfix) with ESMTPSA id A11E1A68E8; Fri, 2 Feb 2018 15:53:08 -0500 (EST) Subject: Q about conf'd system's self-checking output Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: C Gray In-Reply-To: <826E6CDC-4B36-46C5-BB2E-9BB620EFCD48@council124.org> Date: Fri, 2 Feb 2018 12:53:07 -0800 Reply-To: C Gray Content-Transfer-Encoding: quoted-printable Message-Id: <0DD02E02-F53B-41BB-B237-7154847FC1B2@council124.org> References: <8F08E935-33A8-4B5F-9057-51FAD51DA97D@council124.org> <20180201121251.95e345cf.freebsd@edvax.de> <09DEB81A-3DC1-4147-9249-0497C89F429B@council124.org> <69060D2E-8ED1-4BDB-8801-2BA29F15C632@council124.org> <826E6CDC-4B36-46C5-BB2E-9BB620EFCD48@council124.org> To: freebsd-questions@freebsd.org X-Mailer: Apple Mail (2.1085) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Feb 2018 20:53:11 -0000 So I have the .conf[ig] files (e.g., = /usr/local/etc/security/pwquality.conf) set so that=20 my mail-less FreeBSD system will allow root to send my mail-gateway = Macmini=20 with reports. I had and fixed these warnings so the detailed reports are already very = useful (for=20 system operations' debugging) and will be even more so (for security) = over time: Warning: Variable $daily_status_security_chksetuid_enable is = deprecated,=20 use $security_status_chksetuid_enable instead. Warning: Variable $daily_status_security_neggrpperm_enable is = deprecated,=20 use $security_status_neggrpperm_enable instead. Warning: Variable $daily_status_security_chkmounts_enable is = deprecated,=20 use $security_status_chkmounts_enable instead. My changes w/r/t my soundbar issue seem to have partially self-resolved = (maybe=20 because a connection re-seated itself better) itself due to = self-diagnoses a, upgrades,=20 or rediscovery attempts therewith... a welcome surprise but one I wish I = better=20 understood and quasi-controlled. Here's "lanserve1 daily security run output" from 3:14am: -------------- Checking login.conf permissions: lanserve1 kernel log messages: +Calibrating TSC clock ... TSC clock: 2500051110 Hz +LAPIC: ipi_wait() us multiplier 60 (r 4100692 tsc 2500051110) +Timecounter "TSC-low" frequency 1250025555 Hz quality 1000 +usbus0: random: harvesting attach, 8 bytes (4 bits) from uhci0 +12Mbps Full Speed USB v1.0 +acpi0: wakeup code va 0xfffffe008b02c000 pa 0x99000 +atkbd: the current kbd controller command byte 0045 +ugen4.1: at usbus4 +uhub0: on = usbus3 +uhub1: on = usbus1 +uhub2: on = usbus4 +ugen2.1: at usbus2 +ugen0.1: at usbus0 +uhub4: on = usbus0 +uhub3: on = usbus2 +uhub0: 2 ports with 2 removable, self powered +random: harvesting attach, 8 bytes (4 bits) from uhub0 +uhub3: 2 ports with 2 removable, self powered +random: harvesting attach, 8 bytes (4 bits) from uhub3 +uhub2: 8 ports with 8 removable, self powered +random: harvesting attach, 8 bytes (4 bits) from uhub2 +ugen4.2: at usbus4 +uhub5 on uhub2 +uhub5: on = usbus4 +uhub5: MTT enabled +uhub5: 4 ports with 4 removable, self powered +ugen4.3: at usbus4 +ugen4.4: at usbus4 +uhub6 on uhub2 +uhub6: on usbus4 +uhub6: 2 ports with 2 removable, self powered +random: harvesting attach, 8 bytes (4 bits) from uhub6 +Trying to mount root from = zfs:tank1/ROOT/12.0-CURRENT-up-20180124_175726 []... +ugen1.2: at usbus1 +ukbd0 on uhub1 +ukbd0: on usbus1 +kbd2 at ukbd0 +kbd2: ukbd0, generic (0), config:0x0, flags:0x3d0000 +random: harvesting attach, 8 bytes (4 bits) from ukbd0 +ums0 on uhub3 +uaudio0 on uhub5 +uaudio0: on usbus4 +uaudio0: Play: 48000 Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms buffer. +uaudio0: Play: 44100 Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms buffer. +uaudio0: Record: 48000 Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms buffer. +uaudio0: Record: 44100 Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms buffer. +uaudio0: No MIDI sequencer. +pcm0: on uaudio0 +pcm0: Mixer "vol" -> "none": child=3D0x00000010 +pcm0: Mixer "pcm": parent=3D"vol" +pcm0: Mixer "line": +random: harvesting attach, 8 bytes (4 bits) from pcm0 +uaudio0: HID volume keys found. +random: harvesting attach, 8 bytes (4 bits) from uaudio0 +ugen4.2: at usbus4 (disconnected) +uhub5: at uhub2, port 6, addr 2 (disconnected) +ugen4.3: at usbus4 (disconnected) +uaudio0: at uhub5, port 3, addr 3 (disconnected) +pcm0: detached +uaudio0: detached +uhub5: detached -------------- Here's the stdout which the process(es) sent to my screen early this = morning=20 appending directly just after my root csh-login-prompt. I imagine that = the=20 stderr and stdout are synchronized time-wise in the above rendition, = however,=20 I have included the screen output [again] in case it may offer a clue or = two.... > [root@lanserve1] ~# ugen4.2: at usbus4 = (disconnected) > uhub5: at uhub2, port 6, addr 2 (disconnected) > ugen4.3: at usbus4 (disconnected) > uaudio0: at uhub5, port 3, addr 3 (disconnected) > pcm0: detached > uaudio0: detached > uhub5: detached > ugen4.2: at usbus4 > uhub5 on uhub2 > uhub5: on usbus4 > uhub5: MTT enabled > uhub5: 4 ports with 4 removable, self powered > random: harvesting attach, 8 bytes (4 bits) from uhub5 > ugen4.3: at usbus4 > uaudio0 on uhub5 > uaudio0: on usbus4 > uaudio0: Play: 48000Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms = buffer. > uaudio0: Play: 44100Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms = buffer. > uaudio0: Record: 48000Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms = buffer. > uaudio0: Record: 44100Hz, 2 ch, 16-bit S-LE PCM format, 2x8ms = buffer. > uaudio0: No MIDI sequencer.=20 > pcm0: on uaudio0 > pcm0: Mixer "vol" -> "none": child=3D0x00000010 > pcm0: Mixer "pcm": parent=3D"vol" > pcm0: Mixer "line": > random: harvesting attach, 8 bytes (4 bits) from pcm0 > uaudio0: HID volume keys found. > random: harvesting attach, 8 bytes (4 bits) from uaudio0 What I am interested in: (1) what actual call launched at 3-ish am? (2) what and where were conditionals met-or-not-met which = 'decided' to vector off to (a) attempt to resolve? (b) attempt to discover new devices? (c) attempt to resolve newly-discovered = device-configuration issues? (d) attempt to resolve previously-discovered but = unresolved device-configuration issues? I'm also getting an old issue again when I tried to vi/vim (view works) = on /usr/local/etc/security/pwquality.conf: Shared object "libSM.so.6" not found, required by "vim". After my base install and attempts to 'make' ports, I ran into a missing = link from /usr/local/lib/ to /lib/ Now I have this 'base'-ic issue.=20 I've found that certain base-ic install tools have dependencies which = when take ]n care of also have missing dependencies. Is there a tool that will walk through all executables to list all = runtime issues at once rather than over a piecemeal call-and-see = scenario? Whene I run whereis, locate, which, and find nothing, I'm stumped as to = how I am supposed to fix the problem I expected to be configured at = install time. That I may have to start the install all over is a problem as well = because re-doing every .conf file setenv, alias, and such -- or backing = that all up -- is near monumental, so if there is a logical tree-top = walkthrough of logs, in the topmost sequence, so that a fix trickles = down and fixes sub-issues, then I can learn quite a bit just fixing the = system rather than hoping it doesn't just reproduce itself. Make sense. = So, a guide to system->module->function calls may be useful if anyone = can recommend an approach.1 My stdout listed above suggests questions based only on my asynchronous = observations at this point, and I need to better understand the calls = that generate the basic setup taking place w/r/t terms, phrases, and = processes like: "harvesting attach"? "detached"? the boot-time and login-time setting of buffer sizes and = locations? the boot-time and login-time mounting of and/or linking to = devices or volumes? if certain things are set at boot time, login time, or at the = time of need by a port or base module? Is there a 'most pertinent' section (in your manuals' travels you'd = recommend? Have you seen that one graphical depiction (as is often well done when = describing the disk-track-sector relationship) which "hit the mark" for = you w/r/t any of my questions? I will read all suggestions and = appreciate you taking the time, making the effort. I apologize for this flurry, and I will definitely share back whatever I = can when an "aha!" opportunity arises.=20 Thanks. best wishes, chris 'smart' devices are con[niving]s and 'dumb' users are man-made