Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 Mar 2003 08:47:16 -0800
From:      Terry Lambert <tlambert2@mindspring.com>
To:        Garance A Drosihn <drosih@rpi.edu>
Cc:        Bruce Evans <bde@zeta.org.au>, arch@FreeBSD.ORG
Subject:   Re: NEWSYSLOG changes, -Create option for rc.diskless
Message-ID:  <3E6CC194.96EADAA7@mindspring.com>
References:  <20030310000219.N15648-100000@gamplex.bde.org> <p05200f1aba915ef78c61@[128.113.24.47]>

next in thread | previous in thread | raw e-mail | index | archive | help
Garance A Drosihn wrote:
> Well, the idea of -C is to make the "manual creation" process
> something that rc.diskless2 can do trivially and reliably, by
> just asking newsyslog to do it.  If we instead use mtree to
> create the initial files, then I think we'll end up with two
> different databases that will have to have the same information.

Or worse: one that's a subset or superset of the other.

It's much more useful to have a "create" option, like you have.

BTW: mtree would make that *three* databases, not two.  There
are seperate syslog and newsyslog databases.  This is probably
less important, since newsyslog is bound to be a superset or
equivalence set of the syslog file, but they are seperately
maintained, which is annoying (and probably the main reason
people keep talking about integrating newsyslog into syslog).


> However, I have been thinking about the fact that newsyslog.conf
> does often contain rules for files that don't exist.  This patch
> currently adds the -C option, and also adds a C flag for config-file
> entries.  Perhaps the 'C' flag should not mean "always create
> this file if it does not exist".  Perhaps it should mean "create
> this file if it does not exist, and if -C was given".  That way,
> the -C option becomes "create all log files which have a C flag".

Yes.  This makes more sense.  For example, Samba is likely to
start after newsyslog starts, so it should be non-automatic.


> That means our C flag would be a little different than NetBSD's
> C flag, but I think it's a reasonable idea.  That way the config
> file can have a long list of entries, only some of which would be
> automatically created.  What do people think about that idea?

What do the NetBSD folks say?  They may have good reasons for
not behaving that way...

> [the more I think about it, the more I like it, although it means
> more explanation will be needed in the man page]

-- Terry

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3E6CC194.96EADAA7>