Hi Roger, On 7/20/2012 10:50 AM, Roger Leigh wrote: > While this is true, aiccu causes problems due to its unique requirement > that you must have a valid username/password etc. for your tunnel > broker. ssh does not--by default it works without error, unless you > take deliberate steps to break it. > > When I install aiccu, I might not yet have these details due to needing > to sign up, or not having the details to hand. I don't think it's a > reasonable expectation to require these. > > The other point is that if I don't have these details, then it's not > worth starting up. There's a difference between a broken configuration > and being unconfigured. If it's broken, then it's legitimate to fail > on startup; if it's not yet been configured, then by all means print > a warning, but please don't error out.
I tried 2 scenarios: 1) install aiccu...-14.1 with blank username&password -> dist-upgrade 2) install aiccu...-14.1 with bogus username&password -> dist-upgrade In both scenarios the upgrade went ok. In the first scenario aiccu isn't even started and in the second debconf only asked for a password (gave bogus again). So with default installs/upgrades I can't reproduce the problem you describe, only if you deliberate break/change the aiccu config but then you got the same as with openssh-server. There are 3 situations aiccu bails out with an exit 1: 1) configuration file doesn't exist 2) configuration is incorrect 3) AICCU not configured to daemonize The last one could/should be an exit 0 but the other two should really be an exit 1 (and you run into #2). Best regards, Reinier -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
