Christoph, an all...
Possible solutions are to extend init-scripts to do the job
Not sure I like this idea, after running SuSEconfig (shouldn't that be a symlink to SUSEconfig now? ;)), I like to read through the generated config files in /etc or wherever before running the init script. Now, that may be me being paranoid, but I like to make sure that the config of [insert daemon here] is sane before restarting it
, or to patch the corresponding programs to read /etc/sysconfig directly.
This could become a real pain to maintain, not really my problem directly, just thinking about the poor packagers...
* SuSEconfig.sendmail (package: sendmail) -> do not touch either :)
+1 - please don't touch this, it does its job admirably and since it respects manual changes correctly, it allows for people to make their own config changes if they so desire.
* SuSEconfig.susehelp (package: susehelp) -> cron? + initscript?
I think cron for this, there's no inherent reason that I can think of why this shouldn't just be done at 0100. -- James Ogley james@usr-local-bin.org http://usr-local-bin.org Packages for SUSE: http://usr-local-bin.org/rpms Help end poverty: http://oxfam.org.uk/imin --------------------------------------------------------------------- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org For additional commands, e-mail: opensuse-factory+help@opensuse.org