On Thu, Oct 04, 2001 at 06:17:13PM +0200, Leif Neland wrote:
>
>
> On Thu, 4 Oct 2001, Jun Kuriyama wrote:
>
> > At Thu, 4 Oct 2001 11:21:19 +0000 (UTC),
> > Bernd Walter wrote:
> > > I run an md based filesystem for /var/run so it is empty after startup.
> > > Does that mean that I also need to take care of creating directories in
> > > it during boot - and maintaining myself on every box.
> > > Or it it the responsibility of the programms to enshure that the
> > > directories they need are created?
> >
> > /var/run/named is created by mtree (/etc/mtree/BSD.var.dist). If you
> > want to use md(4) for /var/run, you should make directory after
> > /var/run creation.
>
> Is it possible to make the md-filesystem automatically make the needed
> subdirectories, when a program wants to create
> /var/run/a/very/deeply/nested/file ?
That wouldn't work. The whole point of /var/run/named is to set the
permissions on the directory such that a non-root user (the 'bind'
user in FreeBSD typically) can write files in the directory. In order
to create the named directory in /var/run, you need root privs. Give
that to the program, and we are back where we started, no point in
using /var/run/named, just use /var/run.
> Or would that just be too ugly, mixing device drivers with high-level file
> operations? Guess so..
Yeah, that too.
It is not that big of a deal to hack this support for named into the
rc scripts. It is a hassle when considering the "correct" way to
handle this to make it extensible to other daemons we may wish to run
in such a manner.
--
Crist J. Clark [EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
