On 02/04/15 08:23, jd1008 wrote:
On 02/03/2015 04:55 PM, Richard Shaw wrote:
> I'm troubleshooting some video problems with a used laptop I got for cheap.
>
> For the day is was pretty nice, Dell Latitude D620 with Nvidia Quadro graphics (the
problem I'm troubleshooting).
>
> I was looking through the journal when I saw this shortly after logging in:
>
> Feb 03 17:47:15 localhost.localdomain systemd-logind[676]: Removed session c1.
> Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Default.
> Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Default.
> Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Basic System.
> Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Basic System.
> Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Paths.
> Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Paths.
> Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Timers.
> Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Timers.
> Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopping Sockets.
> Feb 03 17:47:15 localhost.localdomain systemd[1364]: Stopped target Sockets.
> Feb 03 17:47:15 localhost.localdomain systemd[1364]: Starting Shutdown.
> Feb 03 17:47:15 localhost.localdomain systemd[1364]: Reached target Shutdown.
> Feb 03 17:47:15 localhost.localdomain systemd[1364]: Starting Exit the Session...
> Feb 03 17:47:15 localhost.localdomain systemd[1364]: Received SIGRTMIN+24 from PID
2173 (kill).
>
> Why does systemd think I'm trying to shut down the computer right after logging
in?
>
> The computer doesn't actually shut down and I'll get a usable desktop after
what I assumed was a hard lock but it takes well over 5 minutes, I haven't put a
stopwatch to it.
>
> Thanks,
> Richard
>
>
You will always see this in the logs AFTER booting.
All of this "stopping ....whatever ....."
comes AFTER
Starting Plymouth switch root service
....
Shortly thereafter you should see
SELinux: initialized (dev sysfs, type sysfs), uses genfs_contexts
.....etc,
I don't believe that is true, or normal.....
Just after rebooting and logging in.....
[egreshko@f21 ~]$ uptime
09:13:21 up 1 min, 4 users, load average: 1.19, 0.46, 0.17
[egreshko@f21 ~]$ journalctl -b -0 | grep -i stopping
No entries found....
From the previous boot log....
[egreshko@f21 ~]$ journalctl -b -1 | grep -i stopping
Feb 04 09:11:38
f21.greshko.com systemd[1180]: Stopping Default.
Feb 04 09:11:38
f21.greshko.com systemd[1180]: Stopping Basic System.
Feb 04 09:11:38
f21.greshko.com systemd[1180]: Stopping Paths.
Feb 04 09:11:38
f21.greshko.com systemd[1180]: Stopping Timers.
Feb 04 09:11:38
f21.greshko.com systemd[1180]: Stopping Sockets.
Feb 04 09:11:40
f21.greshko.com vboxadd[1311]: Stopping VirtualBox Additions [ OK ]
09:11:40 being the time of rebooting.
--
If you can't laugh at yourself, others will gladly oblige.