FAQ Search Today's Posts Mark Forums Read
» Video Reviews

» Linux Archive

Linux-archive is a website aiming to archive linux email lists and to make them easily accessible for linux users/developers.


» Sponsor

» Partners

» Sponsor

Go Back   Linux Archive > Debian > Debian Development

 
 
LinkBack Thread Tools
 
Old 10-20-2011, 10:11 AM
peter green
 
Default Bug#601455: general: can't stop daemon using /etc/init.d/foo stop when, disabled via /etc/default/foo

Many packages seem to provide ENABLE/DISABLE variables in
/etc/default/foo, providing a confusing red herring for this
task --- a second method which does not work nearly as well,
as you pointed out
Though there are some situations where it is nessacery. Consider
vtund for example which has seperate enable/disable flags for
running in server and client modes (with the potential for
multiple seperate client instances).



A complicating factor is that the sysadmin may already have customized
some ENABLE/DISABLE settings and a move like this should not override
their settings. So perhaps packages should stop advertising the
ENABLE/DISABLE vars in /etc/default/<package>, but continue to respect
them when set.

regardless of any plan to discourage use of the /etc/default
mechanism (I think removing it altogether is not really
reasonable) I think the original bug of being unable to stop
a dameon after disabling it in /etc/default still needs to be
fixed.





--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4E9FF3EE.1090006@p10link.net">http://lists.debian.org/4E9FF3EE.1090006@p10link.net
 
Old 10-21-2011, 12:26 AM
Jonathan Nieder
 
Default Bug#601455: general: can't stop daemon using /etc/init.d/foo stop when, disabled via /etc/default/foo

Hi,

peter green wrote:

> Though there are some situations where it is nessacery. Consider vtund for
> example which has seperate enable/disable flags for running in server and
> client modes (with the potential for multiple seperate client instances).

Thanks for this clarification. Luckily vtun's RUN_SERVER option is
not an instance of the DISABLE pattern Mathias mentioned: it does not
work by exiting the init script early, and it does not prevent
stopping the server.

> regardless of any plan to discourage use of the /etc/default
> mechanism (I think removing it altogether is not really reasonable)

To be clear, I didn't mean to suggest that configurability through
/etc/default is something to be phased out or discouraged --- only the
DISABLE variables. If you consider that unreasonable, could you
explain how, so others can come up with something better that
addresses your concerns?

[...]
> I think
> the original bug of being unable to stop
> a dameon after disabling it in /etc/default still needs to be fixed.

Feel free to file reports against individual packages (especially
reports with patches!). However, if one wants to make a serious dent
in this in the archive as a whole, it seems worthwhile to take the
extra minutes to move to a saner interface for disabling services at
the same time, instead of just patching the current "pretend you're
running, but don't run" method.

Cheers,
Jonathan



--
To UNSUBSCRIBE, email to debian-devel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20111021002636.GA17448@elie.hsd1.il.comcast.net">h ttp://lists.debian.org/20111021002636.GA17448@elie.hsd1.il.comcast.net
 

Thread Tools




All times are GMT. The time now is 12:28 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.
Copyright 2007 - 2008, www.linux-archive.org