| 1 |
> The problem is: if the service still runs, |
| 2 |
|
| 3 |
yes, I know. But I read the bug report and Enrico wrote that for some reasons the service didn't run anymore. |
| 4 |
"if it had been started but terminated abnormally (not through this script)" and in this case the zap argument is for me |
| 5 |
the right solution :) |
| 6 |
|
| 7 |
> We should think about mechanisms to check if the service is |
| 8 |
> actually running. |
| 9 |
|
| 10 |
Yes, that's right, I have sometimes problem with apache2 and need to kill apache2 and use the zap argument. |
| 11 |
|
| 12 |
cu |
| 13 |
|
| 14 |
Pablo Yánez Trujillo |
| 15 |
http://klingsor.informatik.uni-freiburg.de/ |
| 16 |
|
| 17 |
|
| 18 |
Enrico Weigelt wrote: |
| 19 |
> * Pablo Yanez Trujillo <yanezp@×××××××××××××××××××××××.de> schrieb: |
| 20 |
>> what about "/etc/init.d/ntpd zap"? It deletes the file on /var/.... and set |
| 21 |
>> the status of the init.d-file as not started. It is useful for such a case |
| 22 |
>> :) |
| 23 |
> |
| 24 |
> The problem is: if the service still runs, it will attemt to start it |
| 25 |
> twice. So this cannot be used in automatic processes, just for manual |
| 26 |
> intervention. |
| 27 |
> |
| 28 |
> We should think about mechanisms to check if the service is |
| 29 |
> actually running. This could also be used for frequently service |
| 30 |
> checks and notification. |
| 31 |
> |
| 32 |
> |
| 33 |
> cu |
| 34 |
-- |
| 35 |
gentoo-dev@g.o mailing list |
Archives