I wrote: > I want the chrony package to install in a configuration that will "just > work" on most systems. To do that I must put a password in that file. I > don't want to put in a default password as most users will not change it, > but I don't want to go to an interactive postinst either. A solution I > came up with is to generate and install a unique random password in the > postinst.
Chris writes: > Why not just have a password in there that cannot be entered by a user (A > bit like putting a '*' in the passwd file)? You may need to alter the > code, but it should be trivial. The password is used by scripts in cron.weekly, ip-up.d, and ip-down.d which use the control program to send commands to the deamon. If I did as you suggest these scripts would not work until the admin put in a real password. -- John Hasler [EMAIL PROTECTED] (John Hasler) Dancing Horse Hill Elmwood, WI
