Am 2014-10-02 17:44, schrieb Michael Biebl: > Am 02.10.2014 um 17:34 schrieb Jakob Schürz: >> I get this message (debug systemd on boot, writing to dmesg) >> >> [ 29.064987] systemd[1]: Got direct mount request on >> /var/cache/backup, triggered by 1771 (mountpoint) > > If I read that correct, it's the mountpoint binary. > You might start grepping for mountpoint in your /etc directory. Maybe > that turns something up.
Ok... I didn't know a Binary called mountpoint. :) Now i know ist. And a grep in /etc for "mountpoint" gave me root@pluto[23:05]:/etc # grep mountpoint * -R grep: warning: alternatives/glx/libGL.so-master: Rekursive Verzeichnisschleife. Übereinstimmungen in Binärdatei alternatives/php. grep: warning: alternatives/libGL.so-master/libGL.so-master: Rekursive Verzeichnisschleife. ca-certificates/update.d/jks-keystore:if ! mountpoint -q /proc; then complete.tcsh: complete attach 'n/-mountpoint/d/' 'n/-m/d/' 'n/-type/(afs nfs rvd ufs)/' \ complete.tcsh: mountpoint noexplicit explicit type mountoptions \ grep: cups/ssl/server.key: Datei oder Verzeichnis nicht gefunden default/cryptdisks:# mountpoints by space. init.d/udev: if mountpoint -q /dev/pts/; then init.d/udev: if mountpoint -q /dev/shm/; then init.d/udev: mountpoint -q /run/ || return 0 init.d/udev: if mountpoint -q /dev/; then init.d/mountnfs.sh: while ! mountpoint -q $mountpt; do init.d/dbus: if ! mountpoint -q /proc/ ; then init.d/checkroot.sh: ddev="$(mountpoint -qx $rootdev)" init.d/checkroot.sh: rdev="$(mountpoint -d /)" init.d/checkroot.sh: if [ "$(mountpoint -qx /dev/root)" = "4:0" ] rc2.d/S19dbus: if ! mountpoint -q /proc/ ; then rc3.d/S19dbus: if ! mountpoint -q /proc/ ; then rc4.d/S19dbus: if ! mountpoint -q /proc/ ; then rc5.d/S19dbus: if ! mountpoint -q /proc/ ; then rcS.d/S17mountnfs.sh: while ! mountpoint -q $mountpt; do rcS.d/S07checkroot.sh: ddev="$(mountpoint -qx $rootdev)" rcS.d/S07checkroot.sh: rdev="$(mountpoint -d /)" rcS.d/S07checkroot.sh: if [ "$(mountpoint -qx /dev/root)" = "4:0" ] rcS.d/S02udev: if mountpoint -q /dev/pts/; then rcS.d/S02udev: if mountpoint -q /dev/shm/; then rcS.d/S02udev: mountpoint -q /run/ || return 0 rcS.d/S02udev: if mountpoint -q /dev/; then smbnetfs.conf:# PS: You can use "cd mountpoint/domain:user:password@computer" grep: systemd/system/network-online.target.wants/home-user-dir1-dir2-dir3-dir4.automount: Datei oder Verzeichnis nicht gefunden grep: systemd/system.back/backup-automount.target.wants/var-cache-backup.automount: Datei oder Verzeichnis nicht gefunden grep: systemd/system.back/home-user-Musik-System\x2dServer.device.requires/[email protected]: Datei oder Verzeichnis nicht gefunden And tadaaa, "mountpoint" is the devil. When i look on the result above, it could only be "init.d/mountnfs.sh" so i try to deactivate nfs-mounts, and report what happens. > >> But i have no idea, what process 1771 is... >> >> Another guy in debianforum.de has the same effect. And i don't know, >> which process wants access to the automount-ponts on bootup? How can i >> find this out? >> >> And the mounting of this automount-points on boottime only happens, >> when >> systemd is involved... Try it on your own. > > Well, obviously. automounts are systemd specific. If this is true, what i thought before, then it's a fault in design. And further u think it's a good aproach, that more intelligent people think about this. Because I think I'm not the only one with this problem. And a "noauto" in fstab should be exact this - even with automount-option. regards Jakob -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
