[PLUG] Unusual Process Message

[Piet van Weel]

Rich...

My google must be different from yours... 
(search "multilog: fatal:" -qmail) :)

http://article.gmane.org/gmane.network.djbdns/7372

-- QUOTE FROM LINK --
> On Monday, Sep 15, 2003, at 08:42 America/Los_Angeles, Chris wrote:
>
> > ' ps wwwwp 193 '
> >
> >   PID TTY      STAT   TIME COMMAND
> >   193 ?        S      0:01 readproctitle service errors: ...ccess
> > denied?multilog: fatal: unable to lock directory ./main: access
> > denied?multilog: fatal: ... etc etc
>
> Find the log directory your  .../tinydns/log/run file is specifying 
> and make sure it's owned by the user the run file is using (as Paul said).

That should clear it up... :) The whole thread on the above link was rather
an interesting read. Just click on the thread name and away you go!!

Cheers

Piet van Weel


>> -----Original Message-----
>> From: plug-bounces at lists.pdxlinux.org [mailto:plug-
>> bounces at lists.pdxlinux.org] On Behalf Of Rich Shepard
>> Sent: Saturday, January 01, 2005 5:36 PM
>> To: General Linux discussion and assistance
>> Subject: Re: [PLUG] Unusual Process Message
>> 
>> On Sat, 1 Jan 2005, Rich Shepard wrote:
>> 
>> >  Time to google and find someone who can help with a daemontools
>> problem.
>> > Dan won't, I know.
>> 
>>    Oh, boy! I'm not alone in finding this multilog error, but virtually
>> every
>> reference google turns up is with qmail. That's not the MTA here. I did,
>> however, learn to find the details, here they are:
>> 
>> [root at salmo]# cat /proc/1384/cmdline
>> readproctitleserviceerrors:...ccess denied
>> multilog: fatal: unable to lock directory ./main: access denied
>> multilog: fatal: unable to lock directory ./main: access denied
>> multilog: fatal: unable to lock directory ./main: access denied
>> multilog: fatal: unable to lock directory ./main: access denied
>> multilog: fatal: unable to lock directory ./main: access denied
>> multilog: fatal: unable to lock directory ./main: access denied
>> 
>>    Can anyone suggest where I look to learn what this means? Where is
>> that
>> main directory located? How do I fix this? It's obviously not fatal, but
>> it's also not clean. A google search on the phrase, "unable to lock
>> directory ./main" returns 7 hits; all qmail related.
>> 
>>    Does this mean that daemontools should be removed? In my naivety it
>> struck
>> me as a useful inet service controller.
>> 
>> Thanks,
>> 
>> Rich
>> 
>> --
>> Dr. Richard B. Shepard, President
>> Applied Ecosystem Services, Inc. (TM)
>> <http://www.appl-ecosys.com>   Voice: 503-667-4517   Fax: 503-667-8863
>> _______________________________________________
>> PLUG mailing list
>> PLUG at lists.pdxlinux.org
>> http://lists.pdxlinux.org/mailman/listinfo/plug