Date: Fri, 16 Oct 1998 16:19:25 -0700 (PDT) From: David Wolfskill <dhw@whistle.com> To: freebsd-current@FreeBSD.ORG Subject: inetd, again, with a slightly different mode of failure Message-ID: <199810162319.QAA09684@pau-amma.whistle.com>
next in thread | raw e-mail | index | archive | help
This is more of a "heads-up" than anything else, especially given the lack of diagnostic detail.... One of my colleagues has a couple of machines running -current: FreeBSD crab.whistle.com 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Tue Sep 22 13:39:07 PDT 1998 root@:/crab/home1/usr/current/freebsd/src/sys/compile/CRAB i386 FreeBSD lax.whistle.com 3.0-CURRENT FreeBSD 3.0-CURRENT #0: Wed Aug 19 16:00:50 PDT 1998 eoldford@lax.whistle.com:/usr/src/sys/compile/LAX i386 He tells me that their level of -currency is the same. (I don't run -current myself, which is one reason this is short on detail). The salient differences of which I am aware are: * crab is utilized significantly more heavily than lax is. Indeed, characterizing lax as "underutilized" would be reasonable. * inetd behaves as might reasonably be expected on lax, while on crab, it occasionally (every 2 - 4 days) seems to forget how to exec certain programs: Oct 16 15:03:01 crab inetd[28051]: cannot execute : No such file or directory Oct 16 15:03:01 crab inetd[26067]: [28051]: exit status 0x4700 Oct 16 15:03:11 crab inetd[28188]: cannot execute : No such file or directory Oct 16 15:03:11 crab inetd[26067]: [28188]: exit status 0x4700 Oct 16 15:03:21 crab inetd[28285]: cannot execute : No such file or directory Oct 16 15:03:21 crab inetd[26067]: [28285]: exit status 0x4700 Oct 16 15:08:20 crab sudo: dhw : TTY=ttyq9 ; PWD=/a/pau-amma/root/pau-amma/home/dhw ; COMMAND=/usr/bin/whoami Oct 16 15:08:46 crab sudo: dhw : TTY=ttyq9 ; PWD=/a/pau-amma/root/pau-amma/home/dhw ; COMMAND=/bin/kill 26067 Oct 16 15:08:46 crab sudo: dhw : TTY=ttyq9 ; PWD=/a/pau-amma/root/pau-amma/home/dhw ; COMMAND=/usr/sbin/inetd The "cannot execute" whines were referring to the following line from /etc/inetd.conf: amanda dgram udp wait operator /usr/local/libexec/amanda/amandad amandad And, as the above excerpt from /var/log/messages shows, I killed & re-started inetd; I then re-ran the "amcheck"... and everything was fine: > amcheck -c Engineering Amanda Backup Client Hosts Check -------------------------------- Client check: 19 hosts checked in 5.685 seconds, 0 problems found. (brought to you by Amanda 2.4.2) (The whines quoted above were from a cron-initiated "amcheck".) Anyway, I mention this in order to let folks know that this kind of symptom is being seen (here, at least), though so far, I've only seen it on this one machine. david -- David Wolfskill UNIX System Administrator dhw@whistle.com voice: (650) 577-7158 pager: (650) 371-4621 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810162319.QAA09684>