On Sat, Oct 11, 2014 at 08:36:22PM +0200, Kai Lüke wrote: > you are right, but then if case that not Port 22 ist used in sshd_config > how about testing if /etc/systemd/system/ssh.socket already exists and > if not generate it with the right port? That maybe would make a smooth > transition from non-systemd wheezy to systemd jessie.
It just seems like an odd thing to worry about on upgrade given that ssh.socket is disabled by default, so the configuration discrepancy will only affect anyone once they explicitly choose to activate it. I'm concerned by the additional bug surface created by trying to second-guess things any further in the maintainer scripts; my experience suggests that the less of that we can do, the better, especially where configuration files are involved. So if this doesn't affect anyone on upgrade until they take some explicit action, which I believe to be the case, then I would prefer to leave it up to sysadmins to sort out. Perhaps a compromise would be for me to document this in README.Debian? It already has a section for socket activation and already has to document other considerations there, such as the non-obvious interaction with MaxStartups. Thanks, -- Colin Watson [cjwat...@debian.org] -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
