X-systemd.automount nfs drive

Hi,
I can't seem to get systemd.automount to behave. I have an nfs share available on machine 'kombi' and am trying to access it from machine 'forrest':
[root@forrest ~]# showmount -e kombi
Export list for kombi:
/mnt/nfs4/georgia 192.168.1.202
/mnt/nfs4 192.168.1.202
It is set up to automount in /etc/fstab:
kombi:/georgia /mnt/georgia nfs4 rw,suid,dev,exec,noauto,nouser,async,clientaddr=192.168.1.202,_netdev,x-systemd.automount,x-systemd.device-timeout=8 0 0
Logging output from journalctl indicates it timed out but then mounted:
Dec 14 17:45:11 forrest systemd[1]: mnt-georgia.mount mounting timed out. Stopping.
Dec 14 17:45:11 forrest systemd[1]: Mounted /mnt/georgia.
Dec 14 17:45:11 forrest systemd[1]: Mounted /mnt/georgia.
However it is not mounted. Any process trying to access /mnt/georgia hangs.
Any ideas where I have gone wrong? I don't care if it automounts at boot or at first access. What I'd like is for it to gracefully handle mounting when 'kombi' is up, and unmounting when 'kombi' is down.

Thanks, I guess I have misread other advice on the forums. Even systemd.mount man page states:
If x-systemd.device-timeout= is specified it may be used to configure how long systemd should wait for a device to show up before giving up on an entry from /etc/fstab.
From this statement I would expect the remote filesystem to not be mounted if the other machine is down, but not to cause a local process to hang trying to access the unmounted directory.
It looks like autofs may be the way to go - from the NFS wiki:
Using autofs is useful when multiple machines want to connect via NFS; they could both be clients as well as servers. The reason this method is preferable over the earlier one is that if the server is switched off, the client will not throw errors about being unable to find NFS shares.

Similar Messages

Can systemd automounter unmount inactive fileystems?

Hi,
tl;dr: Can systemd automounter unmount fileystems after a period of inactivity, like autofs does?
I've just started discovering the wonderful new world of systemd, and to my great joy I found that it contains an automounter, so I thought that I would be able to use that instead of using autofs.
The single thing that I like to automount is my home NAS on my laptop (via NFSv4) that I every day take from home to work and then back home.
To do this with autofs is kind of like killing mosquitoes with a flamethrower. I would much rather just have my automounted NAS defined in my fstab than having to force the slightly mysterious autofs.xxx-files to mount the drive with the options I want it to use.
So, I got systemd to automount my NAS and all was joy! Until I realized that it wasnt unmounting it after a time of non-use. I have googled quite a bit, searched the forums, but have found no mention that systemd either has or doesnt have this kind of functionality.
So my purpose with this post is to get a definitive answer, does systemd do this? And if it doesn't, maybe others searching for the same information will end up here, and find the answer...
/DonO

I've been having this problem for as long as I can remember. I have finally decided to sit down and work something out instead of my laptop hanging all the time when it can't find the nfs server. The systemd.automount feature is nice, but it really sucks that it does not auto unmount when the share is not found.
Also, having systemd.automount means that every time I open vim, or a manpage, and there is no network connection, systemd tries to mount the shares. I'm not sure why because I am not directly accessing them. Everything loads slowly when systemd automount is active for my shares and there is no network connection.
Using soft instead of hard is a workaround, but then when the network connection is lost, corruption can occur.
It seems like the only way to really solve this problem is to have some kind of script run when the network comes up to mount the shares, and to unmount when it goes down. This would require custom systemd units or something. Diving into the systemd manuals is something I have been putting off because they are so hefty.
For anyone that is interested, here is my fstab:
lithium:/mnt/data /mnt/data nfs noauto,noatime,rsize=32768,wsize=32768,soft,retry=0,timeo=3,x-systemd.automount,x-systemd.device-timeout=1ms 0 0
lithium:/var/cache/pacman /var/cache/pacman nfs noauto,noatime,rsize=32768,wsize=32768,soft,retry=0,timeo=3,x-systemd.automount,x-systemd.device-timeout=1ms 0 0
Last edited by demizer (2013-07-14 09:00:23)

