RE: access to log directory denied

Cheers Laurent,

That sorted me out.

Damn when said I followed the instructions verbatim - I really meant
verbatim but overlooked the create /packages step for daemontools :(

These tools are incrediable.  As soon as I corrected the mistake, multilog
not only started immediately, but all activity that had taken place while
the log hadn't been functioning was recorded !?

The following now makes sense:
-----
It is generally not a good idea to use shell pipelines:

     #!/bin/sh
     generate-crucial-data | log-crucial-data

If log-crucial-data fails to start up, any data already written to the pipe
by generate-crucial-data will be discarded. To fix this problem, use a
separate log.
-----

Andy.

-----Original Message-----
From: Laurent Bercot [mailto:[email protected]]
Sent: Sunday, 31 August 2003 10:54 PM
To: [email protected]
Subject: Re: access to log directory denied


> [root] /etc/tinydns/log# setuidgid Gdnslog multilog ./main
> setuidgid: fatal: unable to run multilog: access denied

 That message does not mean that multilog (or anything) has trouble
accessing the log directory. It means that setuidgid has trouble
*running multilog* : execve("/path/to/multilog",...) fails with EPERM.

 For some reason, your multilog binary can't be executed as the Gdnslog
user. Check your daemontools installation, and every component of the
physical path to the multilog binary. Also check that you don't have
a "multilog" binary before /command/multilog in your PATH, as (for
instance) the result of a previous daemontools installation via some
broken third-party package.

--
 Ska