On Thu, 2006-07-06 at 18:18 -0400, Mike Frysinger wrote:
> On Thursday 06 July 2006 15:27, Albert Hopkins wrote:
> > On Tue, 2006-07-04 at 18:58 -0400, Mike Frysinger wrote:
> > > On Tuesday 04 July 2006 18:43, Enrico Weigelt wrote:
> > > > We should think about mechanisms to check if the service i
On Thursday 06 July 2006 15:27, Albert Hopkins wrote:
> On Tue, 2006-07-04 at 18:58 -0400, Mike Frysinger wrote:
> > On Tuesday 04 July 2006 18:43, Enrico Weigelt wrote:
> > > We should think about mechanisms to check if the service is
> > > actually running. This could also be used for frequently
On Tue, 2006-07-04 at 18:58 -0400, Mike Frysinger wrote:
> On Tuesday 04 July 2006 18:43, Enrico Weigelt wrote:
> > We should think about mechanisms to check if the service is
> > actually running. This could also be used for frequently service
> > checks and notification.
>
> there is no fool pro
* Roy Marples <[EMAIL PROTECTED]> schrieb:
> However, with baselayout-1.12 we intercept calls to start-stop-daemon
> and store information about what was started (binary, pidfile) so
> when root then does "/etc/init.d/foo status" we check to see if all
> the binaries are still running. If not
> The problem is: if the service still runs,
yes, I know. But I read the bug report and Enrico wrote that for some reasons
the service didn't run anymore.
"if it had been started but terminated abnormally (not through this script)" and in this case the zap argument is for me
the right solution
On Tuesday 04 July 2006 23:58, Mike Frysinger wrote:
> On Tuesday 04 July 2006 18:43, Enrico Weigelt wrote:
> > We should think about mechanisms to check if the service is
> > actually running. This could also be used for frequently service
> > checks and notification.
>
> there is no fool proof wa
On Tuesday 04 July 2006 18:43, Enrico Weigelt wrote:
> We should think about mechanisms to check if the service is
> actually running. This could also be used for frequently service
> checks and notification.
there is no fool proof way to do this
-mike
pgpKkEmrK36b2.pgp
Description: PGP signatur
One slightly hackish way would be the grab the PID, and check in ps aux
as to if it was running. That's one way to do what you are talking
about.
~ nick
On Wed, 2006-07-05 at 00:43 +0200, Enrico Weigelt wrote:
> * Pablo Yanez Trujillo <[EMAIL PROTECTED]> schrieb:
> > what about "/etc/init.d/ntpd
* Pablo Yanez Trujillo <[EMAIL PROTECTED]> schrieb:
> what about "/etc/init.d/ntpd zap"? It deletes the file on /var/ and set
> the status of the init.d-file as not started. It is useful for such a case
> :)
The problem is: if the service still runs, it will attemt to start it
twice. So this
what about "/etc/init.d/ntpd zap"? It deletes the file on /var/ and set the status of the init.d-file as not
started. It is useful for such a case :)
Regards
Pablo
Pablo Yánez Trujillo
http://klingsor.informatik.uni-freiburg.de/
Enrico Weigelt wrote:
Hi folks,
maybe I've found a problem
Enrico Weigelt wrote:
> Hi folks,
>
> maybe I've found a problem in the init.d stuff:
>
> It seems that /var/lib/init.d/started/* is blindly trusted,
> instead of actually checking if some service is running.
>
> For example, ntpd cannot be restarted via its init.d script
> if it died for some
Hi folks,
maybe I've found a problem in the init.d stuff:
It seems that /var/lib/init.d/started/* is blindly trusted,
instead of actually checking if some service is running.
For example, ntpd cannot be restarted via its init.d script
if it died for some reason - /var/lib/init.d/started/ntpd
12 matches
Mail list logo
