Re: [SSI-devel] onsvc and Debian

[Aneesh K. K.V <ane...@di...>]

On Wed, 2003-07-30 at 17:48, Chirag Kantharia wrote:

> 
> Where is the above defined?
> 
> | +	fprintf(stderr,"Debian doesn't support service startup "
> | +			"using this command \n");
> | +	fprintf(stderr,"Use onall or onclass \n");
> | +	
> | +	exit(1);
> 
> Why exit? Debian surely supports start/stop/reload, which can be used
> using onall.c? Probably, we can leave to the Debian initscripts to
> inform the user that status is not supported.
> 

Both the commands take different set of arguments. So there is no way i
can pass it down to /etc/init.d/service name . Basically all these
command issue onnode <nodenum> /etc/init.d/service option. onsvc will
get the set of node based on the service name. ie it looks at
/cluster/<nodenum>/var/lock/subsys/service_name . This is created by
/etc/init.d/service_name scripts of redhat. Where debian doesn't do it.
Or in other words debian service startup scripts doesn't support the a
method of finding the status of the service .

BTW the changes will be effected only for onsvc command. onall and
onclass will work perfectly fine. 


-aneesh