[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-users] Suspending users & sites
- Subject: Re: [cobalt-users] Suspending users & sites
- From: "Rodolfo J. Paiz" <rpaiz@xxxxxxxxxxxxxx>
- Date: Tue May 8 11:09:04 2001
- List-id: Mailing list for users to share thoughts on Cobalt products. <cobalt-users.list.cobalt.com>
At 5/8/01 09:29 AM -0400, you wrote:
shimi, do
you have any thoughts on this? Anyone else?
While I believe Shimi when he says that will work, you're right in that
killall sends a signal to multiple processes matching sendmail. I'd rather
not do that. The command to restart sendmail is "officially" as listed in
the instructions something like:
kill -HUP `head -n 1 sendmail.pid` (NOT EXACT COMMAND)
I just wrote a tiny script in the /root/bin directory called
sendmail.restart, put these contents in it:
------
#!/bin/bash
#
echo "Rehashing virtusertable..."
makemap hash /etc/mail/virtusertable < /etc/mail/virtusertable
echo "Rehashing access database..."
makemap hash /etc/mail/access < /etc/mail/access
echo "Restarting sendmail..."
kill -HUP `head -n 1 sendmail.pid` # (NOT EXACT COMMAND)
------
Now when I make any change, I just call that script. That way it's (a)
easier and quicker, and (b) less likely that I'll forget to rehash
something someday. I waste a few CPU cycles rehashing everytime I make a
change, but hell with it... the server can handle it.
Again, please keep in mind that I'm typing all this from memory. DO NOT USE
THE COMMAND HERE! Look it up.
--
Rodolfo J. Paiz
rpaiz@xxxxxxxxxxxxxx