On Mon, Dec 20, 2010 at 3:16 PM, Simon Males <[email protected]> wrote: >> http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3 >> >> "... must not overwrite or otherwise mangle the user's configuration >> without asking ... " >> >> In short, your locally changed config file should be safe. If you're >> using a for of debian that does not adhere to this policy, then all >> bets are off (I'm not aware of any distro ignoring this policy). > > Sorry I need to be a little specific. After a memcached upgrade, dpkg > will (to the best of my knowledge) perform something like the > following: > > /etc/init.d/memcached restart > > Is it possible to convince dpkg to perform a similar action on my own > init.d script?:
Not really clean, but perfectly functional... You can edit the original rc script to start any others you need, and therefore if one gets restarted then they all get restarted. Alternatively, if you decide to make a clean change, you could check this tool out... http://packages.debian.org/stable/admin/dpkg-repack Chris- -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
