Server Shut Down

Hi.

How often should I shut down the server (if ever)?

(RH Linux 9: file server, print server, DHCP, DNS, NIS, SMB [WINS]).

Thanks.

Jorge L. Davila-Laureano wrote:

> Hi.
>
> How often should I shut down the server (if ever)?
>
> (RH Linux 9: file server, print server, DHCP, DNS, NIS, SMB [WINS]).

Only for hardware changes, or upgrades to the kernel. Otherwise, there's no
reason to shut it down at all.


--
Lew Pitcher, IT Consultant, Application Architecture
Enterprise Technology Solutions, TD Bank Financial Group

(Opinions expressed here are my own, not my employer's)

Jorge L. Davila-Laureano wrote:
>
> How often should I shut down the server (if ever)?
>

Reboot/shutdown only when absolutely necessary.

Examples of situations where a reboot/shutdown could potentially be
necessary are:

1. Hardware failure/replacement
2. Hardware upgrade
3. Kernel upgrade/patching

Regards,

Lukas

"Jorge L. Davila-Laureano" <j_davila@webmail.uprh.edu> wrote in message
news:d7918682.0402060615.4dc486e1@posting.google.c om

> How often should I shut down the server (if ever)?
> (RH Linux 9: file server, print server, DHCP, DNS, NIS, SMB [WINS]).

I shut down each of the several servers about twice per year, but only to
blow the dust out of the innards since they're in a relatively dirty
environment.

Other than that, I can't find any reason short of hardware failure to do so.


tony

--
use hotmail for any email replies



-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

> How often should I shut down the server (if ever)?

I know its cool to have a _really_ large number when you run 'uptime'
but your server can never get cracked if its not on. Plus, if there's
no one there to use it, why have it on? I shut down most of my servers
(everything but my externel web servers) at 7:00 pm. I figure that
everyone is gone (our office closes at 6:00) and not one is still
working from home (besides, they can do that through our website).
Then I turn them on at 4:45 am, before even the early-birds arrive at
our office.

My servers have NEVER been compromised. I attribute it to open-source
software and shutdowns.

Sean Callaway
www.scallaway.com

"Sean Callaway" <scallaway@programmer.net> wrote in message
news:898fdf26.0402072042.2edde4a5@posting.google.c om

> I shut down most of my servers
> (everything but my externel web servers) at 7:00 pm. I figure that
> everyone is gone (our office closes at 6:00) and not one is still
> working from home (besides, they can do that through our website).
> Then I turn them on at 4:45 am, before even the early-birds arrive at
> our office.
>
> My servers have NEVER been compromised. I attribute it to open-source
> software and shutdowns.

You sound like the type of person that thinks chickens will never have sex
if you keep the roosters and hens in separate pens at night.





-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2004-02-08, Sean Callaway <scallaway@programmer.net> wrote:
>
> I know its cool to have a _really_ large number when you run 'uptime'
> but your server can never get cracked if its not on. Plus, if there's
> no one there to use it, why have it on? I shut down most of my servers
> (everything but my externel web servers) at 7:00 pm. I figure that
> everyone is gone (our office closes at 6:00) and not one is still
> working from home (besides, they can do that through our website).
> Then I turn them on at 4:45 am, before even the early-birds arrive at
> our office.

If you telinit 1 at 7pm, and telinit 5 at 4.45am, you can preserve your
uptime and ''avoid'' getting cracked.

Not all sites can have that kind of downtime--people in my office work
at all hours, so machines need to be available 24/7.

- --keith

- --
kkeller-usenet@wombat.san-francisco.ca.us
(try just my userid to email me)
AOLSFAQ=http://wombat.san-francisco.ca.us/cgi-bin/fom

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQFAJfgYhVcNCxZ5ID8RAgowAJ0QcZQt27R+Ot4mcsSirg 999E0fhQCgnheC
lWh3o845qxkjsOPj9tak0ME=
=XAKB
-----END PGP SIGNATURE-----

> Not all sites can have that kind of downtime--people in my office work
> at all hours, so machines need to be available 24/7.

Of course, I realize that. The office is mostly sales people, so
almost everyone is 9 to 5.

In response to the "keeping the chickens and the roosters seperate"
post, I run other security measures, as well. However, I know that no
one will be able to get in to my systems when they're off.

Sean Callaway
www.scallaway.com

Sean Callaway wrote:

>> Not all sites can have that kind of downtime--people in my office work
>> at all hours, so machines need to be available 24/7.
>
> Of course, I realize that. The office is mostly sales people, so
> almost everyone is 9 to 5.
>
> In response to the "keeping the chickens and the roosters seperate"
> post, I run other security measures, as well. However, I know that no
> one will be able to get in to my systems when they're off.
>


All you need to do is take down the ether with a cron script and then
restart when needed also with a cron script.

Powering systems on an off is said to be extremely hard on them.

Duh *thunks his forehead* I never thought of that. That's a good idea,
now I feel kind of dumb.

Sean Callaway
www.scallaway.com