On Sun, 17 Aug 2014 00:19:48 +0200
Michael Biebl bi...@debian.org wrote:
Am 16.08.2014 23:54, schrieb Joe:
Aug 16 00:02:03 jresid systemd[2913]: systemd-exit.service: main
process exited, code=exited, status=200/CHDIR
Aug 16 00:02:03 jresid systemd[2913]: Failed to start Exit the
Am 19.08.2014 23:11, schrieb Joe:
Again, this seems to confirm that nobody is invoked to do a particular
job and then not logged out for some reason. This seems to be the area,
when PID 2593 appears. As all entries show the same time, I assume logs
are interleaved and this may not be the
Am 20.08.2014 03:05, schrieb Michael Biebl:
/etc/cron.daily/popularity-contest: su -s /bin/sh -c
/usr/sbin/popularity-contest nobody
here. You might check the dates of the /var/log/popularity-contest*
files, if they match with the session starts you get in your journal.
Looking at the
Hi.
On Sat, 16 Aug 2014 00:44:31 +0200
david davce...@keyworld.net wrote:
I have been bothered by this too.
KUser shows this user as nobody whose home directory is
/nonexistent and whose login shell is /usr/sbin/nologin.
The account on one machine is set as disabled but both my current
On Sat, 16 Aug 2014 10:00:08 +0400
Reco recovery...@gmail.com wrote:
Hi.
On Sat, 16 Aug 2014 00:44:31 +0200
david davce...@keyworld.net wrote:
I have been bothered by this too.
KUser shows this user as nobody whose home directory is
/nonexistent and whose login shell is
On Sat, 16 Aug 2014 08:17:50 +0100
Joe j...@jretrading.com wrote:
I have /usr/sbin/nologin also. This is up-to-date sid with systemd,
which may not have the same defaults as previous distributions.
Curious. And what shell do they set now for users with uid 100?
I've checked more-or-less
Am 16.08.2014 11:36, schrieb Reco:
On Sat, 16 Aug 2014 08:17:50 +0100
Joe j...@jretrading.com wrote:
I have /usr/sbin/nologin also. This is up-to-date sid with systemd,
which may not have the same defaults as previous distributions.
Curious. And what shell do they set now for users with
On Sat, 16 Aug 2014 11:51:28 +0200
Michael Biebl bi...@debian.org wrote:
base-passwd (3.5.30) unstable; urgency=medium
[ Colin Watson ]
..
* Change the shell of all global static users other than root (which
retains /bin/sh) and sync (as /bin/sync is rather harmless) to
On Sat, Aug 16, 2014 at 6:51 PM, Michael Biebl bi...@debian.org wrote:
Am 16.08.2014 11:36, schrieb Reco:
On Sat, 16 Aug 2014 08:17:50 +0100
Joe j...@jretrading.com wrote:
I have /usr/sbin/nologin also. This is up-to-date sid with systemd,
which may not have the same defaults as previous
I.m starting to get the picture but we have moved away from what I think
was the prime motive for this trhead to be started.
User 65534 is causing a frustrating 90 - 120 second delay during
shutdown. That's 6 to 9 hrs a year!
Can this delay be eliminated? After all it did not used to happen
On Sat, Aug 16, 2014 at 6:36 PM, Reco recovery...@gmail.com wrote:
On Sat, 16 Aug 2014 08:17:50 +0100
Joe j...@jretrading.com wrote:
I have /usr/sbin/nologin also. This is up-to-date sid with systemd,
which may not have the same defaults as previous distributions.
Curious. And what shell do
david writes:
User 65534 is causing a frustrating 90 - 120 second delay during
shutdown.
Some process that happens to be running as nobody is failing to exit
when instructed to do so. Systemd is waiting patiently for 90 seconds
before sending it a kill -9. You need to either find that process
On Sat, 16 Aug 2014 12:59:24 +0200
david davce...@keyworld.net wrote:
Can this delay be eliminated? After all it did not used to happen before
systemd was implemented.
OP is running Sid. So there are problems with stability in the unstable
version of Debian... and? ...
Oh well.
ps -u
On Sat, Aug 16, 2014 at 7:59 PM, david davce...@keyworld.net wrote:
I.m starting to get the picture but we have moved away from what I think was
the prime motive for this trhead to be started.
User 65534 is causing a frustrating 90 - 120 second delay during shutdown.
That's 6 to 9 hrs a year!
On Fri, 15 Aug 2014 21:39:03 +0100
Joe j...@jretrading.com wrote:
This is a can of worms, and I hereby abandon it.
OK, I lied. I was bored...
A little further on... journald *has* been keeping persistent journals,
but with different user permissions, now root:systemd-journal 640.
Am 16.08.2014 23:54, schrieb Joe:
Aug 16 00:02:03 jresid systemd[2913]: systemd-exit.service: main
process exited, code=exited, status=200/CHDIR
Aug 16 00:02:03 jresid systemd[2913]: Failed to start Exit the Session.
Apparently that service failed with exit code 200 / CHDIR.
Am 15.08.2014 20:34, schrieb Joe:
Apart from 'nobody', according to /etc/passwd. He seems to login most
sessions, and when he does, he causes the dreaded two-minute shutdown.
Here's what I can find in journalctl:
sudo journalctl | grep user-65534
Aug 06 07:56:20 jresid systemd[1]:
On Fri, 15 Aug 2014 21:24:38 +0200
Michael Biebl bi...@debian.org wrote:
Am 15.08.2014 20:34, schrieb Joe:
Apart from 'nobody', according to /etc/passwd. He seems to login
most sessions, and when he does, he causes the dreaded two-minute
shutdown.
Here's what I can find in
I have been bothered by this too.
KUser shows this user as nobody whose home directory is
/nonexistent and whose login shell is /usr/sbin/nologin.
The account on one machine is set as disabled but both my current
machines (#3 failed to turn on today :-( ) suffer the shut down delay -
most
The purpose of the nobody account is to allow daemons to run with
minimum privileges. Getting rid of it would be a bad idea.
--
John Hasler
jhas...@newsguy.com
Elmwood, WI USA
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
20 matches
Mail list logo
