What are all of these PID files doing in my home directory?
$ ls -1 ~/upstart-*
/home/mark/upstart-dbus-bridge.4885.pid
/home/mark/upstart-file-bridge.4885.pid
/home/mark/upstart-udev-bridge.10317.pid
/home/mark/upstart-udev-bridge.4885.pid
/home/mark/upstart-udev-bridge.6044.pid
/home/mark/upstart-udev-bridge.6406.pid
/home/mark/upstart-udev-bridge.6650.pid
Most are current. If I try to remove them, they will (eventually) come back (albeit with new IDs, etc.).
ps
shows the following, for example:
4 S mark 4885 5319 0 80 0 - 27317 poll_s Nov21 ? 00:00:00 /sbin/upstart --user
The same is happening for other users on the same system as well.
Per Jos's comment, the setups of /run
/ /var/run
appear to be correct:
$ mount|grep run
tmpfs on /run type tmpfs (rw,nosuid,noexec,relatime,size=1633648k,mode=755)
tmpfs on /run/lock type tmpfs (rw,nosuid,nodev,noexec,relatime,size=5120k)
$ ll /var/run
lrwxrwxrwx 1 root root 4 Oct 28 2013 /var/run -> /run/
Surely this isn't by design, or that there must be a better place to keep these? As-is, they are not hidden files, nor are they in a hidden directory. This is messy, and result in a longer listing of things I need to look through in what should otherwise be a very clean and organized ~
.
I think this started after one of my last upgrades which included systemd. Is this typical, or do I maybe have something else here influencing this that I need to further investigate? (I have gotten a bit lazy here on this system, and haven't performed a clean install for the past few releases - maybe time for a clean install?)
$ cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=15.10
DISTRIB_CODENAME=wily
DISTRIB_DESCRIPTION="Ubuntu 15.10"
(This would seem to be something that should be resolved by a simple search, but my Google-fu appears to be failing me with this concern.)
pid
files ought to be created in/var/run
which is a symbolic link to/run
. They are written every time you connect an USB device. I suspect the/run
folder, in itself atmpfs
file system, is accidentally mounted in your home directory. Please edit your question and add the output ofmount
(ormount | grep run
).upstart-udev-bridge
process and the others are not executed as root, and are therefore not allowed to write the pid file to/var/run
; they fall back to writing it to the user's home directory.