Re: svscan help
/usr/local/sbin:/usr/sbin:/sbin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lo
cal/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bi
n:/root/bin
- Original Message -
From: List Monkey [EMAIL PROTECTED]
To: Kevin Roberts [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, June 27, 2001 10:53 PM
Subject: Re: svscan help
What does
echo $PATH
say?
On Wed, 27 Jun 2001, Kevin Roberts wrote:
Does any know how to fix this error starting svscan?
env: invalid option - - P
Try `env --help' for more information;
#!/bin/sh
PATH=$PATH:/usr/local/bin:/var/qmail/bin
case $1 in
start)
echo -n Starting djb services: svscan
cd /service
env - PATH=$PATH svscan
echo $! /var/run/svscan.pid
echo .
;;
stop)
echo -n Stopping djb services: svscan
kill `cat /var/run/svscan.pid`
echo -n services
svc -dx /service/*
echo -n logging
svc -dx /service/*/log
echo .
;;
restart)
$0 stop
$0 start
;;
*)
echo 'Usage: svscan {start|stop|restart}'
exit 1
esac
exit 0
Re: svscan help
Ummmthat looks legitimate.
So much for my quick answer ;-)
I cannot see anything wrong. --Pete
/usr/local/sbin:/usr/sbin:/sbin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lo
cal/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bi
n:/root/bin
- Original Message -
From: List Monkey [EMAIL PROTECTED]
To: Kevin Roberts [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Wednesday, June 27, 2001 10:53 PM
Subject: Re: svscan help
What does
echo $PATH
say?
On Wed, 27 Jun 2001, Kevin Roberts wrote:
Does any know how to fix this error starting svscan?
env: invalid option - - P
Try `env --help' for more information;
#!/bin/sh
PATH=$PATH:/usr/local/bin:/var/qmail/bin
case $1 in
start)
echo -n Starting djb services: svscan
cd /service
env - PATH=$PATH svscan
echo $! /var/run/svscan.pid
echo .
;;
stop)
echo -n Stopping djb services: svscan
kill `cat /var/run/svscan.pid`
echo -n services
svc -dx /service/*
echo -n logging
svc -dx /service/*/log
echo .
;;
restart)
$0 stop
$0 start
;;
*)
echo 'Usage: svscan {start|stop|restart}'
exit 1
esac
exit 0
Re: svscan help
On Wed, Jun 27, 2001 at 11:25:55PM -0700, Kevin Roberts wrote: /usr/local/sbin:/usr/sbin:/sbin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lo cal/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bi n:/root/bin try: # sh -x /etc/init.d/svscan start and paste the output here. --Adam
Re: svscan help
Hi, env: invalid option - - P ... env - PATH=$PATH svscan Is there really a blank between the - and the P of PATH? My env ignores any options behind the first -, e.g. $ env - -P PATH=/bin ls env: -P: No such file or directory $ env - PATH=/bin -P ls env: -P: No such file or directory and the only way to get the above message is by having $ env -PATH=/bin ls env: invalid option -- P Try `env --help' for more information. claudio -- Claudio Nieder, Kanalweg 1, CH-8610 Uster, Tel +41 79 357 6743 yahoo messenger: claudionieder aim: claudionieder icq:42315212 mailto:[EMAIL PROTECTED]http://www.claudio.ch
Re: svscan help
+ PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/kerberos/sbin:/usr/kerberos/bin:/u sr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X 11R6/bin:/root/bin:/usr/local/bin:/var/qmail/bin + echo -n 'Starting djb services: svscan' Starting djb services: svscan+ cd /service + env - PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/kerberos/sbin:/usr/kerberos/bin:/u sr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin: /usr/X11R6/bin:/root/bin:/usr/local/bin:/var/qmail/bin svscan + echo 1546 + echo . . + exit 0 [root@salem bin]# env: invalid option -- P Try `env --help' for more information. env: invalid option -- P Try `env --help' for more information. env: invalid option -- P Try `env --help' for more information. env: invalid option -- P Try `env --help' for more information. env: invalid option -- P Try `env --help' for more information. env: invalid option -- P Try `env --help' for more information. env: invalid option -- P - Original Message - From: Adam McKenna [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Wednesday, June 27, 2001 11:55 PM Subject: Re: svscan help On Wed, Jun 27, 2001 at 11:25:55PM -0700, Kevin Roberts wrote: /usr/local/sbin:/usr/sbin:/sbin:/usr/kerberos/sbin:/usr/kerberos/bin:/usr/lo cal/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bi n:/root/bin try: # sh -x /etc/init.d/svscan start and paste the output here. --Adam
Re: svscan help
Redhat 7.1 Kevin - Original Message - From: Adam McKenna [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, June 28, 2001 3:07 PM Subject: Re: svscan help On Thu, Jun 28, 2001 at 02:32:53PM -0700, Lists Servers Email wrote: + PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/kerberos/sbin:/usr/kerberos/bin:/u sr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/X 11R6/bin:/root/bin:/usr/local/bin:/var/qmail/bin + echo -n 'Starting djb services: svscan' Starting djb services: svscan+ cd /service + env - PATH=/usr/local/sbin:/usr/sbin:/sbin:/usr/kerberos/sbin:/usr/kerberos/bin:/u sr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin: /usr/X11R6/bin:/root/bin:/usr/local/bin:/var/qmail/bin svscan + echo 1546 + echo . . + exit 0 [root@salem bin]# env: invalid option -- P Try `env --help' for more information. env: invalid option -- P Try `env --help' for more information. env: invalid option -- P Try `env --help' for more information. env: invalid option -- P Try `env --help' for more information. env: invalid option -- P Try `env --help' for more information. env: invalid option -- P Try `env --help' for more information. env: invalid option -- P Weird. What OS is this running on? Try getting a new copy of the script at http://flounder.net/qmail/svscan-init --Adam
svscan help
Does any know how to fix this error starting
svscan?
env: invalid option - - P
Try `env --help' for more information;
#!/bin/sh
PATH=$PATH:/usr/local/bin:/var/qmail/bincase
"$1" in
start) echo -n "Starting djb
services: svscan" cd
/service env - PATH="$PATH" svscan
echo $!
/var/run/svscan.pid echo
"." ;;
stop) echo -n "Stopping djb
services: svscan" kill `cat
/var/run/svscan.pid` echo -n
"services " svc -dx
/service/* echo -n "
logging" svc -dx
/service/*/log echo
"." ;;
restart) $0
stop $0
start ;;
*) echo 'Usage: svscan
{start|stop|restart}' exit
1esacexit 0
Re: svscan help
What does
echo $PATH
say?
On Wed, 27 Jun 2001, Kevin Roberts wrote:
Does any know how to fix this error starting svscan?
env: invalid option - - P
Try `env --help' for more information;
#!/bin/sh
PATH=$PATH:/usr/local/bin:/var/qmail/bin
case $1 in
start)
echo -n Starting djb services: svscan
cd /service
env - PATH=$PATH svscan
echo $! /var/run/svscan.pid
echo .
;;
stop)
echo -n Stopping djb services: svscan
kill `cat /var/run/svscan.pid`
echo -n services
svc -dx /service/*
echo -n logging
svc -dx /service/*/log
echo .
;;
restart)
$0 stop
$0 start
;;
*)
echo 'Usage: svscan {start|stop|restart}'
exit 1
esac
exit 0
Re: LWQ/svscan question
Dave can probably give a more detailed answer to this, but you don't symbolicly link the directories into /service until you're ready to run them. And even then, svscan won't start them until you do a svc -u (or -o) /service/servicename . Everything I've read about svscan says that once you create the symbolic link in /service that the new service will start within 5 seconds. I don't use svscan to run Qmail (mainly due to a newbie mess up when I initially installed Qmail and don't want to break what *IS* working fine for my needs) but I *DO* use svscan for djbdns and in every instance where I have installed djbdns and created the symbolic link in /service, dnscache has always started on it's own. FWIW Richard
LWQ/svscan question
I looked at the new version of Life with qmail for the first time today, so forgive me if this is a little late. I didn't see anything in the archive to suggest it had already been talked aobut. Since the new LWQ sets up svscan to run independently of the qmail control script, would it not be a wise idea to include a down file in each supervise directory, so that qmail and any other services would not start up when svscan is run? That way you would have greater control over when and in what order the supervised services began during boot-up. ---Kris Kelley
Re: LWQ/svscan question
Charles Cazabon [EMAIL PROTECTED] wrote: Dave can probably give a more detailed answer to this, but you don't symbolicly link the directories into /service until you're ready to run them. That's not how LWQ's qmailctl works. The links in /service are permanent. And even then, svscan won't start them until you do a svc -u (or -o) /service/servicename . Sure it will, unless there's a down file. In short, stop worrying, I think :). Definitely. -Dave
Re: LWQ/svscan question
Dave Sill [EMAIL PROTECTED] wrote: And even then, svscan won't start them until you do a svc -u (or -o) /service/servicename . Sure it will, unless there's a down file. Of course, I received several corrections immediately after sending this. Mea culpa. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: LWQ/svscan question
I wrote: Since the new LWQ sets up svscan to run independently of the qmail control script, would it not be a wise idea to include a down file in each supervise directory, so that qmail and any other services would not start up when svscan is run? Dave Sill replied: That was my original goal, but I soon discovered that the qmail init script was being run before svscan was started, so qmail wasn't starting when the system was rebooted. I opted to remove the down files and let svscan start them ASAP, which is safe since the init scripts have alread been run by that point. I think I'd prefer to have svscan running before any of the relevant init scripts were executed, because I plan on supervise-ing other programs besides qmail. I like the idea of having them all in one place, overseen by one svscan process (my current set-up calls svscan three times), but would like more control over what order the services are started. So what I'll probably do is call svscan from its own start-up script that runs before the scripts of qmail and the other programs, and sprinkle down files where appropriate. It doesn't look like it, but would I be at the risk of breaking anything else in the LWQ scheme of things if I do it this way? Charles Cazabon wrote: Mea culpa; I claim brain fade. Been there, done that, can't remember what happened. ---Kris Kelley
Ensuring only one svscan per directory
We ran into a misconfiguration on one machine where svscan had been added by one person to rc.sysinit and inittab by another, so two copies of svscan were being started. I realise that this is a misconfiguration, but wouldn't it be possible for svscan to add a 'lock' file to the services directory so it only starts once? I'm not sure stale locks would be easy to detect since svscan is usually a very low-numbered PID. -- Michael T. Babcock CTO, FibreSpeed
Re: Ensuring only one svscan per directory
Michael T\. Babcock [EMAIL PROTECTED] writes: I realise that this is a misconfiguration, but wouldn't it be possible for svscan to add a 'lock' file to the services directory so it only starts once? setlock -n /path/to/lockfile svscan /service URL:http://cr.yp.to/daemontools/setlock.html paul
Re: Ensuring only one svscan per directory
+-- On Jun 4, Paul Jarc said: Michael T\. Babcock [EMAIL PROTECTED] writes: I realise that this is a misconfiguration, but wouldn't it be possible for svscan to add a 'lock' file to the services directory so it only starts once? setlock -n /path/to/lockfile svscan /service URL:http://cr.yp.to/daemontools/setlock.html Since that's not built in to svscan, and it's not documented as the standard way to run svscan, it probably wouldn't prevent the human error that caused Michael's problem.
Re: Ensuring only one svscan per directory
Michael T. Babcock([EMAIL PROTECTED])@2001.06.04 11:11:59 +: We ran into a misconfiguration on one machine where svscan had been added by one person to rc.sysinit and inittab by another, so two copies of svscan were being started. I realise that this is a misconfiguration, but wouldn't it be possible for svscan to add a 'lock' file to the services directory so it only starts once? I'm not sure stale locks would be easy to detect since svscan is usually a very low-numbered PID. hmm, the supervise implementation does locking, so at least the impact on the box should not be really noticeable (in fact, you will see errors from the supervises starteted from svscan). adding locking to svscan would be more of a cosmetic change i think. /k -- Captain Hook died of jock itch. KR433/KR11-RIPE -- WebMonster Community Founder -- nGENn GmbH Senior Techie http://www.webmonster.de/ -- ftp://ftp.webmonster.de/ -- http://www.ngenn.net/ karstenrohrbach.de -- alphangenn.net -- alphascene.org -- [EMAIL PROTECTED] GnuPG 0x2964BF46 2001-03-15 42F9 9FFF 50D4 2F38 DBEE DF22 3340 4F4E 2964 BF46 PGP signature
Re: svscan on linux
From: Subba Rao [EMAIL PROTECTED] I have followed the instructions on DJB's site to install and start svscan. On Linux and other SVR4-based systems with /etc/inittab, add SV:123456:respawn :env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null /dev/console 2/dev/console to the end of /etc/inittab, and type kill -HUP 1. the command init q (without the quotes) will reload inittab. I never did get the new and improved instructions to work, so I went back to the original instructions that always worked the first try. echo Starting svscan in /service env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin csh -cf 'svscan /service ' Add the above two lines to rc.local and reboot. Hope that helped. Rick Up
Re: svscan on linux
On 0, Mark Delany [EMAIL PROTECTED] wrote: On Wed, Apr 25, 2001 at 08:32:12PM +, Subba Rao wrote: I have followed the instructions on DJB's site to install and start svscan. On Linux and other SVR4-based systems with /etc/inittab, add SV:123456:respawn :env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null /dev/console 2/dev/console to the end of /etc/inittab, and type kill -HUP 1. I am not seeing the svscan process running. Am I missing any step here? 1.Is the inittab entry all on one line? Show us. 2.What was printed on the console after the kill? 3.Does /service exist? Show us with ls. 4.Is svscan installed ok and executable? Show us with ls. The / directory has: drwxr-xr-x 2 root root 4096 Apr 25 18:20 service/ The svscan binary is installed and executable: -rwxr-xr-x 1 root bin 13532 Aug 15 2000 /usr/local/bin/svscan* In inittab, I tried various combinations after 'svscan /service' and the run level too: SV:123456:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null 2/dev/console SV:2345:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null 2/dev/console Each time I made changes to inittab, I did run: # kill -HUP 1 or # init q or # telinit q The run level on this system is 4. The 'ps waux | grep svscan' will not list svscan. The only command that seems to work is: # csh -cf 'svscan /service ' I would definitely prefer to start svscan from /etc/inittab rather than via the startup scripts. I did reboot the system after making changes to inittab and that did not start svscan. -- Subba Rao [EMAIL PROTECTED] http://members.home.net/subba9/ GPG public key ID 27FC9217
Re: svscan on linux
Okidoki, so more precise instructions: show us the output of all the commands below. On Thu, Apr 26, 2001 at 08:17:27AM +, Subba Rao wrote: 1. Is the inittab entry all on one line? Show us. Do grep ^SV /etc/inittab 3. Does /service exist? Show us with ls. Do ls -ld /service 4. Is svscan installed ok and executable? Show us with ls. Do ls -l /usr/local/bin/svscan SV:2345:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null 2/dev/console Try: SV:2345:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service insert a newline at the end. Then run init 1 init 4 and then do ps auxww|grep svsc Mate
Re: svscan on linux
On 0, Subba Rao [EMAIL PROTECTED] wrote: On Wed, Apr 25, 2001 at 08:32:12PM +, Subba Rao wrote: I have followed the instructions on DJB's site to install and start svscan. On Linux and other SVR4-based systems with /etc/inittab, add SV:123456:respawn :env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null /dev/console 2/dev/console to the end of /etc/inittab, and type kill -HUP 1. I am not seeing the svscan process running. Am I missing any step here? The / directory has: drwxr-xr-x 2 root root 4096 Apr 25 18:20 service/ The svscan binary is installed and executable: -rwxr-xr-x 1 root bin 13532 Aug 15 2000 /usr/local/bin/svscan* In inittab, I tried various combinations after 'svscan /service' and the run level too: SV:123456:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null 2/dev/console SV:2345:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null 2/dev/console Each time I made changes to inittab, I did run: # kill -HUP 1 or # init q or # telinit q The run level on this system is 4. The 'ps waux | grep svscan' will not list svscan. This finally worked, # init u The ps command lists the svscan process. After rebooting, I have to run init u manually as root user. Now, the extension question is, how can you set init to start with the u option? Or should I make it the last call in the init scripts? -- Subba Rao [EMAIL PROTECTED] http://members.home.net/subba9/ GPG public key ID 27FC9217
svscan on linux
I have followed the instructions on DJB's site to install and start svscan. On Linux and other SVR4-based systems with /etc/inittab, add SV:123456:respawn :env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null /dev/console 2/dev/console to the end of /etc/inittab, and type kill -HUP 1. I am not seeing the svscan process running. Am I missing any step here? TIA. -- Subba Rao [EMAIL PROTECTED] http://members.home.net/subba9/ GPG public key ID 27FC9217
Re: svscan on linux
On Wed, Apr 25, 2001 at 08:32:12PM +, Subba Rao wrote: I have followed the instructions on DJB's site to install and start svscan. On Linux and other SVR4-based systems with /etc/inittab, add SV:123456:respawn :env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null /dev/console 2/dev/console to the end of /etc/inittab, and type kill -HUP 1. I am not seeing the svscan process running. Am I missing any step here? 1. Is the inittab entry all on one line? Show us. 2. What was printed on the console after the kill? 3. Does /service exist? Show us with ls. 4. Is svscan installed ok and executable? Show us with ls. Regards.
Re: svscan on linux
-BEGIN PGP SIGNED MESSAGE- Subba Rao wrote: I have followed the instructions on DJB's site to install and start svscan. On Linux and other SVR4-based systems with /etc/inittab, add SV:123456:respawn :env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null /dev/console 2/dev/console to the end of /etc/inittab, and type kill -HUP 1. I am not seeing the svscan process running. Am I missing any step here? Speculating, since you didn't provide much detail: I discovered something bizarre when I installed daemontools on Red Hat 7.1 ... init didn't like the length of the process field for the entry. (Watch the console during boot or init changes to see this). I shortened it by dropping some unnecessary path information, and that made it happy. I'd never seen that before. - -d - -- David Talkington http://www.spotnet.org PGP key: http://www.prairienet.org/~dtalk/dt000823.asc -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 Comment: Made with pgp4pine 1.75-6 iQEVAwUBOud5r71ZYOtSwT+tAQGJNQgAvVXTN3tGS6G+5RnYeluvyGLqBvyE1RxF rpyz4jEVDXqm5+PTs/xpDD0oyd3JFY9bAosdMk/ct5SDQOdjkk7vMPYhXbo1dsAy z0BOhzwljV8BIhTeOIS8e5nKcgnydhSnwJLh0LgCvJ69x36l1emDkdVREdB7L9CC aAIJYKruiby4R3Dvj/u670ZDecI+WGCdmk8UqhhEz5JLTVnF7C+8DgffMqhHQ6FP g6gk7lGvjuPgSG5twg4KZWyH2D/7bTxloz4YCHVZcUSC/4kNTlxM2kbWCCR3hnfH exPlQeLzWbnjqHd5NiAoydRq7HSPpZSHrBYfPJl/0YBc/tuO2UAPPQ== =y0T+ -END PGP SIGNATURE-
Re: svscan on linux
On Wed, Apr 25, 2001 at 08:28:10PM -0500, David Talkington wrote: I discovered something bizarre when I installed daemontools on Red Hat 7.1 ... init didn't like the length of the process field for the entry. (Watch the console during boot or init changes to see this). I From init.c, in read_inittab(), there is if (process strlen(process) 127) strcpy(err, process field too long); This is of course undocumented---but at least there is no silent truncation. The process field Dan recommends has 132 characters in it... But the console stuff is not needed under Linux; just put SV:123456:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service in inittab. Mate
Re: svscan on linux
On Wed, Apr 25, 2001 at 10:12:56PM -0500, Mate Wierdl wrote: On Wed, Apr 25, 2001 at 08:28:10PM -0500, David Talkington wrote: I discovered something bizarre when I installed daemontools on Red Hat 7.1 ... init didn't like the length of the process field for the entry. (Watch the console during boot or init changes to see this). I From init.c, in read_inittab(), there is if (process strlen(process) 127) strcpy(err, process field too long); This is of course undocumented---but at least there is no silent truncation. The process field Dan recommends has 132 characters in it... In fact, it may be that just my lynx that lengthens the process field at http://cr.yp.to/daemontools/svscan.html. The only other thing I see is process = get_part(NULL, '\n'); which I think means that if you put the SV line at the end of inittab without a newline, the process field is not read properly (trying to read past EOF?). Mate
Re: svscan on linux
The only other thing I see is process = get_part(NULL, '\n'); which I think means that if you put the SV line at the end of inittab without a newline, the process field is not read properly (trying to read past EOF?). Mate I have been bitten by this once before, I do not remember where. So now my paranoid Unix thinking is to put a LF or three at the end of every (config) file. How long will it take untill ALL the ancient unix tools have been rewritten with complete painfully correct robustness by the likes of DJB? I, for one, have been intrigued by a suggestion to replace init completely with a shell script (sash?) that invokes svscan to keep certain things running...but I have not had the time to tinker with it. --Pete
Re: svscan and heavy load
Aleksander Olsen [EMAIL PROTECTED] wrote: Starting qmail with 'qmail start' and get the echo 'Starting qmail: svscan.' The first time i started qmail like this, i wasnt aware of the problem. The load was 0.00 and after 5 mins with qmail and svscan running, the load was closing up to 10.00. - Why ? Post the contents of your start script (apparently called "qmail") and a relevant portion of what shows up in the logs after you try to start it. Only then can we help you. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
svscan and heavy load
Hi Starting qmail with 'qmail start' and get the echo 'Starting qmail: svscan.' The first time i started qmail like this, i wasnt aware of the problem. The load was 0.00 and after 5 mins with qmail and svscan running, the load was closing up to 10.00. - Why ? This is a p133 and 64mb ram. Anyone? Thanks! ;) Aleksander
Re: qmail-rspawn not starting under svscan
Golden_Eternity writes: Now, I can get qmail to accept mail from other systems when I start it under svscan, but qmail-rspawn doesn't start. Is it only qmail-rspawn that doesn't start? What about other qmail daemons, that is, qmail-send, qmail-clean, and qmail-lspawn? None of them can be found in the ps output. (There is ``supervise qmail-send'', but it's supervise, not qmail-send.) What's logged in /var/log/qmail/qmail-send/current? What happens if you do ``svc -u /service/qmail-send''? What happens if you do ``svstat /service/qmail-send''? -- Tetsu Ushijima
qmail-rspawn not starting under svscan
Well, I had qmail running fine when I was starting it using a SysV style init script (out of the old qmail howto), but when I tried to install djbdns, I ran into some trouble so I figured I'd try out svscan /service. Now, I can get qmail to accept mail from other systems when I start it under svscan, but qmail-rspawn doesn't start. I shut that down stumbled around a bit and got it partially started back up under the SysV init script but it wouldn't accept connections (tcpserver wouldn't start)... it did send the queued mail, though. ;) To get this message out, qmail started under svscan and then I ran the SysV init script on top of that... I did get qmail-rspawn started that way, but its a big ugly mess... supervise is starting qmail-send and qmail-smtpd (and the two loggers) fine. I see two copies of multilog running and one copy of tcpserver... Well, here's the relevant ps -auxw output. root 18561 6.6 1.3 1088 320 ?S02:30 12:26 supervise qmail-send root 18562 0.0 1.3 1088 320 ?S02:30 0:00 supervise log root 18563 0.0 1.3 1088 320 ?S02:30 0:00 supervise qmail-smtpd qmaill 18565 0.0 1.3 1100 312 ?S02:30 0:00 /usr/local/bin/multilog t s250 /var/log/qmail/qmail-send qmaild 18567 0.0 2.1 1208 484 ?S02:30 0:00 /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb -u 503 -g 502 0 s root 18568 0.0 1.3 1088 320 ?S02:30 0:00 supervise log qmaill 18571 0.0 1.3 1100 316 ?S02:30 0:00 /usr/local/bin/multilog t s250 /var/log/qmail/qmail-smtpd I don't even know where to begin looking for an answer... I'm using the run scripts from the new qmail howto... - svscan style - [root@roto-router qmail-send]# cat run !/bin/sh exec /var/qmail/rc [root@roto-router qmail-smtpd]# cat run #!/bin/sh QMAILDUID=`id -u qmaild` NOFILESGID=`id -g qmaild` exec /usr/local/bin/softlimit -m 200 \ /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb \ -u $QMAILDUID -g $NOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd 21 - SysV style - csh -cf '/var/qmail/rc ' supervise /var/lock/qmail-smtpd tcpserver -v -x/etc/tcp.smtp.cdb -u$USER ID -g$GROUPID 0 25 \ rblsmtpd qmail-smtpd 21 | setuser qmaill accustamp | \ setuser qmaill cyclog -s500 -n5 /var/log/qmail/qmail-smtpd The differences seem to be rblsmtpd, accustamp, and cyclog... But none of those seem to make any sense as the source of my problem... Any suggestions?
[OT?] svscan restart - how???
I know this may be off-topic, but since most of the people on this list seem to be familiar with svscan, I thought I might try. I use svscan to start all of my qmail daemons and can't figure out how to restart it safely on my FreeBSD 4.0 sys. Thus far, I have tried to kill, HUP, etc. for the service itself, with disastrous results... What I am trying to do is simply restart all of the qmail daemons. Perhaps I'm going about it the wrong way. pop3d, smtp and the qmail rc scripts are all started with links to /service. Startup is going very smoothly, same with shutdown - but no restart. Can someone help? Thanks, SF
Re: [OT?] svscan restart - how???
Svscan should not be stopped. It just enter the directories and spawns supervise processes. Supervise should be used to start/stop services. You can use the svc command to restart your qmail system. man svc might help you. []s Davi On Tuesday 13 February 2001 21:11, SNFettig Listserv wrote: I know this may be off-topic, but since most of the people on this list seem to be familiar with svscan, I thought I might try. I use svscan to start all of my qmail daemons and can't figure out how to restart it safely on my FreeBSD 4.0 sys. Thus far, I have tried to kill, HUP, etc. for the service itself, with disastrous results... What I am trying to do is simply restart all of the qmail daemons. Perhaps I'm going about it the wrong way. pop3d, smtp and the qmail rc scripts are all started with links to /service. Startup is going very smoothly, same with shutdown - but no restart. Can someone help? Thanks, SF
Re: [OT?] svscan restart - how???
On Tue, 13 Feb 2001, SNFettig Listserv wrote: I know this may be off-topic, but since most of the people on this list seem to be familiar with svscan, I thought I might try. I use svscan to start all of my qmail daemons and can't figure out how to restart it safely on my FreeBSD 4.0 sys. Thus far, I have tried to kill, HUP, etc. for the service itself, with disastrous results... What I am trying to do is simply restart all of the qmail daemons. Perhaps I'm going about it the wrong way. pop3d, smtp and the qmail rc scripts are all started with links to /service. Startup is going very smoothly, same with shutdown - but no restart. don't restart svscan, do something like the following svc -d /service/qmail-send /service/qmtpd /service/smtpd \ /service/qmail-send/log /service/qmtpd/log /service/smtpd/log wait for the processes to die off and then do something like svc -u /service/qmail-send /service/qmtpd /service/smtpd \ /service/qmail-send/log /service/qmtpd/log /service/smtpd/log [I dont run a pop3d, but someone with a clue should be able to figure out the additional magic] RjL == You know that. I know that. But when || Austin, Texas you talk to a monkey you have to || Email: [EMAIL PROTECTED] grunt and wave your arms -ck ||
svscan does not recurse into subdirectories
Good evening, I've got a maybe stupid and simple question, but doc-reading does not really take me further anymore. :( I set up daemontools, ucspi-tcp and qmail according to the docs and LWQ and created a directory /services/qmail with three subdirectories, qmail-send, qmail-smtpd and qmail-pop3d. They contain the "run"-scripts to start these services and a "log"-subdir, which itself contains the recommended "run"-scripts for logging from LWQ. When starting svscan in /services/qmail, the mentioned services are started correctly and supervise does not report any errors. Everything is working, except that the log-services are not started. An svstat * */log shows: qmail-pop3d: up (pid 9147) 317 seconds qmail-send: up (pid 9148) 317 seconds qmail-smtpd: up (pid 9149) 317 seconds qmail-pop3d/log: unable to open supervise/ok: file does not exist qmail-send/log: unable to open supervise/ok: file does not exist qmail-smtpd/log: unable to open supervise/ok: file does not exist Permissions for the subdirectories are set correctly. My system is Debian GNU/Linux with a 2.4 kernel. From the docs of svscan I learned, that "svscan starts a pair of supervise processes, one for sub, one for sub/log, with a pipe between them.", but this effect does not take place, and I really don't know, what the problem might be. Any help is appreciated, thanks for your advice in advance, yours, Mario -- .~.Mario Thaten ([EMAIL PROTECTED]) /V\ /( )\ "There are just 2 rules in life: ^ ^ Always be yourself, but never mind to change."
Re: svscan does not recurse into subdirectories
Thus said Mario Thaten on Sun, 11 Feb 2001 01:44:25 +0100: From the docs of svscan I learned, that "svscan starts a pair of supervise processes, one for sub, one for sub/log, with a pipe between them.", but this effect does not take place, and I really don't know, what the problem might be. You must have missed the part about the stick bit eh? svscan will only supervise the log directory if the it is set on the parent directory. chmod +t /supervise/qmail/* Andy -- [---[system uptime]] 6:06pm up 100 days, 20:27, 7 users, load average: 1.17, 1.12, 1.09
How do you start smtp with svscan please
Roger Arnold wrote: I am a newbie so sorry if I am on the wrong list. What I need to know is how to enable smtp with svscan so that it is enabled after every reboot please Thanks in advance Roger
Re: How do you start smtp with svscan please
What I need to know is how to enable smtp with svscan so that it is enabled after every reboot please Install the daemontools package (http://cr.yp.to/daemontools.html) and read the FAQ entry "How do I run qmail-smtpd under tcpserver?" Regards, Frank
Re: How does SVSCAN work ?
Andy Bradford wrote: Thus said "dennis" on Mon, 05 Feb 2001 13:23:55 +1100: I must be as thick as two short planks but for the file of me I can't get my head around how SVSCAN works. Can someone please enlighten me, PLEASE !! svscan ``scans'' the directory that you give it for other directories. For each directory it finds, it spawns a supervise process that monitors the service defined in the run file found in that directory. If a supervise process (which monitors a service) dies for some odd reason it will restart another supervise process on that directory to keep the service running. That's all it does, plain and simple. Hi, I tried to use svscan for something other than qmail and couldn't get it to work. The process in question, slapd, wasn't producing specific log files, and svscan refused to start. It works just fine for me with qmail when I specify the log files for qmail. Mike
How does SVSCAN work ?
I must be as thick as two short planks but for the file of me I can't get my head around how SVSCAN works. Can someone please enlighten me, PLEASE !! Yes, I have read, what little there is of the docs. help !!
Re: How does SVSCAN work ?
Thus said "dennis" on Mon, 05 Feb 2001 13:23:55 +1100: I must be as thick as two short planks but for the file of me I can't get my head around how SVSCAN works. Can someone please enlighten me, PLEASE !! svscan ``scans'' the directory that you give it for other directories. For each directory it finds, it spawns a supervise process that monitors the service defined in the run file found in that directory. If a supervise process (which monitors a service) dies for some odd reason it will restart another supervise process on that directory to keep the service running. That's all it does, plain and simple. Andy -- [---[system uptime]] 10:10pm up 95 days, 31 min, 6 users, load average: 1.09, 1.15, 1.13
Qmail setup, svscan glitch
All- I'm new to Qmail and installing it for the first time. I have a 'server' install RedHat 6.2 linux box. I have read everything I could find but have run into a glitch. I am installing exactly like the "Life with qmail" document says to and am at step 2.7. I went to test the build by following the instructions at http://cr.yp.to/daemontools/svscan.html#boot . Well, I added the line it said to to the end of my initab which looks like this: # # inittab This file describes how the INIT process should set up # the system in a certain run-level. # # Author: Miquel van Smoorenburg, [EMAIL PROTECTED] # Modified for RHS Linux by Marc Ewing and Donnie Barnes # # Default runlevel. The runlevels used by RHS are: # 0 - halt (Do NOT set initdefault to this) # 1 - Single user mode # 2 - Multiuser, without NFS (The same as 3, if you do not have networking) # 3 - Full multiuser mode # 4 - unused # 5 - X11 # 6 - reboot (Do NOT set initdefault to this) # id:3:initdefault: # System initialization. si::sysinit:/etc/rc.d/rc.sysinit l0:0:wait:/etc/rc.d/rc 0 l1:1:wait:/etc/rc.d/rc 1 l2:2:wait:/etc/rc.d/rc 2 l3:3:wait:/etc/rc.d/rc 3 l4:4:wait:/etc/rc.d/rc 4 l5:5:wait:/etc/rc.d/rc 5 l6:6:wait:/etc/rc.d/rc 6 # Things to run in every runlevel. ud::once:/sbin/update # Trap CTRL-ALT-DELETE ca::ctrlaltdel:/sbin/shutdown -t3 -r now # When our UPS tells us power has failed, assume we have a few minutes # of power left. Schedule a shutdown for 2 minutes from now. # This does, of course, assume you have powerd installed and your # UPS connected and working correctly. pf::powerfail:/sbin/shutdown -f -h +2 "Power Failure; System Shutting Down" # If power was restored before the shutdown kicked in, cancel it. pr:12345:powerokwait:/sbin/shutdown -c "Power Restored; Shutdown Cancelled" # Run gettys in standard runlevels 1:2345:respawn:/sbin/mingetty tty1 2:2345:respawn:/sbin/mingetty tty2 3:2345:respawn:/sbin/mingetty tty3 4:2345:respawn:/sbin/mingetty tty4 5:2345:respawn:/sbin/mingetty tty5 6:2345:respawn:/sbin/mingetty tty6 # Run xdm in runlevel 5 # xdm is now a separate service x:5:respawn:/etc/X11/prefdm -nodaemon #This is for svscan SV:123456:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /servic e /dev/null /dev/console 2/dev/console When I do a "kill -HUP 1" then ps all I get is [root@skip daemontools-0.70]# ps PID TTY TIME CMD 10732 pts/100:00:00 su 10733 pts/100:00:00 bash 13992 pts/100:00:00 ps I am new to this, please help me if you can see what I did wrong. I followed the instructions precisesly so I'm not sure what went wrong. Or maybe it worked and I'm not seeing something... Thanks Matt
Re: Qmail setup, svscan glitch
Matt Simonsen [EMAIL PROTECTED] wrote: I'm new to Qmail and installing it for the first time. I have a 'server' install RedHat 6.2 linux box. [...] Well, I added the line it said to to the end of my initab which looks like this: [...] When I do a "kill -HUP 1" then ps all I get is [root@skip daemontools-0.70]# ps PID TTY TIME CMD 10732 pts/100:00:00 su 10733 pts/100:00:00 bash 13992 pts/100:00:00 ps Read the man page for ps. With no arguments, it will only show you processes owned by you. You probably need to do 'ps auxw' to get meaningful results here. This is more of a general Unix newbie question than anything specific to qmail. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
RE: Qmail setup, svscan glitch
You're right I'll cope "RTF Man page" to the whiteboard 20 times. Sorry. Matt -Original Message- From: Charles Cazabon [mailto:[EMAIL PROTECTED]] Sent: Friday, February 02, 2001 7:59 AM To: [EMAIL PROTECTED] Subject: Re: Qmail setup, svscan glitch Matt Simonsen [EMAIL PROTECTED] wrote: I'm new to Qmail and installing it for the first time. I have a 'server' install RedHat 6.2 linux box. [...] Well, I added the line it said to to the end of my initab which looks like this: [...] When I do a "kill -HUP 1" then ps all I get is [root@skip daemontools-0.70]# ps PID TTY TIME CMD 10732 pts/100:00:00 su 10733 pts/100:00:00 bash 13992 pts/100:00:00 ps Read the man page for ps. With no arguments, it will only show you processes owned by you. You probably need to do 'ps auxw' to get meaningful results here. This is more of a general Unix newbie question than anything specific to qmail. Charles -- --- Charles Cazabon[EMAIL PROTECTED] GPL'ed software available at: http://www.qcc.sk.ca/~charlesc/software/ Any opinions expressed are just that -- my opinions. ---
Re: Svscan
Gavin McCord [EMAIL PROTECTED] writes: I've created the /service directory with the necessary permissions and added on one line SV:123456:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null /dev/console 2/dev/console This should all be on one line. Maybe it was your mailer that wrapped it, but if not, fix it. However, having HUPped init, there's no new svscan running. I say new because there is an svscan running the qmail programs. How was your old svscan invoked? If it was done by an inittab line that started with SV:, then init thinks this new configuration is supposed to be the same instance. Can I run two svscans, or is there a conflict there? If so, what's the best way to reconcile the /var/qmail/supervise and /service directories. You can run two svscans in different directories, but it'd be better to have just one running in /service. Make symlinks in /service to your qmail service directories, start svscan there, and then (if you want to stop the harmless warnings) svc -dx each of the qmail service directories (including their log directories). paul
Re: Svscan
I'm getting error msgs to the console (a small selection): supervise: fatal: unable to start lib/run: file does not exist supervise: fatal: unable to start tmp/run: file does not exist supervise: fatal: unable to start cdrom/run: file does not exist supervise: fatal: unable to start bin/run: file does not exist supervise: fatal: unable to start usr/run: file does not exist supervise: fatal: unable to start var/run: access denied ad infinitum This from the entry in inittab. -- I'm Keyser Soze...No, I'm Keyser Soze. I'm Keyser Soze and so's my wife! (Monty Python play The Usual Suspects.)
Re: Svscan
On Fri, Jan 19, 2001 at 07:34:41PM +, Gavin McCord wrote: I'm getting error msgs to the console (a small selection): supervise: fatal: unable to start lib/run: file does not exist supervise: fatal: unable to start tmp/run: file does not exist supervise: fatal: unable to start cdrom/run: file does not exist supervise: fatal: unable to start bin/run: file does not exist supervise: fatal: unable to start usr/run: file does not exist supervise: fatal: unable to start var/run: access denied ad infinitum You are starting svscan in /. Either start it in /service or give /service as parameter to svscan. This is all well documented. This from the entry in inittab. -- Henning Brauer | BS Web Services Hostmaster BSWS| Roedingsmarkt 14 [EMAIL PROTECTED] | 20459 Hamburg http://www.bsws.de | Germany
Re: Svscan
looks like you didn't give svscan an argument to your service directory. check to see what the svscan line is like. should be invoked like svscan /service, not just svscan or svcan /. -tcl. On Fri, 19 Jan 2001, Gavin McCord wrote: I'm getting error msgs to the console (a small selection): supervise: fatal: unable to start lib/run: file does not exist supervise: fatal: unable to start tmp/run: file does not exist supervise: fatal: unable to start cdrom/run: file does not exist supervise: fatal: unable to start bin/run: file does not exist supervise: fatal: unable to start usr/run: file does not exist supervise: fatal: unable to start var/run: access denied ad infinitum This from the entry in inittab. -- I'm Keyser Soze...No, I'm Keyser Soze. I'm Keyser Soze and so's my wife! (Monty Python play The Usual Suspects.)
Svscan
I'm running qmail following the instructions in Life with Qmail. Now, I'm looking at replacing BIND with djbns. However, I'm stuck when at the first hurdle - daemontools. I've created the /service directory with the necessary permissions and added on one line SV:123456:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null /dev/console 2/dev/console into /etc/inittab. (I'm running Slackware 7.1 if this makes any difference.) However, having HUPped init, there's no new svscan running. I say new because there is an svscan running the qmail programs. Can I run two svscans, or is there a conflict there? If so, what's the best way to reconcile the /var/qmail/supervise and /service directories. -- I'm Keyser Soze...No, I'm Keyser Soze. I'm Keyser Soze and so's my wife! (Monty Python play The Usual Suspects.)
Re: Svscan
If they are using different directories then you can run more than one svscan. Is init logging any errors? Is svscan sending anything to the console? Regards. On Thu, Jan 18, 2001 at 11:32:59PM +, Gavin McCord wrote: I'm running qmail following the instructions in Life with Qmail. Now, I'm looking at replacing BIND with djbns. However, I'm stuck when at the first hurdle - daemontools. I've created the /service directory with the necessary permissions and added on one line SV:123456:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null /dev/console 2/dev/console
svscan is not running error
I am running RH6.2 with all sorts of uscpi-tcp, supervise, daemontools, vmailmgr, qmail, courier-imap as shown in the HOW-TO installation page. Everything seems to be installed OK and courier-imap started OK too but when I try run any other qmail-xxx then the error "svscan is not running" occured. Can someone show me how to properly install and setup uscpi-tcp/unix/supervise/daemontools for these configurations. Thanks, Steve
svscan
Hello, I installed svscan, as instructed for best performance with qmail, and then i started qmail using csh because svscan did not start it in enough time. now i have this message in my /var/log/messages file: Dec 2 .. init: Id "SV" respawning too fast: disabled for 5 minutes dont know how to fix this either, it has been doing this now for about 45 minutes... any ideas? thanks,
Re: svscan
On Wed, Dec 20, 2000 at 11:42:57AM -0800, Thomas Holton wrote: Hello, I installed svscan, as instructed for best performance with qmail, Well, svscan doesn't affect the performance of qmail - it affects the manageability and reliability of starting qmail. and then i started qmail using csh because svscan did not start it in enough time. now i have this message in my /var/log/messages file: Dec 2 .. init: Id "SV" respawning too fast: disabled for 5 minutes dont know how to fix this either, it has been doing this now for about 45 minutes... any ideas? This is actually a general Unix admin question, but be that as it may... You could have made make life a lot easier by showing us the inittab entry. Did you double-check that your inittab entry is correct? Did you read the inittab man page to understand what it's trying to do? How does that gel with the inittab entry you created? My guess is that you've got the path wrong to svscan or that the path points to something that isn't executable or that you've asked svscan to scan a directory that doesn't exist. Regards.
Re: svscan
Thomas, I'm finding theexact same problem here. I guess you are installing from Bruce's RPM packages ... well it seems that there is some kind of version mismatch between the packages. I couldn't solve it yet. I'd say you should check which are the recommended verisons of the daemontools package and the supervise-scripts package... that's the path I'm following. martin Thomas Holton wrote: Dec 2 .. init: Id "SV" respawning too fast: disabled for 5 minutes
Re: svscan
Thanks for your prompt reply. The commands i put into the inittab file are the ones given in the documentation: SV:123456:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null /dev/console 2/dev/console since svscan is located /usr/local/bin, it is clearly in the path. Besides, the message is talking about respawning too fast... it is still doing it at this time as well. Any other information you can give is greatly appreciated! On 20 Dec 2000, Mark Delany wrote: On Wed, Dec 20, 2000 at 11:42:57AM -0800, Thomas Holton wrote: Hello, I installed svscan, as instructed for best performance with qmail, Well, svscan doesn't affect the performance of qmail - it affects the manageability and reliability of starting qmail. and then i started qmail using csh because svscan did not start it in enough time. now i have this message in my /var/log/messages file: Dec 2 .. init: Id "SV" respawning too fast: disabled for 5 minutes dont know how to fix this either, it has been doing this now for about 45 minutes... any ideas? This is actually a general Unix admin question, but be that as it may... You could have made make life a lot easier by showing us the inittab entry. Did you double-check that your inittab entry is correct? Did you read the inittab man page to understand what it's trying to do? How does that gel with the inittab entry you created? My guess is that you've got the path wrong to svscan or that the path points to something that isn't executable or that you've asked svscan to scan a directory that doesn't exist. Regards.
Re: svscan
Actually mine is an install from the source which i have done. so i bet our problem is not the same then huh? unfortunately i downloaded the most recent version, so i wonder how i should go about this now? still no clue here so i suppose i should go back and try installing again. -tom On Wed, 20 Dec 2000, martin langhoff wrote: Thomas, I'm finding theexact same problem here. I guess you are installing from Bruce's RPM packages ... well it seems that there is some kind of version mismatch between the packages. I couldn't solve it yet. I'd say you should check which are the recommended verisons of the daemontools package and the supervise-scripts package... that's the path I'm following. martin Thomas Holton wrote: Dec 2 .. init: Id "SV" respawning too fast: disabled for 5 minutes
Re: svscan
On Wed, Dec 20, 2000 at 12:50:05PM -0800, Thomas Holton wrote: Thanks for your prompt reply. The commands i put into the inittab file are the ones given in the documentation: SV:123456:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null /dev/console 2/dev/console All on one line? SV:123456:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null /dev/console 2/dev/console Are there any messages on /dev/console? What happens if you start up svscan manually? # cd / # /usr/local/bin/svscan /service Show us the output. Regards. since svscan is located /usr/local/bin, it is clearly in the path. Besides, the message is talking about respawning too fast... it is still doing it at this time as well. Any other information you can give is greatly appreciated! On 20 Dec 2000, Mark Delany wrote: On Wed, Dec 20, 2000 at 11:42:57AM -0800, Thomas Holton wrote: Hello, I installed svscan, as instructed for best performance with qmail, Well, svscan doesn't affect the performance of qmail - it affects the manageability and reliability of starting qmail. and then i started qmail using csh because svscan did not start it in enough time. now i have this message in my /var/log/messages file: Dec 2 .. init: Id "SV" respawning too fast: disabled for 5 minutes dont know how to fix this either, it has been doing this now for about 45 minutes... any ideas? This is actually a general Unix admin question, but be that as it may... You could have made make life a lot easier by showing us the inittab entry. Did you double-check that your inittab entry is correct? Did you read the inittab man page to understand what it's trying to do? How does that gel with the inittab entry you created? My guess is that you've got the path wrong to svscan or that the path points to something that isn't executable or that you've asked svscan to scan a directory that doesn't exist. Regards.
Re: svscan
Thomas, I am guessing it's an issue with supervise scripts. Thy've gone from 2.x to 3.x and there things stopped working for me. The problem is that I haven't been able to replace 3.1 with 2.4 in a clean way. martin Thomas Holton wrote: still no clue here so i suppose i should go back and try installing again. -tom
Re: svscan
Thanks again: SV:123456:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null /dev/console 2/dev/console All on one line? no, makes up two lines Are there any messages on /dev/console? no, there is nothing in /dev/console/ What happens if you start up svscan manually? # cd / # /usr/local/bin/svscan /service Show us the output. many messages: supervise: fatal: unable to start qmail-smtpd/run: access denied supervise: fatal: unable to start qmail-send/run: file does not exist supervise: fatal: unable to start log/run: access denied and actually these messages are many times each. The permissions for /var/qmail/ are me with grp qmail. For whom should they be permissioned? thanks!
Re: svscan
On Wed, Dec 20, 2000 at 06:32:46PM -0300, martin langhoff wrote: Thomas, I am guessing it's an issue with supervise scripts. Thy've gone from 2.x to 3.x and there things stopped working for me. The problem is that I haven't been able to replace 3.1 with 2.4 in a clean way. I don't know what this 2.x and 3.x refers to - certainly not svscan from cr.yp.to, but in any event, svscan does not deal with the supervise scripts, supervise does. still no clue here so i suppose i should go back and try installing again. I guess that's one way to get a clue as to what's going on. Not my first choice though. Regards.
Re: svscan
On Wed, Dec 20, 2000 at 01:39:54PM -0800, Thomas Holton wrote: many messages: supervise: fatal: unable to start qmail-smtpd/run: access denied supervise: fatal: unable to start qmail-send/run: file does not exist supervise: fatal: unable to start log/run: access denied Are these log entries not explicit enough for you? Generally scripts need to be executable and exist if you expect them to be run. --Adam
Re: svscan
On Wed, Dec 20, 2000 at 01:39:54PM -0800, Thomas Holton wrote: Thanks again: SV:123456:respawn:env - PATH=/usr/local/bin:/usr/sbin:/usr/bin:/bin svscan /service /dev/null /dev/console 2/dev/console All on one line? no, makes up two lines Right. It needs to be one line. Are there any messages on /dev/console? no, there is nothing in /dev/console/ Once you make it one line you'll get them. You need to signal init every time you change this file. Read the man pages on init and initab to get an understanding of this mechanism. What happens if you start up svscan manually? # cd / # /usr/local/bin/svscan /service Show us the output. many messages: supervise: fatal: unable to start qmail-smtpd/run: access denied supervise: fatal: unable to start qmail-send/run: file does not exist supervise: fatal: unable to start log/run: access denied You have a serious number of install errors. You should re-check every step you made to ensure you followed the instructions exactly. The errors you are getting occur when people don't follow instructions to the letter. And I do mean EXACTLY TO THE LETTER. I suggest that for each step you do in the install, you then check that what you've done is correct. If the instruct says to create a file, do a cat to check it. If the instruction says to set a mode, use an ls -l to check it. If you make a synmlink, make sure that it links with ls -lL. Better yet, get a friend or peer to check each step with you. If the instructions aren't absolutely clear to you or your peer, ask what they mean, don't guess. This list knows only too well that guessers get it wrong - invariably. Here's a simple example. What made you split the inittab entry into two lines? Did you guess that it was ok? Regards.
Svscan, Multilog and performance issue
I have set up qmail using std instructions from life with qmail. In order to run svscan, it has to set up log directory and run multilog, some log program. However I notice that the hard disk and system is heavily loaded when multilog is turned on. Using my P133, the load is usually about 70% and the hard disk keeps accessing all the time. It in turns affect the response time when ssh to the email server. Could I not run multilog, ie not having a log directory at all to run svscan? I think I can not to run svscan instead just run supervise by some script file. Is it advisable? I also use svscan to control some other functions, including dhcpd and dhclient. However could control the order to these services being started by svscan? David Kwok
[Fwd: Re: Starting qmail: problem with svscan]
/usr/local/sbin/qmail stat /var/qmail/supervise: does not exist But obviously is does, since (1) everything is working, and (2) you recently posted the output of "ls -lR /var/qmail/supervise". Sounds like your /usr/local/sbin/qmail script is corrupt. You might try re-downloading it from: http://Web.InfoAve.net/~dsill/qmail-script-dt61.exe Thanks a lot Dave. I'll do it and I'll post you the result of it. = Here's the result when I start qmail: supervise: fatal: unable to start log/run: exec format error -- Joao Costa == DevWeb
Re: Starting qmail: problem with svscan
* Joao Costa [EMAIL PROTECTED] writes: supervise: fatal: unable to start log/run: exec format error Which part of "your run script is broken" do you not understand? sh -x it and see what happens. -- Robin S. Socha http://socha.net/ Cc: me and I'll kill -9 you.
Re: Starting qmail: problem with svscan
Should the service directory have any file? My service directory has none. /var/qmail/supervise should have qmail-send and qmail-smtpd subdirectories. I have both subdirectories on /var/qmail/supervise. -- Joao Costa == DevWeb
Re: Starting qmail: problem with svscan
I have installed qmail by following the steps that Dave Sill provides in his web-site (http://Web.InfoAve.Net/~dsill/lwq.html). Still, when I try to start qmail I get the following error message continuously: -n Starting qmail: svscan /etc/init.d/qmail: /var/qmail/run/svscan.pid: cannot create Hmm. What platform are you running on? The "-n" is an BSD vs. Sys V thing, and is ugly, but won't prevent the script from working. I don't know where you got /var/qmail/run/svscan.pid from, though, because the script in LWQ uses /var/run/svscan.pid. But even that's not enough to cause the following: I am running on SunOS 5.6. supervise: fatal: unable to acquire qmail-send/supervise/lock: access denied supervise: fatal: unable to acquire log/supervise/lock: access denied supervise: fatal: unable to acquire qmail-smtpd/supervise/lock: access denied supervise: fatal: unable to acquire log/supervise/lock: access denied What does the following show: ls -lR /var/qmail/supervise /var/qmail/supervise: total 4 drwxr-xr-t 4 root other512 Nov 14 17:25 qmail-send drwxr-xr-t 4 root other512 Nov 14 17:26 qmail-smtpd /var/qmail/supervise/qmail-send: total 6 drwxr-xr-x 3 root other512 Nov 14 17:26 log -rwxr-xr-x 1 root other 29 Nov 14 17:00 run drwx-- 2 root other512 Nov 15 12:13 supervise /var/qmail/supervise/qmail-send/log: total 4 -rwxr-xr-x 1 root other 88 Nov 14 17:01 run drwx-- 2 root other512 Nov 15 12:13 supervise /var/qmail/supervise/qmail-send/log/supervise: total 2 prw--- 1 root other 0 Nov 14 18:26 control -rw--- 1 root other 0 Nov 14 18:26 lock prw--- 1 root other 0 Nov 14 17:26 ok -rw-r--r-- 1 root other 18 Nov 15 12:13 status /var/qmail/supervise/qmail-send/supervise: total 2 prw--- 1 root other 0 Nov 14 18:26 control -rw--- 1 root other 0 Nov 14 18:26 lock prw--- 1 root other 0 Nov 14 17:25 ok -rw-r--r-- 1 root other 18 Nov 15 12:13 status /var/qmail/supervise/qmail-smtpd: total 6 drwxr-xr-x 3 root other512 Nov 14 17:26 log -rwxr-xr-x 1 root other339 Nov 14 17:03 run drwx-- 2 root other512 Nov 15 12:13 supervise /var/qmail/supervise/qmail-smtpd/log: total 4 -rwxr-xr-x 1 root other 94 Nov 14 17:05 run drwx-- 2 root other512 Nov 15 12:13 supervise /var/qmail/supervise/qmail-smtpd/log/supervise: total 2 prw--- 1 root other 0 Nov 14 18:26 control -rw--- 1 root other 0 Nov 14 18:26 lock prw--- 1 root other 0 Nov 14 17:26 ok -rw-r--r-- 1 root other 18 Nov 15 12:13 status /var/qmail/supervise/qmail-smtpd/supervise: total 2 prw--- 1 root other 0 Nov 14 18:26 control -rw--- 1 root other 0 Nov 14 18:26 lock prw--- 1 root other 0 Nov 14 17:26 ok -rw-r--r-- 1 root other 18 Nov 15 12:13 status ls -ld / /var /var/qmail /var/qmail/supervise drwxr-xr-x 26 root root1024 Nov 14 16:02 / drwxrwxrwt 23 root sys 512 Oct 31 17:01 /var drwxr-xr-x 9 root qmail512 Nov 14 17:56 /var/qmail drwxr-xr-x 4 root other512 Nov 14 16:58 /var/qmail/supervise What is svscan suppose to do? It monitors the service directory and runs "supervise" on services as needed. How can I get the parameters of svscan (read svscan's instructions)? LWQ has a section on daemontool which contains a link to the on-line documentation: http://Web.InfoAve.Net/~dsill/lwq.html#daemontools -- Joao Costa == DevWeb
Re: Starting qmail: problem with svscan
Joao Costa [EMAIL PROTECTED] wrote: I have installed qmail by following the steps that Dave Sill provides in his web-site (http://Web.InfoAve.Net/~dsill/lwq.html). Still, when I try to start qmail I get the following error message continuously: -n Starting qmail: svscan /etc/init.d/qmail: /var/qmail/run/svscan.pid: cannot create Hmm. What platform are you running on? The "-n" is an BSD vs. Sys V thing, and is ugly, but won't prevent the script from working. I don't know where you got /var/qmail/run/svscan.pid from, though, because the script in LWQ uses /var/run/svscan.pid. But even that's not enough to cause the following: I am running on SunOS 5.6. You can replace the echo -n "blah blah blah: " with echo "blah blah blah: \c" I'm still concerned about /var/qmail/run/svscan.pid vs. /var/run/svscan.pid. Was this something you changed intentionally? supervise: fatal: unable to acquire qmail-send/supervise/lock: access denied supervise: fatal: unable to acquire log/supervise/lock: access denied supervise: fatal: unable to acquire qmail-smtpd/supervise/lock: access denied supervise: fatal: unable to acquire log/supervise/lock: access denied What does the following show: ls -lR /var/qmail/supervise [snipped] OK, that all looks good. These are the same symptoms you get if you run "qmail start" twice without a "qmail stop" in between. What does the following show: qmail stat ps -ef |grep qmail -Dave
Re: Starting qmail: problem with svscan
qmail stat qmail: command not found Make that: /usr/local/sbin/qmail stat /var/qmail/supervise: does not exist ps -ef |grep qmail qmailr 2099 2096 0 Nov 14 ?0:00 qmail-rspawn qmaild 2087 2082 0 Nov 14 ?0:00 /usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb -c 20 -u 1040 -g 107 0 smtp root 2710 2471 1 18:46:53 pts/00:00 grep qmail root 2080 1641 0 Nov 14 ?0:01 supervise qmail-send qmaill 2085 2081 0 Nov 14 ?0:00 /usr/local/bin/multilog t /var/log/qmail root 2082 1641 0 Nov 14 ?0:01 supervise qmail-smtpd qmaill 2089 2083 0 Nov 14 ?0:00 /usr/local/bin/multilog t /var/log/qmail/smtpd qmails 2096 2080 0 Nov 14 ?0:00 qmail-send root 2098 2096 0 Nov 14 ?0:00 qmail-lspawn ./Maildir qmailq 2100 2096 0 Nov 14 ?0:00 qmail-clean That looks good, and shows that qamil has been running since Nov 14. So what's not working? -- Joao Costa == DevWeb
Re: Starting qmail: problem with svscan
Joao Costa [EMAIL PROTECTED] wrote: /usr/local/sbin/qmail stat /var/qmail/supervise: does not exist But obviously is does, since (1) everything is working, and (2) you recently posted the output of "ls -lR /var/qmail/supervise". Sounds like your /usr/local/sbin/qmail script is corrupt. You might try re-downloading it from: http://Web.InfoAve.net/~dsill/qmail-script-dt61.exe -Dave
Re: Starting qmail: problem with svscan
/usr/local/sbin/qmail stat /var/qmail/supervise: does not exist But obviously is does, since (1) everything is working, and (2) you recently posted the output of "ls -lR /var/qmail/supervise". Sounds like your /usr/local/sbin/qmail script is corrupt. You might try re-downloading it from: http://Web.InfoAve.net/~dsill/qmail-script-dt61.exe Thanks a lot Dave. I'll do it and I'll post you the result of it. -- Joao Costa == DevWeb
Starting qmail: problem with svscan
Hi, I have installed qmail by following the steps that Dave Sill provides in his web-site (http://Web.InfoAve.Net/~dsill/lwq.html). Still, when I try to start qmail I get the following error message continuously: -n Starting qmail: svscan /etc/init.d/qmail: /var/qmail/run/svscan.pid: cannot create supervise: fatal: unable to acquire qmail-send/supervise/lock: access denied supervise: fatal: unable to acquire log/supervise/lock: access denied supervise: fatal: unable to acquire qmail-smtpd/supervise/lock: access denied supervise: fatal: unable to acquire log/supervise/lock: access denied Does anyone know how to solve this problem? What is svscan suppose to do? How can I get the parameters of svscan (read svscan's instructions)? Thank you. -- Joao Costa == DevWeb
Re: Starting qmail: problem with svscan
Joao Costa [EMAIL PROTECTED] writes: Does anyone know how to solve this problem? What is svscan suppose to do? How can I get the parameters of svscan (read svscan's instructions)? There are a set of man pages for daemontools on qmail.org. svscan takes one parameter, the service directory. Are you running as root? Do the directories exist? -Matt -- | Matthew J. Brown - Senior Network Administrator - NBCi Shopping | | 1983 W. 190th St, Suite 100, Torrance CA 90504 | | Phone: (310) 538-7122| Work: [EMAIL PROTECTED] | | Cell: (714) 457-1854| Personal: [EMAIL PROTECTED] |
Re: Starting qmail: problem with svscan
Does anyone know how to solve this problem? What is svscan suppose to do? How can I get the parameters of svscan (read svscan's instructions)? There are a set of man pages for daemontools on qmail.org. svscan takes one parameter, the service directory. Should the service directory have any file? My service directory has none. Are you running as root? Do the directories exist? I am running as root and all directories exist. -- Joao Costa == DevWeb
Re: Starting qmail: problem with svscan
On Tue, Nov 21, 2000 at 07:13:54PM +, Joao Costa wrote: Does anyone know how to solve this problem? What is svscan suppose to do? How can I get the parameters of svscan (read svscan's instructions)? There are a set of man pages for daemontools on qmail.org. svscan takes one parameter, the service directory. Should the service directory have any file? My service directory has none. svscan runs one supervise for each dir present in the services dir. And supervise does need the run script. See http://cr.yp.to/daemontools/supervise.html for instructions RC -- +--- | Ricardo Cerqueira | PGP Key fingerprint - B7 05 13 CE 48 0A BF 1E 87 21 83 DB 28 DE 03 42 | Novis - Engenharia ISP / Rede Técnica | Pç. Duque Saldanha, 1, 7º E / 1050-094 Lisboa / Portugal | Tel: +351 2 1010 - Fax: +351 2 1010 4459 PGP signature
Re: Starting qmail: problem with svscan
Joao Costa [EMAIL PROTECTED] wrote: Should the service directory have any file? My service directory has none. /var/qmail/supervise should have qmail-send and qmail-smtpd subdirectories. -Dave
Re: Starting qmail: problem with svscan
Joao Costa [EMAIL PROTECTED] wrote: I have installed qmail by following the steps that Dave Sill provides in his web-site (http://Web.InfoAve.Net/~dsill/lwq.html). Still, when I try to start qmail I get the following error message continuously: -n Starting qmail: svscan /etc/init.d/qmail: /var/qmail/run/svscan.pid: cannot create Hmm. What platform are you running on? The "-n" is an BSD vs. Sys V thing, and is ugly, but won't prevent the script from working. I don't know where you got /var/qmail/run/svscan.pid from, though, because the script in LWQ uses /var/run/svscan.pid. But even that's not enough to cause the following: supervise: fatal: unable to acquire qmail-send/supervise/lock: access denied supervise: fatal: unable to acquire log/supervise/lock: access denied supervise: fatal: unable to acquire qmail-smtpd/supervise/lock: access denied supervise: fatal: unable to acquire log/supervise/lock: access denied What does the following show: ls -lR /var/qmail/supervise ls -ld / /var /var/qmail /var/qmail/supervise What is svscan suppose to do? It monitors the service directory and runs "supervise" on services as needed. How can I get the parameters of svscan (read svscan's instructions)? LWQ has a section on daemontool which contains a link to the on-line documentation: http://Web.InfoAve.Net/~dsill/lwq.html#daemontools -Dave
Re: Starting qmail: problem with svscan
Am Die, 21 Nov 2000 schrieb Matt Brown: Joao Costa [EMAIL PROTECTED] writes: Does anyone know how to solve this problem? What is svscan suppose to do? How can I get the parameters of svscan (read svscan's instructions)? svscan takes one parameter, the service directory. Does svscan also known as qmail-scanner. I remember head of a nessesary patch. This patch is buggy and must be manual debugged. Someone of this list have done this for himself. Is some version of the corrected version of this patch existing in the net? Is a version of qmail-scanner existing that includes a install-script that includes the patching of the file - done by the mentioned patch. Regards, Ruprecht
Re: system v style init script for svscan
"Have you looked at LWQ?" its practically a FAQ. Please excuse my ignorance, but: what is LWQ? Linux World headQuarter? ;-) Nope. He most likely meant Dave Sill's "life with qmail". Regards, Chin Fang [EMAIL PROTECTED] Felix
Re: system v style init script for svscan
Chin Fang [EMAIL PROTECTED] wrote: "Have you looked at LWQ?" its practically a FAQ. Please excuse my ignorance, but: what is LWQ? Linux World headQuarter? ;-) Nope. He most likely meant Dave Sill's "life with qmail". Check this out: http://www.acronymfinder.com/af-query.asp?Acronym=lwqFind=FindString=exact -Dave
svscan: unable to stat qmail: file does not exist
Hello all, After searching through the docs and the mail list archives I still can't find a reference to this problem so here it goes: I'm following the directions from http://www.redhat.com/mirrors/LDP/HOWTO/Qmail-VMailMgr-Courier-imap- HOWTO.html to setup Qmail with all the goodies I need for now. I got the source RPMs and installed those where possible. The qmail users and groups have been created. No paths were changed from the default. when I run '/etc/rc.d/init.d/svscan start' I get the following: svscan: warning: unable to stat qmail: file does not exist and it just keeps displaying on the terminal window where I tried to start the daemon. When I run '/etc/rc.d/init.d/svscan stop' I get the following: Stopping svscan: [ OK ] Stopping service pop3d: stopped. Stopping service pop3d/log: stopped. Stopping service qmail: svok: fatal: unable to chdir to qmail: file does not exist already stopped. Stopping service qmqpd: stopped. Stopping service qmqpd/log: stopped. Stopping service qmtpd: stopped. Stopping service qmtpd/log: stopped. Stopping service smtpd: stopped. Stopping service smtpd/log: stopped. Stopping service vmailmgrd: stopped. Stopping service vmailmgrd/log: stopped. I've looked in /var/run/messages and the only thing that gets logged there is: Oct 10 11:27:00 web svscan: svscan shutdown succeeded My question is twofold: 1. How do I go about creating the file/directory that svscan needs? 2. What package installed svscan so I can go in and fix the bug? (Namely that svscan seems to know it needs a file but doesn't fscking tell me what file it needs!) As always help is greatly appreciated. (I'm under the gun to get this working, our $1000+ commercial package is corrupting mail boxes and we're loosing mail and customer confidence.) Chris
Re: svscan: unable to stat qmail: file does not exist
Chris Cioffi [EMAIL PROTECTED] wrote: when I run '/etc/rc.d/init.d/svscan start' I get the following: svscan: warning: unable to stat qmail: file does not exist The output of "sh -x /etc/rc.d/init.d/svscan start" would be helpful, but I'd guess that you've got a link in your services directory (which could be /services) called "qmail" that points to the wrong place. I have no idea what the right place is, or which of the packages or HOWTO's should have set this up. 1. How do I go about creating the file/directory that svscan needs? Good question. 2. What package installed svscan so I can go in and fix the bug? svscan is part of daemontools. (Namely that svscan seems to know it needs a file but doesn't fscking tell me what file it needs!) It needs "qmail" to point to a directory containing the appropriate "run" script, among other things. As always help is greatly appreciated. (I'm under the gun to get this working, our $1000+ commercial package is corrupting mail boxes and we're loosing mail and customer confidence.) You're installing an MTA you know nothing about on a production system, and you expect that to raise customer confidence? Wasn't that a Dilbert strip? -Dave
Re: svscan weirdness...
Speaking of weirdness, I have an even stranger svscan problem, on my home machine running FreeBSD 4.1: If I start svscan from /etc/rc.local (in the line after xdm startup), my X server hangs, or rather it does not seem to recognise any keyboard input. Most keypresses elicit no response at all, while Alt-Ctrl-Fn (for n!=2) produces the usual "no virtual console there" beep. With such an unresponsive machine, I have no option other than hitting the reset button. Not a hint in any log file as to what can be the cause of this. If I start svscan after logging in, there is no problem. And whether it is me or rc.local starting the program, it happens through a shell script which really boils down to env - PATH=... svscan, so changes in the environment should be sort of irrelevant. (I don't really expect the list to solve this one for me, but if someone has a reasonable possible explanation, it might save me a lot of work trying to debug it.) - Harald
Re: svscan weirdness...
On Fri, 6 Oct 2000, Harald Hanche-Olsen wrote: Speaking of weirdness, I have an even stranger svscan problem, on my home machine running FreeBSD 4.1: If I start svscan from /etc/rc.local (in the line after xdm startup), my X server hangs, or rather it does not seem to recognise any keyboard input. Most keypresses elicit no response at all, while Alt-Ctrl-Fn (for n!=2) produces the usual "no virtual console there" beep. With such an unresponsive machine, I have no option other than hitting the reset button. Not a hint in any log file as to what can be the cause of this. If I start svscan after logging in, there is no problem. And whether it is me or rc.local starting the program, it happens through a shell script which really boils down to env - PATH=... svscan, so changes in the environment should be sort of irrelevant. (I don't really expect the list to solve this one for me, but if someone has a reasonable possible explanation, it might save me a lot of work trying to debug it.) Why not start xdm from /etc/ttys ? Outa curiousity does xdm work normally if you don't start svscan? Vince. -- == Vince Vielhaber -- KA8CSHemail: [EMAIL PROTECTED]http://www.pop4.net 128K ISDN from $22.00/mo - 56K Dialup from $16.00/mo at Pop4 Networking Online Campground Directoryhttp://www.camping-usa.com Online Giftshop Superstorehttp://www.cloudninegifts.com ==
Re: svscan weirdness...
+ Vince Vielhaber [EMAIL PROTECTED]: | Why not start xdm from /etc/ttys ? I think my reasoning was that the X server will simply take the first available virtual console, and while that is fairly predictable, if something breaks there is a potential surprise there. Possibly even a race condition between the X server and a bunch of gettys? | Outa curiousity does xdm work normally if you don't start svscan? Oh, yes. That's how I run it now. What I really should do next is to run svscan but not xdm at startup to see what happens then. It's just that when every failed experiment requires a hit to the reset button, with subsequent fsck-ing before I can get back to work, I tend to put it off. - Harald
svscan weirdness...
I am using svscan to start qmail and dnscache. I use a similar config on our mail server and it works fine. But on my Linux workstation, when I reboot I get screens full of errors. I do a 'killall svscan supervise' and the errors stop. Then I start up svscan from the command line using exactly the same syntax as in the rc.local file (I just type "svscan /service ") and it works perfectly. Here's the actual errors and configs: ------ svscan: warning: unable to start supervise dnscache: file does not exist svscan: warning: unable to start supervise dnscache/log: file does not exist svscan: warning: unable to start supervise qmail-smtpd: file does not exist svscan: warning: unable to start supervise qmail-smtpd/log: file does not exist svscan: warning: unable to start supervise qmail-send/log: file does not exist svscan: warning: unable to start supervise qmail-send: file does not exist ------ svscan is started like this, from /etc/rc.d/rc.local: -- #!/bin/sh /usr/local/bin/svscan /service -- And /service looks like this: petra:~$ ls -ld /service/ drwxr-xr-x 2 root root 4096 Jul 21 18:58 /service/ petra:~$ ls -l /service/ total 0 lrwxrwxrwx 1 root root 14 Jun 19 15:57 dnscache - /etc/dnscache// lrwxrwxrwx 1 root root 32 Jul 21 18:28 qmail-send - /var/qmail/supervise/qmail-send// lrwxrwxrwx 1 root root 32 Jul 21 17:51 qmail-smtpd - /var/qmail/supervise/qmail-smtpd/ And the same contents of each of the relevant directories: petra:~$ ls -l /etc/dnscache/ total 20 drwxr-sr-x 4 root root 4096 Jun 19 15:57 log/ drwxr-sr-x 5 root root 4096 Sep 2 14:30 root/ -rwxr-xr-x 1 root root 236 Jun 19 15:56 run* -rw--- 1 root root 128 Jun 19 15:56 seed drwx--S--- 3 root root 4096 Oct 5 10:57 supervise/ petra:~$ cat /etc/dnscache/run #!/bin/sh exec 21 exec seed ROOT=/etc/dnscache/root; export ROOT IP=127.0.0.1; export IP IPSEND=0.0.0.0; export IPSEND CACHESIZE=100; export CACHESIZE exec envuidgid dnscache \ softlimit -o250 -d300 \ /usr/local/bin/dnscache petra:~$ ls -l /var/qmail/supervise/qmail-send/ total 12 drwxr-xr-x 3 root root 4096 Jul 21 18:02 log/ -rwxr-xr-x 1 root root 29 Jul 21 17:35 run* drwx-- 2 root root 4096 Oct 5 10:57 supervise/ petra:~$ cat /var/qmail/supervise/qmail-send/run #!/bin/sh exec /var/qmail/rc petra:~$ cat /var/qmail/rc #!/bin/sh exec /usr/bin/env - PATH="/var/qmail/bin:$PATH" qmail-start ./Maildir/ petra:~$ ls -l /var/qmail/supervise/qmail-smtpd/ total 12 drwxr-xr-x 3 root root 4096 Jul 21 18:22 log/ -rwxr-xr-x 1 root root 125 Jul 21 18:56 run* drwx-- 2 root root 4096 Oct 5 10:57 supervise/ petra:~$ cat /var/qmail/supervise/qmail-smtpd/run #!/bin/sh exec /usr/local/bin/tcpserver -R -q -p -x /etc/tcp.smtp.cdb -u1002 -g102 0 smtp \ /var/qmail/bin/qmail-smtpd 21 Anyone see any red flags here? Thanks, Ben -- Ben Beuchler [EMAIL PROTECTED] MAILER-DAEMON (612) 321-9290 x101 Bitstream Underground www.bitstream.net
Re: svscan weirdness...
Ben Beuchler [EMAIL PROTECTED] wrote: svscan: warning: unable to start supervise dnscache: file does not exist Déjà vu. svscan can't find supervise. supervise lives in /usr/local/bin. -- #!/bin/sh /usr/local/bin/svscan /service -- Add: PATH=$PATH:/usr/local/bin export PATH before running svscan. -Dave
Re: svscan weirdness...
On Thu, Oct 05, 2000 at 12:57:47PM -0400, Dave Sill wrote: svscan: warning: unable to start supervise dnscache: file does not exist Déjà vu. Yeah... I saw the other post merest moments after I sent mine. Add: PATH=$PATH:/usr/local/bin export PATH before running svscan. D'oh... I knew it had to be something simple. Thanks! -- Ben Beuchler [EMAIL PROTECTED] MAILER-DAEMON (612) 321-9290 x101 Bitstream Underground www.bitstream.net
multilog thrashing under svscan
I'm trying to set up an autoturn implementation we've been using to run under svscan with all the other spiffy daemontools. The tcpserver command that launches maildirserial and all that is running great, but the log command is continually being restarted by supervise. I'm quite confused, as the log/run script is virtually identical to the others I'm using for qmail-smtpd, qmail-send, etc. Anyway, here's the svscan directory structure I'm working with, with the autoturn directory symlinked into /service, with the rest of my svscan proggies: -- amazhan [11:53am] # ls -ld /var/qmail/supervise/autoturn drwx--x--T 4 root qmail 512 Sep 18 11:39 /var/qmail/supervise/autoturn ^ Sticky bit IS set... amazhan [11:54am] # ls -lR /var/qmail/supervise/autoturn total 3 drwxr-xr-x 3 root qmail 512 Sep 18 11:46 log -rwxr-xr-x 1 root qmail 225 Sep 18 11:39 run drwx-- 2 root qmail 512 Sep 18 11:40 supervise /var/qmail/supervise/autoturn/log: total 2 -rw-r--r-- 1 root qmail 91 Sep 18 11:46 run drwx-- 2 root qmail 512 Sep 18 11:47 supervise /var/qmail/supervise/autoturn/log/supervise: total 1 prw--- 1 root qmail 0 Sep 18 11:47 control -rw--- 1 root qmail 0 Sep 18 11:30 lock prw--- 1 root qmail 0 Sep 18 11:30 ok -rw-r--r-- 1 root qmail 18 Sep 18 11:47 status /var/qmail/supervise/autoturn/supervise: total 1 prw--- 1 root qmail 0 Sep 18 11:39 control -rw--- 1 root qmail 0 Sep 18 11:30 lock prw--- 1 root qmail 0 Sep 18 11:30 ok -rw-r--r-- 1 root qmail 18 Sep 18 11:40 status -- And the actual "run" scripts: -- amazhan [11:55am] # cat /var/qmail/supervise/autoturn/run #!/bin/sh exec /usr/local/bin/tcpserver -l amazhan -H -q -R \ -x /etc/tcprules/tcp.autoturn.cdb -u74 -g1001 0 1338 \ sh -c 'cd /var/qmail/autoturn;maildirsmtp $TCPREMOTEIP autoturn-$TCPREMOTEIP- $TCPREMOTEIP AutoTURN' 21 amazhan [11:55am] # cat /var/qmail/supervise/autoturn/log/run #!/bin/sh exec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog t /var/log/autoturn -- According to the multilog docs, /var/log/autoturn shouldn't even need to exist, as it will create it if it doesn't. But after it failed the first time, I created the directory, owned by qmaill, with perms the same as the other multilog directories (755). What am I missing? Thanks, Ben -- Ben Beuchler [EMAIL PROTECTED] MAILER-DAEMON (612) 321-9290 x101 Bitstream Underground www.bitstream.net
Re: multilog thrashing under svscan
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 18 Sep 2000, at 12:12, Ben Beuchler wrote: amazhan [11:53am] # ls -ld /var/qmail/supervise/autoturn drwx--x--T 4 root qmail 512 Sep 18 11:39 /var/qmail/supervise/autoturn I'd rather see there drwx--x--t (ie. at least a --x for "other"); you see, your multilog is run as qmaill and qmaill can't pass through /var/qmail/supervise/autoturn. -BEGIN PGP SIGNATURE- Version: PGP 6.5.8 -- QDPGP 2.61b Comment: http://community.wow.net/grt/qdpgp.html iQA/AwUBOcZBclMwP8g7qbw/EQK3RACfQBczUG1uvmRN0c/uVMc+jU1mcacAoNe+ qzHcmmFdSRjyYZEcP9SItw5P =y2Z6 -END PGP SIGNATURE- -- Petr Novotny, ANTEK CS [EMAIL PROTECTED] http://www.antek.cz PGP key ID: 0x3BA9BC3F -- Don't you know there ain't no devil there's just God when he's drunk. [Tom Waits]
Re: multilog thrashing under svscan
On Mon, Sep 18, 2000 at 12:12:00PM -0500, Ben Beuchler wrote: the log command is continually being restarted by supervise. I'm quite confused, as the log/run script is virtually identical to the others I'm using for qmail-smtpd, qmail-send, etc. [snip] /var/qmail/supervise/autoturn/log: total 2 -rw-r--r-- 1 root qmail 91 Sep 18 11:46 run [snip] What am I missing? chmod a+x /var/qmail/supervise/autoturn/log/run :) james -- James Raftery (JBR54) - Programmer Hostmaster - IE TLD Hostmaster IE Domain Registry - www.domainregistry.ie - (+353 1) 706 2375 "Managing 4000 customer domains with BIND has been a lot like herding cats." - Mike Batchelor, on [EMAIL PROTECTED]
Re: multilog thrashing under svscan
On Mon, Sep 18, 2000 at 06:25:42PM +0100, James Raftery wrote: /var/qmail/supervise/autoturn/log: total 2 -rw-r--r-- 1 root qmail 91 Sep 18 11:46 run [snip] What am I missing? chmod a+x /var/qmail/supervise/autoturn/log/run :) D'oh d'oh d'oh d'oh d'oh d'oh... bangs head on wall repeatedly Ouch. Thanks! Ben -- Ben Beuchler [EMAIL PROTECTED] MAILER-DAEMON (612) 321-9290 x101 Bitstream Underground www.bitstream.net
svscan
hi, where to find svscan ? -- jens --- instant networks - netzwerkmanagment internetfullservices http://www.instant-networks.de
Re: svscan
On Thu, Sep 14, 2000 at 11:45:59PM +0200, Jens Georg wrote: where to find svscan ? http://cr.yp.to/daemontools.html -- Ben Beuchler [EMAIL PROTECTED] MAILER-DAEMON (612) 321-9290 x101 Bitstream Underground www.bitstream.net
SVSCAN not starting qmail
Well I first installed qmail on my RH6.2 box as a test. When I was ready to go live. I decided to copy over the scripts that I hacked on for hours. My problem now is that svscan doesn't seem to start the the services automatically. I can't start qmail at all. I check the scripts and they are all ok. I'm enclosing the scripts just in case. I have made sure to create the symlinks for the service directory. Svscan starts but the services don't. I know I've made a goof but I don't know where. Additionally I would like the pop3 to stop logging to the console. How do I allow unlimited access to my server? (No SPAM FILTER) My tcprules say :allow "pop3" #!/bin/shexec /usr/local/bin/tcpserver -v -R 0 pop3 /var/qmail/bin/qmail-popup mail.alljax.net\ /home/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir 21"rc" #!/bin/shexec env - PATH="/var/qmail/bin:$PATH" \qmail-start "`cat /var/qmail/control/defaultdelivery`" "send" #!/bin/shexec /var/qmail/rc "send/log" #!/bin/shexec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog ts250 /var/log/qmail/qmail-send "smtpd" #!/bin/shQMAILUID=`id -u qmaild`NOFILESGID=`id -g qmaild`exec /usr/local/bin/softlimit -m 500 \/usr/local/bin/tcpserver -v -p -x /etc/tcp.smtp.cdb \-u $QMAILUID -g $NOFILESGID 0 smtp /var/qmail/bin/qmail-smtpd 21 "smtpd/log" #!/bin/shexec /usr/local/bin/setuidgid qmaill /usr/local/bin/multilog ts250 /var/log/qmail/qmail-smtpd
svscan/supervise run script
When launching a program under svscan/supervise that has no port connections, (I just want to keep it running,) what is the correct line in the "run" script if I want to use syslog? Would something like: exec env - PATH="$PATH:/usr/local/bin" my_prog | \ splogger my_prog_id 3 or: exec env - PATH="$PATH:/usr/local/bin" my_prog 21 | \ splogger my_prog_id 3 work OK? Both seem to work OK, but are they correct? Thanks, John -- John ConoverTel. 408.370.2688 [EMAIL PROTECTED] 631 Lamont Ct. Cel. 408.772.7733 Campbell, CA 95008 Fax. 408.379.9602 http://www.johncon.com
Re: svscan/supervise run script
On Thu, Aug 03, 2000 at 07:08:38AM -, John Conover wrote: ! exec env - PATH="$PATH:/usr/local/bin" my_prog 21 | \ ! splogger my_prog_id 3 Almost. Use the log directory instead, if you can (replace qmaill with whatever user you want to run your log process on): cd /service/foobar printf '#!/bin/sh\nexec env - PATH="$PATH:/usr/local/bin" my_prog 21' run chmod +x run mkdir log printf '#!/bin/sh\nexec setuidgid qmaill splogger my_prog_id 3' log/run chmod +x log/run chmod +t . If the main process dies for some reason, the logging program is kept running ``so that no data is lost'' (according to the svscan page). ---Chris K. -- Chris, the Young One |_ If you can't afford a backup system, you can't Auckland, New Zealand |_ afford to have important data on your computer. http://cloud9.hedgee.com/ |_ ---Tracy R. Reed PGP: 0xCCC6114E/0x706A6AAD |_
qmail install/svscan question
Hi all, Just installed qmail on my first Linux server (easily converted from NT when I had a new project that called for a *stable* web/mail server :-). I've read the install docs, and am following Dave Sill's LWQ install directions. When it comes time to start qmail, I get this error loop: starting qmail:svscan supervise: fatal: unable to acquire log/supervise/lock: temporary failure supervise: fatal: unable to acquire qmail-send/supervise/lock: temporary failure supervise: fatal: unable to acquire log/supervise/lock: temporary failure supervise: fatal: unable to acuire qmail-smtpd/supervise/lock: temporary failure What needs to be changed where to make qmail/svscan happy? My directories and permissions are set as described in LWQ: http://web.infoave.net/~dsill/lwq.html#start-qmail Thanks, J!M jim (at) symbolicsite.com
Problems using svscan on Digital UNIX 4.0D
I administer a legacy server running tha above mentioned operating system, and decided to try out qmail on it to get some hands on experience. I follow the HOWTO (v2) closely, and everything seems fine until I try to start the svscan init script. Then I get the following error: . . 20362:/sbin/loader: Fatal Error: cannot malloc 24040:/sbin/loader: Fatal Error: cannot malloc 18016:/sbin/loader: Fatal Error: cannot malloc 20391:/sbin/loader: Fatal Error: cannot malloc 22058:/sbin/loader: Fatal Error: cannot malloc . . And I have a really hard time killing it off. :) I have spendt half the weekend looking for a solution, but at no avail. I have tried out several versions of daemontools (0.60, 0.61 and 0.70), both native and gcc compilers. I also don't think there is a memory problem as the compile goes fine and the system should have plenty of memory. I anyone have any idea about what causes this problem, I would really appreciate it! -- Bjørn Nordbø
svscan doesn't clean up dirs during shutdown...
Hello list (sorry if this is already out, I thought I already posted it, but my mailclient isn't able to find it), I've got a little problem with my qmail installation on my new FreeBSD 4 Stable box: everything is working really well, but during shutdown, supervise (or svscan, whatever is responsible) doesn't remove it's lockfiles in /var/qmail/supervise/qmail-send/log/supervise /var/qmail/supervise/qmail-send/supervise /var/qmail/supervise/qmail-smtpd/log/supervise /var/qmail/supervise/qmail-smtpd/supervise and during the following reboot svscan does complain that the lockfiles are already there. While it would be easy to hack Dave's startup script to first delete the lockfiles and then going on with the start of qmail I'd prefer to have a clean solution here as this system is going to be cloned several times in the next few weeks. Any ideas? Best regards, Gabriel
