Hey
Since upgrading to systemd 215-5+b1, I have seen no further
re-occurrences of this issue.
Cheers
Iain
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Control: tag -1 + moreinfo
Hi,
can any of you reproduce this on current testing/sid (that is, with
systemd v215)?
Cheers,
--
intrigeri
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hey,
I have the same situation. Seems like systemd froze 3 days ago. What
got me to notice was an attempted apt-get upgrade on this jessie system:
sudo ls /proc/1/fd
[sudo] password for iain:
0 1 2
14:28:24 weezer:~$ sudo ls -l /proc/1/fd
total 0
lrwx-- 1 root root 64 Aug 30 15:25 0 ->
I had the same problem yesterday, I noticed it when trying to apt-get
upgrade a debian testing system. Fuser showed no process owning
/run/systemd/private, and ls /proc/1/fd showed that all filedescriptors
were closed, except 0, 1 and 2 which were linked to /dev/null.
After rebooting that problem
Package: systemd
Version: 208-6
Severity: important
Dear Maintainer,
I have two machines here with systemd becoming non-responsive after roughly one
to a few days of uptime. Both share the same hardware and software install.
This has been so for about a week (i.e. the problem reappears after a re
5 matches
Mail list logo
