From: prj@po.cwru.edu (Paul Jarc)
Date: Mon, 25 Dec 2006 20:50:31 -0500
"John R. Dunning" <jrd@jrd.org> wrote:
> Also please forgive me if there's a better list to post this to,
http://cr.yp.to/lists.html#log
Yes, tried to sub to that one a few times, but got no response.
Appeared dead.
http://www.skarnet.org/lists/#supervision
Ah. Cool. Didn't know about that one.
> instead of an idling service, I get a string of defunct tcpserver
> processes.
http://homepages.tesco.net./~J.deBoynePollard/FGA/daemontools-service-not-staying-up.html
Ok, thanx, that provides some useful hints. Wonder why google didn't
find it? Grumble.
> I'm trying to figure out where the output from supervise goes;
{ ps -ef || ps aux; } | grep '[r]eadproctitle'
http://cr.yp.to/daemontools/svscanboot.html
http://cr.yp.to/daemontools/readproctitle.html
Huh, that's a good trick. I dug around in those pages earlier, but
didn't catch the bit about what the 400 dots buy you. Guess I was
looking so hard for logging info, I blew right by that part. Thanx!
But you're probably looking for the output from the service, not
supervise itself. That's in /service/*/log/main/current.
http://cr.yp.to/daemontools/svscan.html
http://cr.yp.to/daemontools/multilog.html
Yah. In this case, what I thought I was looking for was enough output
from supervise itself to tell what path it was following, which I
could then use to debug the service's init stuff further. But in
fact, the grep readproctitle trick is telling me what I need to know.
Many thanx!
|