| 1 |
> Basically, this is not intended to be used to shutdown a puter on a |
| 2 |
> regular basis, unless you burn out P/S's on a daily basis. O-o |
| 3 |
> |
| 4 |
> Just didn't want someone to be using this on a regular basis and then |
| 5 |
> wondering why their system has a new nickname, FUBAR. :'( |
| 6 |
|
| 7 |
In most cases you'll find that 'shutdown -h now' |
| 8 |
takes only a few seconds. If you're typing againsed |
| 9 |
the clock and don't to it every day then the SysReq |
| 10 |
tecnhique is somewhat error prone. |
| 11 |
|
| 12 |
In most cases the stuff that can't handle a |
| 13 |
crash tends to live at higher runlevels anyway |
| 14 |
and gets stopped when you exit rl 3; stuff that |
| 15 |
gets started at boot time are more likely |
| 16 |
service daemons that can easily handle a reset. |
| 17 |
Even if your shutdown croaks halfway through |
| 18 |
the stuff, chances are that got shut down first |
| 19 |
was the most fragile anyway (e.g., databases |
| 20 |
that had to flush cache) and you got whatever |
| 21 |
you could cleaned up however fast you could do |
| 22 |
it and you live with the rest on restart. |
| 23 |
|
| 24 |
-- |
| 25 |
Steven Lembark +1 888 359 3508 |
| 26 |
Workhorse Computing 85-09 90th St |
| 27 |
lembark@×××××××.com Woodhaven, NY 11421 |
| 28 |
-- |
| 29 |
gentoo-user@l.g.o mailing list |
Archives