On Fr, 05.04.19 12:42, Harald Dunkel (harald.dun...@aixigo.de) wrote:
> On 4/5/19 12:21 PM, Lennart Poettering wrote:
> > On Fr, 05.04.19 11:53, Harald Dunkel (harald.dun...@aixigo.de) wrote:
> >
> > >
> > > This is a VNC session, started via crontab @reboot.
> >
> > IIRC debian/ubuntu do not
On 4/5/19 12:21 PM, Lennart Poettering wrote:
On Fr, 05.04.19 11:53, Harald Dunkel (harald.dun...@aixigo.de) wrote:
This is a VNC session, started via crontab @reboot.
IIRC debian/ubuntu do not have pam-systemd in their PAM configuration
for cron, which means these services are not tracked
On Fri, Apr 5, 2019 at 12:53 PM Harald Dunkel
wrote:
> Hi Lennart,
>
> On 4/5/19 10:28 AM, Lennart Poettering wrote:
> >
> > For some reason a number of X session processes stick around to the
> > very end and thus keep your /home busy.
> >
> > [82021.052357] systemd-shutdown[1]: Sending SIGKILL
On Do, 04.04.19 09:41, Kay One (kayone...@gmail.com) wrote:
> Hello Folks,
>
> I am consistently receiving following error on my ARM Core Box and couldn't
> figure out what's going on my linux. Verified all the possible solutions
> available on all forums but no luck till date.
> Can you please
On Fr, 05.04.19 11:53, Harald Dunkel (harald.dun...@aixigo.de) wrote:
> Hi Lennart,
>
> On 4/5/19 10:28 AM, Lennart Poettering wrote:
> >
> > For some reason a number of X session processes stick around to the
> > very end and thus keep your /home busy.
> >
> > [82021.052357] systemd-shutdown[1]:
Hi Lennart,
On 4/5/19 10:28 AM, Lennart Poettering wrote:
For some reason a number of X session processes stick around to the
very end and thus keep your /home busy.
[82021.052357] systemd-shutdown[1]: Sending SIGKILL to remaining processes...
[82021.101976] systemd-shutdown[1]: Sending
On 4/5/19 8:45 AM, Mantas Mikulėnas wrote:
Normally I'd expect user sessions (user-*.slice, session-*.scope,
user@*.service) to be killed before mount units are stopped; I wonder how
random gpg-agent processes have managed to escape that. (Actually, doesn't
Debian now manage gpg-agent via
On Fr, 05.04.19 08:28, Harald Dunkel (harald.dun...@aixigo.de) wrote:
65;5403;1c
> Hi folks,
>
> I've got a device-busy-problem with /home, mounted via NFS.
> Shutdown of the host takes more than 180 secs. See attached
> log file.
>
> Apparently the umount of /home at 81925.154995 failed, (device
Am Fr., 5. Apr. 2019 um 08:45 Uhr schrieb Mantas Mikulėnas :
> The job order (home.mount vs nfs-client.target) already looks correct, so
> fstab options probably won't help much; I'd try to ensure that the umount
> doesn't fail in the first place.
>
> Normally I'd expect user sessions
On Fri, Apr 5, 2019 at 9:28 AM Harald Dunkel
wrote:
> Hi folks,
>
> I've got a device-busy-problem with /home, mounted via NFS.
> Shutdown of the host takes more than 180 secs. See attached
> log file.
>
> Apparently the umount of /home at 81925.154995 failed, (device
> busy, in my case it was a
Hi folks,
I've got a device-busy-problem with /home, mounted via NFS.
Shutdown of the host takes more than 180 secs. See attached
log file.
Apparently the umount of /home at 81925.154995 failed, (device
busy, in my case it was a lost gpg-agent). This error was
ignored, the NFS framework was
11 matches
Mail list logo
