![](/i/fill.gif) |
![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Orchid XP v2 <voi### [at] dev null> wrote:
> > SIGKILL should basically never be used because it's "too strong", only
> > when no other options work.
> Isn't that the one the kernel sends during shutdown?
Well, during shutdown the kernel first sends SIGTERM to all running
processes, after which it sends SIGKILL to the remaining. I suppose in
most cases there aren't any processes running after the former (at least
if all processes are bug-free and behave correctly) but it's a good way
to make sure that all processes are truely terminated before shutdown.
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Warp <war### [at] tag povray org> wrote:
> Not in POV-Ray itself, but you can suspend (almost) any program in unix
> by pressing ctrl-z on the console where you started it (this actually sends
> SIGHUP to the process, which can also be sent to it by other means, eg.
> using the kill command).
Correction: SIGTSTP
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
>>> SIGKILL should basically never be used because it's "too strong", only
>>>when no other options work.
>
>
>>Isn't that the one the kernel sends during shutdown?
>
>
> Well, during shutdown the kernel first sends SIGTERM to all running
> processes, after which it sends SIGKILL to the remaining. I suppose in
> most cases there aren't any processes running after the former (at least
> if all processes are bug-free and behave correctly) but it's a good way
> to make sure that all processes are truely terminated before shutdown.
That's more of less what I figured, yes. :-)
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
Warp <war### [at] tag povray org> wrote:
> Well, during shutdown the kernel first sends SIGTERM to all running
> processes, after which it sends SIGKILL to the remaining. I suppose in
> most cases there aren't any processes running after the former (at least
> if all processes are bug-free and behave correctly) but it's a good way
> to make sure that all processes are truely terminated before shutdown.
Warp, would you be able to point me to a link documenting this behavior?
I'm interested in reading more about the general boot/shutdown order of
things. I assume not all flavors of Unix/Linux implement the same
proceedures in the same order, do they?
- How
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
How Camp <hac### [at] gmail com> wrote:
> Warp, would you be able to point me to a link documenting this behavior?
> I'm interested in reading more about the general boot/shutdown order of
> things. I assume not all flavors of Unix/Linux implement the same
> proceedures in the same order, do they?
I don't know any specific documents, but try googling for things like
"init", "runlevel 6" and "linux boot".
The last one, for example, gave this:
http://ourworld.compuserve.com/homepages/KanjiFlash/BPTour.htm
It's about the booting process, not the shutdown, though.
--
- Warp
Post a reply to this message
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |
| ![](/i/fill.gif) |
|
![](/i/fill.gif) |
|
![](/i/fill.gif) |
| ![](/i/fill.gif) |