On Tue, Feb 07, 2006 at 04:36:53PM +0100, Christian Hammers wrote: > > > instead, you should possibly file a bug against cron-apt, or > > maybe apt/dpkg if there is not a way to do what you want. > The only possible suggestion here would let dpkg have a default > answer of "n" to the question if the config file should be replaced > by the maintainer. Maybe something in /etc/dpkg/dpkg.cfg.
Or maybe hack cron-apt to pipe yes -n to the operations. Then I can think of some other problems that will cause, like answering n to "Do you wish to continue" on kernel-packages. > But apart from that I would strongly discourage actually doing updates > with cron-apt. Use it to notify yourself by mail but never let the > system restart your services unattended if it's not absulutely > necessary. It's hard in our situation, because we have too many systems to maintain by hand. I guess I'll have to find another way around it. -- Ryan Underwood, <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
