You missed the point Billy. It would be less likely to happen on Windoze
because the machines don't stay up for years without requiring a reboot, if
for nothing else to patch security holes. We are talking years, people had
left in the meantime, and not due to layoffs. While it is true that they
should have, and do now, better administrative procedures HPUX and most
other Unix systems are highly stable. One cause is that since you used to
pay a lot for them (less now) if it went down the customer held the vendor's
feet to the fire as to why the system was down. Since the customer paid
quite a bit for it, they spoke loud. In the Windoze world no CEO or CIO
calls up some high level person at MS and demands to know why their Windoze
box blue screened. MS would never let the person talk to anyone beyond
first level support. MS's expectations regarding stability are much
different from HP's or Sun's expectations about the reliability and uptime
of their machines. A Windoze server has its roots in a personal computer,
where it was acceptable to have to reboot at least daily. That attitude has
changed somewhat over the years, but not sufficiently to have as good an
uptime (in general) and stability as a more robust and efficient OS.
Jim
--
Replace part of the email address: kennedy-down_with_spammers_at_attbi.com
with family. Remove the negative part, keep the minus sign. You can figure
it out.
"Billy Verreynne" <vslabs_at_onwe.co.za> wrote in message
news:avm26g$7fj$1_at_ctb-nnrp2.saix.net...
> Jim Kennedy wrote:
>
> > When they bought them back up they had some problems. The
> > machines had been running for years without being taken down and over
> > those years they had started a variety of processes from the consoles.
> > Unfortunately, no one documented their process and did not put it in the
> > equivalent Unix startup script.
> <snipped>
>
> > That would never happen on Windoze.
>
> Bullshit.
>
> How about running a NET START in a CMD console on Windows and forgetting
to
> enable it in Service Manager's config to autostart it next boot time
> around?
>
> How about using NET USE to do a critical mapping that's required for a
home
> rolled server? And forgetting to make it persistant?
>
> How about manually modifying your router table?
>
> The so-called problem you mentioned witn HP-UX has sweet nothing to do
with
> HP or Unix or the operating system.
>
> It has everything to do with SHITTY ADMINISTRATORS. And there are loads of
> them around.
>
> --
> Billy
Received on Fri Jan 10 2003 - 06:43:45 CST
