Montana Banana, Inc. wrote:
> Is there any reason why I should regularly re-start the httpsd daemon, perhaps
> weekly? Or should I just let the daemon run forever, or until I need to restart
> it manually for some reason?
No reason - My public server has been up continuously for 64 days, max=84 days. The
only reason it ever goes down is for configuration changes or because some idiot
trips over the power plug.
One caveat - I assume you are running this on *nix. If its NT, it doesn't apply.
I've never seen an NT server run reliably, doing real work, and last longer than a
week. My servers are all Linux (including major corporate and banking customers).
> If I re-start it weekly from a cron job/script, wouldn't I have to insert the
> httpsd password into the script? Isn't this a security risk? Is there a way to
> restart the daemon without putting passwords into the script?
Yes, you would have to insert the password, and yes, it is a security risk. If
someone were to see the password and could get your server's private key (if they
could do one, they could probably do the other) and set up a server that masquerades
as yours.
Final Note: there is a cure for these problems if you are running NT, with the
following procedure:
1) Insert Linux Boot disk
2) ctrl-alt-del
3) fdisk
:)
Austin
begin: vcard
fn: Austin Gosling
n: Gosling;Austin
org: ioNET S.A.
adr: Armando Pesantes OE9-743;;;Quito;Pichincha;;Ecuador
email;internet: [EMAIL PROTECTED]
title: General Manager
tel;work: +593 2 43 54 12
tel;fax: +593 2 43 54 12
note: PGP public key http://www.ionet.com.ec/pubkeys/alg.txt
x-mozilla-cpt: ;0
x-mozilla-html: FALSE
version: 2.1
end: vcard
