On Tue, 2011-07-26 at 21:28 +0100, Paul Howarth wrote: > On Tue, 26 Jul 2011 16:13:59 -0400 > Dave Jones <davej@xxxxxxxxxx> wrote: > > > On Tue, Jul 26, 2011 at 06:22:50PM +0200, Jim Meyering wrote: > > > FYI, I've just yum-updated my rawhide VM to the latest > > > (but not from the console) and was surprised to lose the connection > > > while it was happening. Again. It happened to me last week, too. > > > > > > I got back in via the console and tried to reinstall it via "yum > > > reinstall openssh-server". That failed (sorry, didn't record the > > > diagnostic). > > > > > > Just dug a little and found this was reported a week ago: > > > > > > http://bugzilla.redhat.com/722625 > > > > It bit me again yesterday, this time while in a screen session > > (I thought I'd learn from the earlier mistake). When I logged back in, > > somehow the screen session had vanished. > > > > This behaviour from sshd is pretty nasty. I don't recall it ever > > doing this before on updates, so why does it start doing it now ? > > > > arguably that bz should be reassigned to sshd, as that's the root > > cause for yum freaking out. > > Perhaps it's because in %postun it has "systemctl try-restart > sshd.service" where it used to have "service sshd condrestart", and > systemd kills all running sshd processes whereas the old one only > killed the main one and not the children? It looks more like the first victim of systemd using cgroups as a replacement for setsid() etc. ... pam_systemd being the first return volley in that war. *sigh*. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel
