Skip wrote:
One more dumb question (and this really is more of a linux question
than a SA question), but if I start spamd -d from a console, and then
quit that console, won't the daemon quit too?
No, that's what makes it a daemon.. it detaches from the console
completely, thus remains active even if the shell that spawned it
terminates.
I think the only other option is to "run it from cron" to get it out
of a console, but that's a real kludge and I'd rather not do that.
Erm.. definitely not. running from cron is only for things you want to
run at regular intervals. It is not a valid way for starting daemons
(ie: something you want to run once and leave running)
You might also want to look at setting up an init script that daemonizes
spamd automatically at bootup. There's some sample init scripts in with
the spamd directory. How exactly you install it varies with what OS
you're using.
Generally it gets installed in /etc/init.d or /etc/rc.d/init.d, and then
symlinked to various /etc/rc<runlevel number>.d directories to cause it
to be called at various runlevels. If your system has redhat-ish and
chkconfig, it can automate this part for you, as the redhat init script
that comes with spamd has chkconfig tags in it.
John Hardin wrote:
On Fri, 21 Mar 2008, Skip wrote:
If I did go this route, how would I make sure that my spamc talks to
my spamd and not the other one that is already running on the box?
Don't use the default network port number.