Questions: 10-keymap.fdi not working // automounting ntfs drives // ++

Hi there,
this time I want to change 100% from windows to linux and i found archlinux to be a really nice system.
I like it "the arch way"
1) I followed the beginner's wiki and choose those xf86-input-evdev 2.3.2-1 drivers.
I set the 10-keymap.fdi file
<merge key="input.xkb.layout" type="string">de</merge>
<merge key="input.xkb.variant" type="string" />nodeadkeys</merge>
</match>
</device>
</deviceinfo>
The problem is, that the layout doesn't change to 'de'
I put
setxkbmap de -variant nodeadkeys &
into my.xinitrc, but this is not a good solution, because when logging in with SLIM there is still the english layout (e.g. for passwords with an "y" i have to press "z" because y and z are swaped in de / en layout .)
So what can I do? Is my 10-keymap.fdi somehow wrong?
2)
I would like to use my windows ntfs partitions in arch, so I installed ntfs-3g. Manual mounting with "mount -t ntfs-3g /dev/sd.. /mnt/... " works, but how can I manage that arch mounts everything it finds automaticly on startup and while running (e.g adding an usb drive)?
I installed "hal" but nothing is mounted on startup (/mnt is empty?)
3)
I saw there is a "netfs" daemon in my rc.conf
I googled it and I read it is for unix network.
When I install samba later, should I remove it then? (samba can do windows and unix both right?)
4)
I use openbox (and would like to continue using it). Is it possible to make windows "snap" to the edge and take half screen like in Windows 7 ?
And are there any commands or something like that to rearrange windows on the screen, for example "show all windows side by side" or "sorted" ?
This is my rc.conf
http://pastebin.com/fvj7cBVp
>> Thank you for you help! <<
Last edited by cyberius (2010-05-30 14:53:17)

1)
replace ...
hi
thanks, it worked!
2)
use udev rules or autofs.
are udev rules and autofs two different ways of automounting devices?
i'm not shure, but i think i read on beginners wiki somewhere that hal automounts my drives?
hal, udev, autofs.. i'm confused
hm i read http://wiki.archlinux.org/index.php/Udev and created those files (with content) as they are written in the wiki
/etc/udev/rules.d/11-media-by-label-auto-mount.rules
/etc/udev/rules.d/10-my-media-automount.rules
/etc/udev/rules.d/11-sd-cards-auto-mount.rules
sadly nothing happend (i didnt see any mounted partition in /media or /mnt.. after reboot)
i know that
ls /dev/sd
sda sda1 sda2 sdb sdb1
those should be my windows partitions
did i miss somethingor should i better try autofs?
Last edited by cyberius (2010-05-30 14:54:42)

Stop systemd.service by other systemd.service (nfs)

Hi there,
I'm currently tweaking my nfs setup.
What do I want
Mount my exported directories via bind to export, when the nfs-server starts. And unmount the directories on stop of the nfs-server
Approach
/etc/systemd/system/nfs.target
[Unit]
Description=Network File System Server
Wants=export-daten.mount export-daten-Downloads.mount export-portage.mount export-root.mount export-root-boot.mount
Requires=nfs-server.service
BindsTo=nfs-server.service
[Install]
WantedBy=multi-user.target
/etc/systemd/system/export-daten.mount
[Unit]
Description=/home/blubb/Daten nach /export/daten
BindsTo=nfs-server.service
StopWhenUnneeded=true
[Mount]
What=/home/blubb/Daten
Where=/export/daten
Options=bind
[Install]
WantedBy=nfs.target
ls nfs.target.wants
export-daten-Downloads.mount export-daten.mount export-portage.mount export-root-boot.mount export-root.mount
nfs-server.service is the original one shipped by Arch in /usr/lib/systemd/system.
Current behaviour
start nfs.target: mounts directories, starts nfs-server
stop nfs.target: unmounts directories, doesn't stop nfs-server
start nfs-server.service fails, because can't export /export/daten/Downloads, which doesn't exist, because the mount-units were not processed.
stop nfs-server.service: umount directories (due to the BindsTo directive) and stops the nfs.target.
Desired behaviour
The current behaviour works, but isn't very clean. Would be nice, if nfs.target stops the nfs-server.service too. I don't want nfs-server.service copy to /etc and modify as I will miss any updates of the original unit in /usr/lib.
Is it possible to stop nfs-server.service in/by nfs.target?

