Subject: Re: Renaming /var/run/syslog.socket
To: Klaus Klein <kleink@ira.uka.de>
From: Ignatios Souvatzis <is@jocelyn.rhein.de>
List: tech-userlevel
Date: 03/18/1999 21:16:19
On Thu, Mar 18, 1999 at 09:03:07PM +0100, Ignatios Souvatzis wrote:
> On Thu, Mar 18, 1999 at 08:58:51PM +0100, Klaus Klein wrote:
> > Hubert Feyrer <feyrer@rfhs8012.fh-regensburg.de> writes:
> > 
> > > Some Netscape binaries (and probably others) have /var/run/log
> > > compiled in ...
> > 
> > This particular problem can be generalized into a compatibility issue
> > of far higher severity: executables statically linked against libc
> > still refer to the old pathname of the socket(!).
> 
> This is no problem. Whoever runs -current should read current-users, and has
> been warned.
> 
> I wonder whether pointing people to adding -p /var/run/log would be enough 
> for Huberts concern...

Actually, this could be added to the COMPAT_FREEBSD manual page... do we 
have one?

(or as an example in a comment in rc.conf next to the syslogd parameter list)

(I ask because I suspect that we'd like some linux log device, too, sometimes,
etc., etc. So I suspect single one won't be sufficient for all kinds of
static kernels.)

Or, like I wrote earlier:
> after all, it didn't work before, either.

Regards,
	-is