From owner-freebsd-current Tue Jun 11 23:06:28 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id XAA01217 for current-outgoing; Tue, 11 Jun 1996 23:06:28 -0700 (PDT) Received: from post.io.org (post.io.org [198.133.36.6]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA01212 for ; Tue, 11 Jun 1996 23:06:26 -0700 (PDT) Received: from zap.io.org (taob@zap.io.org [198.133.36.81]) by post.io.org (8.7.5/8.7.3) with SMTP id CAA12121 for ; Wed, 12 Jun 1996 02:05:05 -0400 (EDT) Date: Wed, 12 Jun 1996 02:06:15 -0400 (EDT) From: Brian Tao To: FREEBSD-CURRENT-L Subject: Re: syslogd can't create /dev/log? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 12 Jun 1996, Brian Tao wrote: > > Here's another odd problem with 2.2-960501-SNAP... I can't seem to > get syslogd to run: Someone shoot me or pass the dunce cap or something... chalk this one up to operator error. :( > syslogd: cannot create /dev/log: Address already in use Of course, syslogd creates the /dev/log socket when it starts up, and destroys it when it shuts down. /dev/log has been hanging around because /dev here is flagged sappnd. kern.securelevel is at 1, so I can't remove sappnd without dropping into single user first. Argh! I didn't think anything had to be deleted out of /dev... wouldn't /dev/log be better off in /var/run or something like that? -- Brian Tao (BT300, taob@io.org, taob@ican.net) Systems and Network Administrator, Internet Canada Corp. "Though this be madness, yet there is method in't"