Tanks, works so far. One problem is left.
For some reason, nfs option nohide doesn't work. So I have to export other filesystems in subtree too. My 2 units:
export-daten.mount
[Unit]
Description=/home/sm/Daten nach /export/daten
BindsTo=nfs-server.service
StopWhenUnneeded=true
[Mount]
What=/home/sm/Daten
Where=/export/daten
Options=bind
[Install]
WantedBy=nfs.target
and the filesystem, which is mounted in there:
export-daten-Downloads.mount
[Unit]
Description=/home/sm/Daten/Downloads nach /export/daten/Downloads
BindsTo=nfs-server.service
Requires=export-daten.mount
StopWhenUnneeded=true
[Mount]
What=/home/sm/Daten/Downloads
Where=/export/daten/Downloads
Options=bind
[Install]
WantedBy=nfs.target
According to the Manpage I'm not sure, if the Requires option is even recognized. Mounting works. But when I stop my nfs-server, I get this message:
journalctl
Feb 12 07:23:53 Nas systemd[1]: Stopping Network File System Server.
Feb 12 07:23:53 Nas systemd[1]: Stopped target Network File System Server.
Feb 12 07:23:53 Nas systemd[1]: Unit export-daten-Downloads.mount is not needed anymore. Stopping.
Feb 12 07:23:53 Nas systemd[1]: Unit export-portage.mount is not needed anymore. Stopping.
Feb 12 07:23:53 Nas systemd[1]: Unit export-root-boot.mount is not needed anymore. Stopping.
Feb 12 07:23:53 Nas systemd[1]: Unmounting /boot nach /export/root/boot...
Feb 12 07:23:53 Nas systemd[1]: Unit export-root.mount is not needed anymore. Stopping.
Feb 12 07:23:53 Nas systemd[1]: Unmounting /var/portage nach /export/portage...
Feb 12 07:23:53 Nas systemd[1]: Stopping NFS server and services...
Feb 12 07:23:53 Nas systemd[1]: Unmounting /home/sm/Daten/Downloads nach /export/daten/Downloads...
Feb 12 07:23:53 Nas systemd[1]: Unit export-daten.mount is not needed anymore. Stopping.
Feb 12 07:23:53 Nas systemd[1]: Unit export-root-home-sm-Daten-Downloads.mount entered failed state.
Feb 12 07:23:53 Nas kernel: nfsd: last server has exited, flushing export cache
Feb 12 07:23:53 Nas systemd[1]: Unmounted /boot nach /export/root/boot.
Feb 12 07:23:53 Nas systemd[1]: Unit export-root.mount is not needed anymore. Stopping.
Feb 12 07:23:53 Nas systemd[1]: Unmounted /var/portage nach /export/portage.
Feb 12 07:23:53 Nas systemd[1]: Unmounted /home/sm/Daten/Downloads nach /export/daten/Downloads.
Feb 12 07:23:53 Nas systemd[1]: Unit export-daten.mount is not needed anymore. Stopping.
Feb 12 07:23:53 Nas systemd[1]: Stopped NFS server and services.
Feb 12 07:23:53 Nas systemd[1]: Stopping NFS Mount Daemon...
Feb 12 07:23:53 Nas rpc.mountd[21709]: Caught signal 15, un-registering and exiting.
Feb 12 07:23:53 Nas systemd[1]: Unmounting /home/sm/Daten nach /export/daten...
Feb 12 07:23:53 Nas systemd[1]: Unmounting / nach /export/root...
Feb 12 07:23:53 Nas systemd[1]: Stopped NFS Mount Daemon.
Feb 12 07:23:53 Nas systemd[1]: Unmounted /home/sm/Daten nach /export/daten.
Feb 12 07:23:53 Nas systemd[1]: Unmounted / nach /export/root.
Manpage:
If a mount point is beneath another mount point in the file system hierarchy, a dependency between both units is created automatically.
It seems, that works for mounting, but not for the umount.
Can I do something to unmount that stuff cleaner?

