Bug#793814: Workaround for this bug

[Stefano]

My machine is 64bit (VMware guest). I can do any test/check on it when the
problem appears, since it's a development machine and no critical job runs
on it. If you have an idea.

-- 
Stefano
Il 15/ott/2015 19:48, "Michael Biebl" <biebl at debian.org> ha scritto:

> Am 15.10.2015 um 19:15 schrieb James Bottomley:
> > On Thu, 2015-10-15 at 07:35 +0200, Stefano wrote:
> >> Same here. I have a git server with clients connecting every 10 minutes
> or
> >> so via SSH, and the problem is exactly the same.
> >>
> >> About 20 hours from reboot logind goes nuts, then it must be restarted
> at
> >> very variable intervals, about a couple a day.
> >
> > What architecture is this?  I only see the problems on a 32 bit x86
> > system.  I don't see them on a 64 bit x86 in spite of trying to trigger
> > them there (in a sample size of 1 of each, so it's not statistically
> > significant ... yet).
>
> Thanks, that is an interesting data point.
>
> > I also see that /run/systemd/sessions has about a hundred or so sessions
> > whose leaders are dead on the 32 bit system.  On the 64 bit system it
> > appears only still living sessions are in here.
> >
> > The final curious observation is that on the 32 bit system, the session
> > id never seems to go over 4k.  On the 64 bit system, it does.
>
> Btw, in both cases (#770135 and #793814) the users have been restarting
> the dbus daemon. You mentioned that you did not do that.
>
> So I'm not sure if it's actually the same issue after all and your
> problem should be tracked as a separate issue.
>
>
>
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20151015/ee2cb237/attachment-0002.html>