| 1 |
On 05/08/2013 03:18 PM, Jeroen Roovers wrote: |
| 2 |
> On Wed, 8 May 2013 20:55:35 +0200 |
| 3 |
> Ambroz Bizjak <ambrop7@×××××.com> wrote: |
| 4 |
> |
| 5 |
>>> Init.d scripts are programs - they could probably do just about |
| 6 |
>>> anything. |
| 7 |
>> |
| 8 |
>> They couldn't monitor a process and restart it when it crashes, as |
| 9 |
>> specified by the restart options in the unit file. That is, without |
| 10 |
>> significant modifications in the way OpenRC works, such as adding a |
| 11 |
>> monitoring process, or hacks such as launching a daemon that monitor |
| 12 |
>> that process specifically. |
| 13 |
> |
| 14 |
> Sounds like a great feature. A crashed process is a buggy one, and I |
| 15 |
> would want to investigate said program before I relaunched it, and not |
| 16 |
> have it automatically relaunched as if nothing had happened. |
| 17 |
|
| 18 |
That's highly, highly, highly use-case dependent. If it's a non-critical |
| 19 |
service, or in a non-critical environment, that's one thing. If it's a |
| 20 |
service whose downtime can be measured in value lost, that's quite another. |
| 21 |
|
| 22 |
I've had setups where, yes, I had it respawn. But I also wanted it to |
| 23 |
send me a core dump so I could investigate. Were I in that circumstance |
| 24 |
again, I'd automate collection and analysis of the dumps to produce heat |
| 25 |
maps for me. |
Archives