Systemd and nfs-common ?

My nfs-client setup takes 62s to mount a nfsv4 share. I've tried to solve this by creating an own systemd nfs-common.service but it fails. It doesn't see rpcbind as started, which it is. I've googled high and low for a systemd *.service that works but haven't any nfs-common.service file at all.
I have ExecStart=/etc/rc.d/nfs-common start in my .service file and it is enabled but status message is;
nfs-common.service - nfs-common
Loaded: loaded (/etc/systemd/system/nfs-common.service; enabled)
Active: failed (Result: exit-code) since Sat, 19 May 2012 12:25:43 +0200; 10min ago
Process: 1911 ExecStart=/etc/rc.d/nfs-common start (code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/nfs-common.service
sudo /etc/rc.d/nfs-common start gives;
Start rpcbind first. [FAIL]
Same as in journal systemd-journalctl | grep -i nfs;
May 19 12:14:09 mediadatorn kernel: RPC: Registered tcp NFSv4.1 backchannel...e.
May 19 12:14:09 mediadatorn kernel: FS-Cache: Netfs 'nfs' registered for caching
May 19 12:14:10 mediadatorn[103]: Inserted module 'nfs'
May 19 12:14:11 mediadatorn nfs-common[227]: Start rpcbind first. [FAIL]
All this came about since I started trying to optimize systemd. Before today, when I tried to disable all legacy arch units, I had the nfs client running ok. I did this after reading falconindys tip in the big systemd thread. By the way, that thread is so big it has become nearly useless.
Boot up times:
systemd-analyze
Startup finished in 13269ms (kernel) + 94810ms (userspace) = 108080ms
systemd-analyze blame
62034ms mnt-SERVER_NYTT.mount
6764ms console-kit-daemon.service
2787ms systemd-modules-load.service
1838ms home.mount
867ms syslog-ng.service
552ms rpc-statd.service

swanson wrote:
I followed this
falconindy wrote:
arch-daemons.target. Sadly, it's going to be a little longer than I wanted until that unit disappears. That said, the intended usage of that target was never meant to be more than:
1) Install systemd, initscripts-systemd, systemd-arch-units (arch-daemons.target is enabled)
2) reboot
3) copy /run/systemd/generator/arch-daemons.target.wants/*.service to /etc/systemd/system for anything where a native unit file doesn't exist
4) kill -1 1 (refreshes systemd's unit database)
5) systemctl enable *.service (for the services you copied over in step 3)
6) disable arch-daemons.target
7) ????
8) profit.
(finally found it)
Right now I'm trying to reverse it and start over.
I tried this, and immediately didn't get it to mount. I restarted rpcbind (supposedly already running) and nfs-common and I think it still stalled on mounting, but now I that I've been away from it, it finally did mount.
Last edited by nomorewindows (2012-06-24 00:09:47)

X-systemd.automount and sshfs

I've been using sshfs to access files on my pi for serveral months now. Today i tried to enable automatic mounting with x-systemd.automount, but although a manual mount is still possible, the automatic mount fails constantly with a "no such device" error since i added the additional option in /etc/fstab. Journalctl -f on the pi reveals that the "Connection is closed [preauth]", so I would guess that something is wrong with my client authenticating. But I don't understand how is this possible because I can in fact mount the partition manually. Even if I use the exact command used by systemd (found via ps -fe) with root it prompts me for the password of my key and then it mounts correctly. Shouldn't automount then prompt for my password, when my X starts? Any ideas?
line in /etc/fstab:
herrzinter-pi.local:/media/mediacrypt /home/herrzinter/Multimedia fuse.sshfs users,noauto,_netdev,reconnect,x-systemd.automount 0 0
Last edited by MrTea (2013-07-01 15:34:13)

WonderWoofy is right, until now I always used the automatically generated nautilus entry to mount the remote folder. In this case mount command is executed as <user> and so I don't need to put the additional information in the /etc/fstab. btw i didn't exactly look this up, but I've used this setup for quiet some time now, and I guess, that I forgot the herrzinter@ part once and noted that it worked anyway
I now added this and the "IdentityFile=/..." option pointing to a dummy ssh key without passphrase and it then it's working, but I am not to happy with this, as an empty passphare key is not really nice, and also nautilus is showing me duplicated entries... but in genreal I have to look at the setup again I am not sure anymore if the x-systemd.automount option is really such a good idea in my case, as the network setup of my laptop is changing quite often... perhaps a bash script at login, or a custom systemd unit is better suited for my purpose
Thank you all anyway

Mounted local NFS drives take down Finder after move out of network

Hello,
This is a basic scenario that happens to me often. At home, I mount several NFS drives from my linux server. They work fine. If i close my MBP, don't shutdown, and take it with me to a new location outside of my local network, I still see my NFS drives mounted. After a while, I will get a prompt saying that those drives are no longer available, or some such language.
However, if I try and unmount them from the finder or try and access those drives, the is Finder done for, and all computer functions for that matter, like volume, brightness.
I have left it that way for up a half-hour before hard re-starting.
I know I should unmount the drives before I take the computer with me, but honestly, I will continue to forget.
Is there a way to avoid this, like setting a timeout of a 1 minute or so, if the drive is not available?
Thanks for your time,
Chuck
MBP Mac OS X (10.4.9)

Hello,
This is a basic scenario that happens to me often. At home, I mount several NFS drives from my linux server. They work fine. If i close my MBP, don't shutdown, and take it with me to a new location outside of my local network, I still see my NFS drives mounted. After a while, I will get a prompt saying that those drives are no longer available, or some such language.
However, if I try and unmount them from the finder or try and access those drives, the is Finder done for, and all computer functions for that matter, like volume, brightness.
I have left it that way for up a half-hour before hard re-starting.
I know I should unmount the drives before I take the computer with me, but honestly, I will continue to forget.
Is there a way to avoid this, like setting a timeout of a 1 minute or so, if the drive is not available?
Thanks for your time,
Chuck
MBP Mac OS X (10.4.9)

Mounting NFS Drive limitations when using the GUI?

I mounted a NFS drive in the "Workgroup Manager" and I can't turn on Enable Access Control Lists on this volume" (ACL). Because I don't have ACL on I can't share this volume well using Samba.
When trying to turn ACL on I get this error: "kErrorChangingACLState"
However; if I go under the hood of OSX, and mount the NFS volume via Terminal I inherited ACL support. I am not sure if this is dangerous but I can now share the NFS file structure and Samba happily lets the proper people access.
It seems that ACL is very important to have Windows allow Group access. POSIX support only lets "Everyone" and "User" access. It seems to know that the files is part of the correct group but Windows won't let you on.
Does anyone know why one can't force the NFS volume in the GUI to have ACL support?
-Hays

Thanks cjlim for chiming in.
This is coming from a Nokia representative in one Disqus forum:
We've seen many people from US asking for this feature. Right now you can get a direction list before starting your journey, with HERE Maps. From there you can then launch HERE Drive. In HERE Drive you have a map instead, which should show you where it is going to take you. Otherwise we believe that reading a direction list while driving is highly distracting and unsafe.
Will the lack of compass affect entering trip itinerary in HERE Maps before launching HERE Drive+?

Automount SSHFS drive in user-level systemd session

Hello,
I'm able to automount a network drive through SSHFS using the following .mount unit in the system-level systemd session:
[Unit]
Description=adama shared drive
[Mount]
What=[email protected]:/home/shared
Where=/home/koral/remote/adama
Type=fuse.sshfs
Options=_netdev,noauto,users,idmap=user,IdentityFile=/home/koral/.ssh/id_rsa,allow_other
[Install]
WantedBy=default.target
As is, the network drive is mounted at system start-up and it is read/write-able by any user logged into the local system.
I'd like the drive to be mounted only when my $USER logs-in and read/write-able only by my $USER, so I considered moving the .mount unit to my user-level systemd session, but now the automounting fails with an unhelpful error message:
systemd[1969]: Mounting adama shared drive...
systemd[1969]: home-koral-remote-adama.mount mount process exited, code=exited status=1
systemd[1969]: Failed to mount adama shared drive.
systemd[1969]: Unit home-koral-remote-adama.mount entered failed state
I guess there is a permission issue somehow, could you please help figuring it out ?
Note: I'm still using systemd-204 as the user-level session is kind of broken in later versions as described here.
Kind regards.
Last edited by koral (2014-03-30 17:54:45)

xtian wrote:I can mount using the manual command `$sshfs [email protected]:/ /mnt/mrwizard.local`
According to the above your username is xtian, which it isn't in your fstab entry:
xtian wrote:[email protected]:/ /mnt/mrwizard.local ...
So without having looked for further errors nor knowing anything about sshfs, I would suppose to change this.
Sometimes simple spelling errors are actually the hardest to solve. – Like I always try to '#include <some_library.c>'.

10.5.1 - Automount shared drive question

I have a mac mini with an external HDD attached (running 10.4) -- my macbook pro can find the mini without problems, along with all currently mounted drives. The only drive it CAN'T find is the external hard drive.
Is this a problem with how it is mounted? It only finds disk images and not samba mounts? Any way to make it automatically show up when I connect to my mini?

Goto Sharepoints home, there is also a Sharepoints Automounter... but maybe I don't read it right yet... just finally got Internet in Leopard a few minutes ago.
As far as "bookmarks", the cool workaround in Tiger was to once mounted, drag those Globe Icons to the Dock between Applications & Trash, or if you had many, create a New Folder on the Desktop, drag all those Globe Icons there, rename then if you wish, then drag that folder to the Dock... but no idea how Lep[ard operates with that yet... far as I'm concerned, if Leopard has 300+ improvements, then it must have 500+ steps backwards!

Usb drive automount with drive's Name

I've read http://wiki.archlinux.org/index.php/Udev#Udev_Tricks so now usb drives are automounted as /mnt/usbhd-sda1 (or something similar). But I want them to mount as /mnt/usb-drive-name
where usb-drive-name is auto-detected (not preentered by hand).
Unfortunetly I didn't find drive name in information provided by udevinfo.
Is it possible to do that?
Also I'm using KDE and want to set it up so that automounted drive would appear in system:/media. As far as I understand in order for that to happen I need a record in fstab but I have no idea what that should be.
Thanks in advance.
Last edited by el_ave (2007-03-20 21:14:51)

You have clearly not done very much research on this subject. Did you know that with hal and dbus daemons, kde will automount for you? And for that to happen, there should _not_ be an entry about that device in fstab, unless it is clearly specified as "noauto". You need also be a member of the correct groups to do this.
After that, it's a easy as clicking the device in media:/ and renaming it...
Please, read up on the wiki.
esp. the "beginners guide" by chaosgeistern.

Automounting flash drives, but can't unmount them?

Hi all, I'm new to Arch after switching from Crunchbang a few days ago.
I've managed to enable automounting for my USB drives with udev and HAL, but when I try to eject them in Nautilus, I get
umount: /media/EMBARQ is not in the fstab (and you are not root)
Is there any way to allow myself to umount a USB drive as a regular user? Using sudo umount /media/XX works fine, but it's a bit irritating to have a shiny new eject button that I can't use.
EDIT: I just use Nautilus as a file manager, and not the full GNOME desktop.
Last edited by schnauzer (2009-11-11 04:24:42)

I've already done that, but no luck. This is what my /etc/dbus-1/system.d/hal.conf looks like:
<!DOCTYPE busconfig PUBLIC
"-//freedesktop//DTD D-BUS Bus Configuration 1.0//EN"
"http://www.freedesktop.org/standards/dbus/1.0/busconfig.dtd">
<busconfig>


<policy user="hal">
<allow own="org.freedesktop.Hal"/>
</policy>
<policy user="root">
<allow own="org.freedesktop.Hal"/>
</policy>

<policy context="default">
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.DBus.Introspectable"/>
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.DBus.Properties" />
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Device"/>
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Manager"/>
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Device.CPUFreq"/>
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Device.DockStation"/>
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Device.KillSwitch"/>
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Device.KeyboardBacklight"/>
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Device.LaptopPanel"/>
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Device.Leds"/>
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Device.LightSensor"/>
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Device.Storage"/>
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Device.Storage.Removable"/>
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Device.SystemPowerManagement"/>
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Device.Volume"/>
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Device.Volume.Crypto"/>
<allow send_destination="org.freedesktop.Hal"
send_interface="org.freedesktop.Hal.Device.WakeOnLan"/>
</policy>

<policy group="power">
<allow send_interface="org.freedesktop.Hal.Device.SystemPowerManagement"/>
<allow send_interface="org.freedesktop.Hal.Device.LaptopPanel"/>
</policy>
<policy group="storage">
<allow send_interface="org.freedesktop.Hal.Device.Volume"/>
<allow send_interface="org.freedesktop.Hal.Device.Volume.Crypto"/>
</policy>
</busconfig>
Also,
[schnauzer@wilson ~]$ groups
disk lp wheel video audio optical floppy storage scanner power users
Last edited by schnauzer (2009-11-11 15:47:53)

Archlinux - Automounting USB Drives [SOLVED]

Greetings,
I'm running Arch with AwesomeWM (no DE). I created the Udev rule as described here:
https://wiki.archlinux.org/index.php/Ud … if_present
I am still unable to have my device automount as a normal user. A cd /media and ls yields nothing. Suggestions? New to Arch.
lsusb output:
Bus 001 Device 004: ID 058f:6387 Alcor Micro Corp. Transcend JetFlash Flash Drive
Thanks!
Chris
Last edited by CFet (2011-08-10 16:33:52)

I did the same thing, copied the first example from the wiki and it works fine, no udisks/devmon etc., so it should be doable.
Maybe check the output of dmesg after inserting the stick, might be some error or other info. Does it give it an id like sdb1?

How to: automount network drive at start up?

so i put my netwrok drive to login item under user account control and it automaticelly mount the drive on boot up but it really annoy me when the finder window popping up and showing the drive is mounted everytime it statrt up eventhough I tried selecting the checkbox to "hide".
OS X 10.8.3
is there a way to automount a network drive without popping up in the finder at start up?

Unless the mount is needed before a user logs in, it may mount on demand, depending on what process demands it first. If that doesn't work for you, see below.
Autofs: Automatically Mounting Network File Shares in Mac OS X

Problems automounting NFS

I have an Ubuntu box with NFS server setup. I can mount this in Snow Leopard by opening the terminal and typing:
mount 192.168.1.145:/export/john /Users/john/Server
I can do this as sudo or without and either way I get a folder in my 'Home' folder that I am unable to open as I do not have sufficient permissions BUT also have a disk appear under 'Devices' in finder that I can access. I can read and write to it this way which is great.
If, however, I try exactly the same using Disk Utility and the NFS auto mounter, I only get the entry in my 'Home' folder and am unable to open it due to permissions etc.
Through the terminal method, ls -l gives:
drwxrwxrwx 22 1000 1000 4096 18 Jul 19:36 Server
But with the NFS automount option it is:
dr-xr-xr-x 2 root staff 1 18 Jul 19:56 Server
I am sure that this is something simple about permissions that I am not grasping but I am really stuck! I have read a number of similar posts about this but they all seem to say that a bug was fixed with the upgrade to 10.6.8. I am using 10.6.8.
I really want to get this fixed. I have been using Samba to share but there is, for me, a massive speed difference when transferring files with NFS
Any suggestions would be appreciated.
Thanks

NFS is pretty hard to debug via internet forum because each server is different. Try looking at Apple's Autofs documentation and play around with the actual autofs config files. You might have better luck that way.

X-systemd.automount nfs drive

Similar Messages

Maybe you are looking for