Bryan Scott wrote:
[2] - svscan will restart any application whose run file exits,
unless it finds
a file called 'down' in which case it will note that but not start
the run file.
This is what `svc -d` creates and `svc -u` deletes. Try typing the
following:
# svc -d /service/PACKAGE
# svstat /service/PACKAGE
So here's one. With 0.31rc2 and 0.31.1, I've tried linking qpsmtpd
into /service/qpsmtpd-fork. It starts and dies immediately (I can
watch with dozens of ps ax | grep fork from the shell). But I can cd
to /var/qmail/qpsmtpd and do a ./run without any problems. Somehow
supervise can't get it started.
I could run it without supervise, but that defeats the purpose of
using daemontools in the first place. :)
Here's my slightly modified run file (basically the same as John's):
#!/bin/sh
exec 2>&1 \
sh -c '
exec \
softlimit -m 25000000 \
perl -T ./qpsmtpd-forkserver \
--port "25" \
--limit-connections "15" \
--user "qmaild"
-d
'
And of course, nothing in log/main/current.
Come to think of it, main doesn't exist yet. Guess multilog isn't
getting started either.
-- Bryan
Might be an environment difference between you ./run and
svscan ./run.
-Bob
