Hi,
> Andreas Kloeckner <inf...@tiker.net> writes: > > Michael Biebl <bi...@debian.org> writes: > > > >> [ Unknown signature status ] > >> Am 10.09.2016 um 02:27 schrieb Andreas Kloeckner: > >>> Package: systemd > >>> Version: 231-4 > >>> Severity: normal > >>> > >>> Dear Maintainer, > >>> > >>> on my system, the following happens (from journalctl -e) on trying to > start the > >>> services in the subject. > >>> > >>> -------------------------------------- > >>> Sep 09 19:04:17 bolt systemd[2685]: systemd-hostnamed.service: Failed > at step NAMESPACE spawning /lib/systemd/systemd-hostnamed: Too many levels > of symbolic links > >> > >> Is /home or /tmp a symbolic link? > >> How exactly does the /var/run symlink look like > >> > >> Please post the output of > >> # ls -ld /home /tmp /var/run > > > > Thanks for your response! > > > > # ls -ld /home /tmp /var/run > > drwxr-xr-x 3 root root 4096 Jun 25 13:38 /home > > drwxrwxrwt 13 root root 36864 Sep 10 11:40 /tmp > > lrwxrwxrwx 1 root root 5 Sep 9 19:25 /var/run -> /run/ > So, it turns out that my /root directory was a symlink. And that's what > was causing all this grief. Fixed now, thanks for your help. > Andreas I've also been bitten by this bug, in my case /home was a symlink. Upstream reports the bug as closed[1] few weeks ago, but it seems to be still present in latest Debian package (231-10). Can anyone confirm that this patch is included in that version, or will it be included in a future one? [1] https://github.com/systemd/systemd/issues/567 Thanks, -- Antonio Trueba atga...@gmail.com
