| 1 |
Steven Lembark wrote: |
| 2 |
> |
| 3 |
> > Well, this one takes longer. Just the foldingathome takes about 20 |
| 4 |
> > seconds or more to shutdown. It can take over 60 seconds at times. |
| 5 |
> > That service for some reason has to completely shutdown before the |
| 6 |
> > others start to shutdown. The others will shutdown in parallel like I |
| 7 |
> > have set up. Then there is all the other services that have to stop. |
| 8 |
> > Quite literally, I only had seconds to shutdown since the P/S was |
| 9 |
> > stinking like a skunk. I just needed to umnount the file systems and |
| 10 |
> > power off as fast as possible. I didn't want to just pull the plug but |
| 11 |
> > I needed a shutdown that fast. |
| 12 |
> |
| 13 |
> Hackint the shutdowns to background the shutdown |
| 14 |
> op and return is usually pretty simple -- don't know |
| 15 |
> why more app's don't do that by default. |
| 16 |
> |
| 17 |
> 'halt' will get you down with little typing if you |
| 18 |
> want to bypass the init scripts; so will "kill -TERM 1". |
| 19 |
> Add a 'sync' before either of them and you'll probably |
| 20 |
> be able to come up with minimal trouble. |
| 21 |
> |
| 22 |
|
| 23 |
What's the difference between halt command and shutdown? I thought they |
| 24 |
were basically the same thing. |
| 25 |
|
| 26 |
Also, in case you missed it. I have a service, foldingathome, that |
| 27 |
takes a while to stop and no other service can be stopped in parallel |
| 28 |
with this one. That is one of my key sticking points with the |
| 29 |
shutdown. Most of the others are pretty fast. I just needed the |
| 30 |
quickest *clean* shutdown I could get. |
| 31 |
|
| 32 |
Thanks |
| 33 |
|
| 34 |
Dale |
| 35 |
|
| 36 |
:-) :-) |
| 37 |
-- |
| 38 |
gentoo-user@l.g.o mailing list |
Archives