Description of problem: Mount of network windows directory does not occur. Version-Release number of selected component (if applicable): $ uname -a Linux PC-Linux 2.6.40.4-5.fc15.i686 #1 SMP Tue Aug 30 14:54:41 UTC 2011 i686 i686 i386 GNU/Linux $ rpm -qa|grep cifs cifs-utils-5.0-2.fc15.i686 How reproducible: It's reproducible trying to automatically mount a directory to exist on a windows server. In my case the server is windows server 2003 R2. By adding the appropriate line in /etc/fstab (as shown in the attachments) is not the mount. At boot time you have error messages and you can not enable this option. View attachments. Steps to Reproduce: 1. 2. 3. Actual results: Circumvented the problem by writing in /etc/rc.local the line "systemctl start mnt-server.mount". Mount the partition but it still happens at boot errors. Expected results: Additional info: These are the posts before adding the line in / etc / rc.local Starting /mnt/server [1;31mfailed[0m, see 'systemctl status mnt-server.mount' for details. [root@PC-Linux ~]# systemctl status mnt-server.mount mnt-server.mount - /mnt/server Loaded: loaded Active: failed since Tue, 30 Aug 2011 16:22:32 +0200; 13min ago Where: /mnt/server What: /192.168.2.250/dati Process: 812 ExecMount=/bin/mount /mnt/server (code=exited, status=32) CGroup: name=systemd:/system/mnt-server.mount [root@PC-Linux ~]# These are the messages after adding the line in / etc / rc.local [root@PC-Linux ~]# systemctl status mnt-server.mount mnt-server.mount - /mnt/server Loaded: loaded Active: active (mounted) since Wed, 07 Sep 2011 12:50:54 +0200; 4h 17min ago Where: /mnt/server What: //192.168.2.250/dati CGroup: name=systemd:/system/mnt-server.mount [root@PC-Linux ~]#
Created attachment 521907 [details] Network situation and mount situation
do you use networkmanager? Normally we don't delay boot for the network. if you want such a behaviour you have to manually enable that via "systemctl enable NetworkManager-wait.service".
I think that the network connections you should start automatically. Manually enabling enable "systemctl NetworkManager-wait.service" allows to start automatically the next time? Using Network instead Network Manager, the situation would change?
Not sure I grok your questions. Does "sc e NM-w.s" make things work for you?
[root@PC-Linux ~]# systemctl enable NetworkManager-wait.service Couldn't find NetworkManager-wait.service. [root@PC-Linux ~]# I think is not working.
It's NetworkManager-wait-online.service
All right. This works. It would be good to have it already running when you establish a network connection automatically.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.