Another workaround, systemd-based, because yes it still happens on
Xenial :
$ systemctl edit my-mount-point.mount
[Unit]
After=glusterfs-server.service
Wants=glusterfs-server.service
$ systemctl cat my-mount-point.mount
# /run/systemd/generator/my-mount-point.mount
# Automatically generated by
I confirm this bug on a freshly installed Ubuntu 12.04.2. However, it
does not appear on an apparently similarly configured (yet older,
probably installed as a 12.04.1) machine.
root@okserver:~# cat /proc/2761/stat
2761 (apache2) S 16432 16432 16432 0 -1 4202816 62931 0 23 0 446 35 0 0 39 19 1
0
I confirm this bug on a freshly installed Ubuntu 12.04.2. However, it
does not appear on an apparently similarly configured (yet older,
probably installed as a 12.04.1) machine.
root@okserver:~# cat /proc/2761/stat
2761 (apache2) S 16432 16432 16432 0 -1 4202816 62931 0 23 0 446 35 0 0 39 19 1
0
This also happens with apache2-mpm-worker
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1008385
Title:
apache-mpm-itk writes wrong process name in /proc/$$/status
To manage notifications about
To complete on the first point of the initial post (what keys are seen
by seahorse), what i've found (it's hidden somewhere on the seahorse
pages at live.gnome.org) is that seahorse will only take into account
keys beginning with id_rsa or id_dsa
I was using a key named id_vpn in my .ssh folder
