Christian Boltz píše v Po 04. 09. 2006 v 16:01 +0200: > Hello, > > Am Montag, 4. September 2006 12:45 schrieb Stanislav Brabec: > > Create a new daemon, running by default: triggerd > > "one more daemon" is not a really good solution... > There are already too much daemons ;-) and some people will disable it > as they did with zmd already. > > The idea with "touch a triggerfile" sounds good - you could combine it > with SuSEconfig style scripts starting with > test -e /var/run/trigger/ldconfig || exit 0 # [1] > to speedup SuSEconfig.
SuSeconfig is deprecated and it was an idea how to get it rid. Using triggers in packages does not work well in some cases, triggering by directory change would be better - for example gtk-update-icon-cache has to be triggered by a touch in cca 240 packages, including KDE packages, absolutely unrelated to gtk (but because KDE and GNOME can share icon themes, it can contain data usable in GNOME). IMHO triggering by directory change can be implemented by two ways: - Trigger them inside RPM during RPM database update. (Unacceptable, will make our RPM incompatible with the rest of the world.) - In kernel using inotify. (Needs an extra daemon.) > No need for a daemon. Yes, but there is a chance to run the "daemon" temporarily from RPM and terminate it, when RPM installation is over. Permanently running daemon could have more usage: - Update config files from /etc/sysconfig/foo - Restart daemons after config change - Update caches/indexes after manual installation of non-package. - ... -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: [EMAIL PROTECTED] Lihovarská 1060/12 tel: +420 284 028 966 190 00 Praha 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
