Closing.
]]>Do not necrobump old threads, especially solved ones.
Closed (edit: too slow ... but damnit, the timestamps are the same down to the second.)
]]>The problem was due to SELinux preventing NetworkManager from mounting the directory.
The steps to correct the problem:
Changing SELinux to permissive mode in /etc/selinux/config
reboot
grep NetowrkManager_t /var/log/audit/audit.log | audit2allow -M nm_mount
selinux -i nm_mount.pp
Change SELinux back to enforcing in /etc/selinux/config
reboot
You should look at the nm_mount.te to see what it's doing before you blindly allow the new module. If there is anything along the lines of this, you will want to relabel the directory you're mounting to first:
#!!!! WARNING: 'home_root_t' is a base type.
See Think before you just blindly audit2allow -M mydomain for more info on that.
]]>NetworkManager[251]: <warn> Dispatcher script failed: Script '/etc/NetworkManager/dispatcher.d/nfs.sh' exited with error status 32
Soooorryyyy.
]]>kaipee wrote:Thanks gonX, so NetworkManager output "status" corresponds to variable $2. I see now.
If I get it right, 'status' is $1.
$ echo "echo $0
echo $1
echo $2" > /tmp/bashscript
$ chmod +x /tmp/bashscript
$ /tmp/bashscript Hi Mate
/tmp/bashscript
Hi
Mate
Said in another way, no, status is $2, and interface is $1.
]]>Thanks gonX, so NetworkManager output "status" corresponds to variable $2. I see now.
If I get it right, 'status' is $1.
]]>You've just confused me even more by not explaining how this relates to the networkmanager script
NetworkManager passes "interface" and "status", respectively, where "status" can be 'up' or 'down. Interface should be self-explanatory
]]>Example what the positional arguments mean:
$ cat aaa
#!/bin/bash
echo $0 $1 $2
$ ./aaa one two three
./aaa one two
$ ./foo bar baz
foo = $0
bar = $1
baz = $2