* Steve Lamb said: > > You need to get a root shell WITHOUT a reboot. So you need roots > > shell to be static, and you need a static su, and a static sulogin. > > Because if you were so concerned about data integrity that you would not > leave a known crippled server in place where unforeseen complications could > cause data corruption. Come on. You put up a brand new machine with a shiny, new Debian installation on it. Suddenly your 2GB SCSI drive fails for some reason. The system was brand new, was it a "known crippled server"? You're root partition on the broken disk is damaged, but your other disk which has /usr and /var/www on it still works. What you have to do? Hotswap the broken disk and copy a backup of the root dir and do it all without downing a server. With statics it's possible. > Because if you were so concerned about the service's uptime you would be > operating in a redundant architecture so that the loss of a single machine > would not bring down the service. Yeah, give me those hundreds of thousands of bucks and I'll do it. > One has to ask, BTW, how new httpds are being loaded if the machine is so > fucked that you can't even login or work without static binaries? Oh, wait, > you'd have them all statically linked as well. I get it now. One has to know more than one httpd around, boy. roxen doesn't fork new bins, use roxen if you're concerned. > Until you can convince me of a situation where that is otherwise, your > entire argument is bunk. What is the reason to convince you? marek
Attachment:
pgptB_kI7bTOv.pgp
Description: PGP signature