Page 3 of 3

Re: Auto-logout after weekly update [Solved]

Posted: Fri Dec 14, 2018 0:17
by albfneto
I carried an full upgrade, today, 12/13/2018.
This is only to inform that i not had problem with the new version of systemd.
My system is fully working like a cham!

Re: Auto-logout after weekly update [Solved]

Posted: Thu Jan 03, 2019 17:41
by mamaq
I want to update my system, but realized that the system don't has the link from /var/run to /run.
Do I still need to delete /var/run and create the symlink?
Also can I remove /var/run without creating further problems, if I perform a diff between /var/run and /run, I get the following output and some files only exists in /var/run.

Code: Select all

Files /var/run/utmp and /run/utmp differ
Only in /run: agetty.reload
Only in /run: autofs.fifo-mnt-NAS
Only in /run: autofs.pid
Only in /run: autofs-running
Only in /run: brltty
Only in /run: cups
Only in /run/entropy: .entropy.client.interfaces.repository.lock
Only in /run/entropy: .entropy.security.System.lock
Only in /run/entropy: repository
Only in /run: initramfs
Only in /run: libvirt
Only in /run: lock
Only in /run: log
Only in /run: lvm
Only in /run: mount
Only in /run: nscd
Only in /run: openldap
Only in /run: rpcbind.sock
Only in /run: saslauthd
Only in /run: systemd
Only in /run: tmpfiles.d
Only in /run: udev
Only in /run: udisks2
Only in /run: user
Only in /run: xtables.lock
Only in /var/run: avahi-daemon
Only in /var/run: connman
Only in /var/run: cron.pid
Only in /var/run: dbus
Only in /var/run: dictd.pid
Only in /var/run: docker
Only in /var/run: docker.sock
Only in /var/run: equo.pid
Only in /var/run: ifplugd.eth0.pid
Only in /var/run: .keep
Only in /var/run: lightdm
Only in /var/run: lightdm.pid
Only in /var/run/mdadm: map
Only in /var/run: mysqld
Only in /var/run: pcscd
Only in /var/run: resolvconf
Only in /var/run: rpc.statd.lock
Only in /var/run: screen
Only in /var/run: sshd.pid
Only in /var/run: wpa_supplicant

Re: Auto-logout after weekly update [Solved]

Posted: Thu Jan 03, 2019 17:47
by joost
mamaq wrote:
Thu Jan 03, 2019 17:41
I want to update my system, but realized that the system don't has the link from /var/run to /run.
Do I still need to delete /var/run and create the symlink?
Also can I remove /var/run without creating further problems, if I perform a diff between /var/run and /run, I get the following output and some files only exists in /var/run.

Code: Select all

Files /var/run/utmp and /run/utmp differ
Only in /run: agetty.reload
Only in /run: autofs.fifo-mnt-NAS
Only in /run: autofs.pid
Only in /run: autofs-running
Only in /run: brltty
Only in /run: cups
Only in /run/entropy: .entropy.client.interfaces.repository.lock
Only in /run/entropy: .entropy.security.System.lock
Only in /run/entropy: repository
Only in /run: initramfs
Only in /run: libvirt
Only in /run: lock
Only in /run: log
Only in /run: lvm
Only in /run: mount
Only in /run: nscd
Only in /run: openldap
Only in /run: rpcbind.sock
Only in /run: saslauthd
Only in /run: systemd
Only in /run: tmpfiles.d
Only in /run: udev
Only in /run: udisks2
Only in /run: user
Only in /run: xtables.lock
Only in /var/run: avahi-daemon
Only in /var/run: connman
Only in /var/run: cron.pid
Only in /var/run: dbus
Only in /var/run: dictd.pid
Only in /var/run: docker
Only in /var/run: docker.sock
Only in /var/run: equo.pid
Only in /var/run: ifplugd.eth0.pid
Only in /var/run: .keep
Only in /var/run: lightdm
Only in /var/run: lightdm.pid
Only in /var/run/mdadm: map
Only in /var/run: mysqld
Only in /var/run: pcscd
Only in /var/run: resolvconf
Only in /var/run: rpc.statd.lock
Only in /var/run: screen
Only in /var/run: sshd.pid
Only in /var/run: wpa_supplicant
viewtopic.php?f=86&t=34902&hilit=%2Frun#p182998