On Wed, 27.07.11 16:56, James Antill (ja...@fedoraproject.org) wrote:
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*.
systemd is not using cgroups as replacement for
One thing to watch out for is /var/empty. I have had to manually recreate
/var/empty and /var/empty/sshd to get the server to work again. This
might be related to the recent rpm issue, but I am not sure about that.
--
devel mailing list
devel@lists.fedoraproject.org
On Wed, 2011-07-27 at 09:33 -0500, Bruno Wolff III wrote:
One thing to watch out for is /var/empty. I have had to manually recreate
/var/empty and /var/empty/sshd to get the server to work again. This
might be related to the recent rpm issue, but I am not sure about that.
Yes, it is related to
On Tue, 2011-07-26 at 23:46 +0200, Lennart Poettering wrote:
On Tue, 26.07.11 17:16, James Antill (ja...@fedoraproject.org) wrote:
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
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
On 07/26/2011 12:22 PM, Jim Meyering wrote:
snip
service ssh restart
Would that be:
service sshd restart
?
--
Regards,
OldFart
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Clyde E. Kunkel wrote:
On 07/26/2011 12:22 PM, Jim Meyering wrote:
snip
service ssh restart
Would that be:
service sshd restart
Yes, thanks.
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
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
On Tue, 26 Jul 2011 16:13:59 -0400
Dave Jones da...@redhat.com 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.
On Tue, 2011-07-26 at 21:28 +0100, Paul Howarth wrote:
On Tue, 26 Jul 2011 16:13:59 -0400
Dave Jones da...@redhat.com 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
On Tue, 26.07.11 17:16, James Antill (ja...@fedoraproject.org) wrote:
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
On Tue, Jul 26, 2011 at 11:46:30PM +0200, Lennart Poettering wrote:
If restarting sshd kills the sshs sessions then my guess is that
pam_systemd is not enabled (or somehow failing) and hence user sessions
stay members of the sshd cgroup instead of getting their own.
Lennart, is pam_systemd a
12 matches
Mail list logo
