Disable autofs?

What is svc:/system/filesystem/autofs:default (from SMF)
I am considering disabling it.
Any information welcome.
Thanks!

Automount/autofs
# svcs -l autofs
fmri svc:/system/filesystem/autofs:default
name automounter
enabled true
state online
next_state none
state_time Fri Apr 30 14:51:05 2010
logfile /var/svc/log/system-filesystem-autofs:default.log
restarter svc:/system/svc/restarter:default
contract_id 63
dependency require_all/none svc:/system/filesystem/local (online)
dependency require_all/restart svc:/milestone/name-services (online)
dependency optional_all/none svc:/network/nfs/client (online)
dependency require_all/restart svc:/network/rpc/bind (online)

Similar Messages

How to disable auto_home and individual datasets on Solaris 11 11/11

Good morning,
There's a lot of changes in Solaris 11 that I like, but two of the ones I dislike, I just can't seem to get rid of them.
I'd like to disable auto_home, permanently. I don't want users' home directories to be mapped on /home .
I've read that all I needed was to remove all mentions of home in /etc/auto_home and/or /etc/auto_master (can't recall which one of the 2 files as I removed all mentions, 'f course...) .
Once done, I read I simply needed to run automount once (automount -v) .
No go. The next user I've created was mapped in /etc/auto_home, and /etc/password modified accordingly.
Moreover, each new account is created as its own individual ZFS dataset. I understand the advantages of this, as each user can create his own snapshots, etc. But I don't need that, and I certainly won't need a zfs list output that scrolls on many pages !
How can I disable this ? I just tested it, 2 seconds ago :
[08:43:10|jfg@oslo:/opt] sudo useradd -u 9999 -c 'TEST' -d /export/home/TEST -m -s /bin/bash test
80 blocks
[08:45:59|jfg@oslo:/opt] grep TEST /etc/passwd ; grep TEST /etc/auto_* ; zfs list | grep TEST
test:x:9999:10:TEST:/home/test:/bin/bash
/etc/auto_home:test localhost:/export/home/TEST
rpool/homes/oslo/test 35K 21.1G 35K /export/home/TEST
<EDIT> : forgot to mention, I destroyed the original dataset for the home directories, rpool/export/home, and created a new one, rpool/homes/zoneName/ as multiple zones accounts will be "hosted" in this dataset.
Thanks for helping,
Regards,
-- Jeff
Edited by: user5989503 on Jan 10, 2012 8:54 AM

Thanks Alan,
I remember awhile back reading about this on OpenSolaris, but it just came back to mind as you mentioned it.
Still, other than svcadm disable autofs, I can't see how to disable only auto_home.
And I'm still stuck with my individual zfs datasets that I hate hoooo so much ! :-)
Thanks,
-- Jeff

NFS causes whole system hang

I have a home server that I just set up recently that runs Arch linux. It exports a couple of external hard drives via NFS. I have been mouting them with autofs on my laptop. However, after several hours the entire system completely hangs up. I originally thought it had something to do with the rpc-gssd daemon that the NFS wiki page recommends running as it was dying in a strange way and I thought that may have been related to the hang ups. After implementing a different workaround (blacklist rpcsec_gss_krb5) and disabling rpc-gssd, I am still having the same hang issue.
Here is what happens:
I boot up my computer, start Firefox, Thunderbird, various terminals, etc. I mount the NFS share with autofs by opening up the /media/net/atomic/qx2_data directory. After a while, the NFS mounts in Thunar start disappering momentarily. Then a little while later the system completely hangs and requires a hard reboot. The end of the log from journalctl is posted below.
Right now I have disabled autofs and I will only mount the drives on the server via SFTP to avoid this problem, but I would really like to get this debugged. Also, this is not likely related to any sort of a connection issue as both computers are hardwired to the same Gigabit Ethernet switch.
Any ideas on what might be going on here?
/etc/autofs/auto.net:
atomic -fstype=nfs4,rw,async,sec=sys,bg,intr atomic.local:/
Log:
Dec 17 16:33:35 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:34:51 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:36:07 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:37:23 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:38:35 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:39:51 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:41:07 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:42:23 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:43:39 watatsumi automount[19747]: key ".hidden" not found in map source(s).
Dec 17 16:45:16 watatsumi kernel: BUG: soft lockup - CPU#5 stuck for 23s! [htop:2505]
Dec 17 16:45:16 watatsumi kernel: Modules linked in: usbtmc auth_rpcgss oid_registry nfsv4 tun joydev snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd fuse nvidia(PO) iTCO_wdt iTCO_vendor_support uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core snd_usb_audio videodev snd_usbmidi_lib snd_rawmidi media snd_seq_device arc4 evdev microcode psmouse serio_raw iwldvm mac80211 snd_hda_codec_realtek iwlwifi snd_hda_intel snd_hda_codec cfg80211 snd_hwdep drm snd_pcm jme jmb38x_ms rfkill mii snd_page_alloc memstick snd_timer i2c_i801 mei_me snd i2c_core soundcore mei thermal shpchp wmi lpc_ich processor battery ac button video pcspkr nfs lockd
Dec 17 16:45:16 watatsumi kernel: sunrpc fscache ext4 crc16 mbcache jbd2 sd_mod hid_generic usbhid hid ahci libahci libata ehci_pci firewire_ohci sdhci_pci xhci_hcd scsi_mod ehci_hcd sdhci firewire_core crc_itu_t mmc_core usbcore usb_common
Dec 17 16:45:16 watatsumi kernel: CPU: 5 PID: 2505 Comm: htop Tainted: P O 3.12.5-1-ARCH #1
Dec 17 16:45:16 watatsumi kernel: Hardware name: CLEVO P150HMx/P150HMx, BIOS 4.6.4 08/09/2011
Dec 17 16:45:16 watatsumi kernel: task: ffff880801678000 ti: ffff8807dcbec000 task.ti: ffff8807dcbec000
Dec 17 16:45:16 watatsumi kernel: RIP: 0010:[<ffffffff814f4f8e>] [<ffffffff814f4f8e>] _raw_spin_lock+0x2e/0x40
Dec 17 16:45:16 watatsumi kernel: RSP: 0018:ffff8807dcbedd88 EFLAGS: 00000297
Dec 17 16:45:16 watatsumi kernel: RAX: 0000000000000082 RBX: ffffffff81299133 RCX: 0000000000000000
Dec 17 16:45:16 watatsumi kernel: RDX: 0000000000000083 RSI: ffffffff8172447b RDI: ffffffff818063c0
Dec 17 16:45:16 watatsumi kernel: RBP: ffff8807dcbedd88 R08: 0000000000017b80 R09: ffff88080e83ce00
Dec 17 16:45:16 watatsumi kernel: R10: ffff8807dcbedfd8 R11: ffffffff81209fbd R12: ffff8807dcbedea0
Dec 17 16:45:16 watatsumi kernel: R13: ffff8807dcbede93 R14: ffffffff812981f2 R15: ffff8807dcbedcf8
Dec 17 16:45:16 watatsumi kernel: FS: 00007f52ddf3c700(0000) GS:ffff88082f540000(0000) knlGS:0000000000000000
Dec 17 16:45:16 watatsumi kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 17 16:45:16 watatsumi kernel: CR2: 00007f52ddf7d000 CR3: 00000007cb1d2000 CR4: 00000000000407e0
Dec 17 16:45:16 watatsumi kernel: Stack:
Dec 17 16:45:16 watatsumi kernel: ffff8807dcbedda0 ffffffff811bdee9 ffff88077db89c18 ffff8807dcbeddb8
Dec 17 16:45:16 watatsumi kernel: ffffffff811c0089 ffff88064dd7d9c0 ffff8807dcbedde8 ffffffff8120d9db
Dec 17 16:45:16 watatsumi kernel: ffff88064dd7d9c0 0000000000000005 ffff8807ba6dc480 ffffffff8120df90
Dec 17 16:45:16 watatsumi kernel: Call Trace:
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811bdee9>] inode_sb_list_add+0x19/0x60
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811c0089>] new_inode+0x29/0x30
Dec 17 16:45:16 watatsumi kernel: [<ffffffff8120d9db>] proc_pid_make_inode+0x1b/0x100
Dec 17 16:45:16 watatsumi kernel: [<ffffffff8120df90>] ? proc_map_files_lookup+0x160/0x160
Dec 17 16:45:16 watatsumi kernel: [<ffffffff8120dfab>] proc_task_instantiate+0x1b/0xc0
Dec 17 16:45:16 watatsumi kernel: [<ffffffff8120e28f>] proc_fill_cache+0xbf/0xe0
Dec 17 16:45:16 watatsumi kernel: [<ffffffff8120ea1d>] proc_task_readdir+0x18d/0x3b0
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811b75ad>] iterate_dir+0xad/0xe0
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811b79e2>] SyS_getdents+0x92/0x120
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811b76c0>] ? fillonedir+0xe0/0xe0
Dec 17 16:45:16 watatsumi kernel: [<ffffffff814fcfed>] system_call_fastpath+0x1a/0x1f
Dec 17 16:45:16 watatsumi kernel: Code: 66 90 55 65 48 8b 04 25 70 c7 00 00 48 89 e5 83 80 44 e0 ff ff 01 b8 00 01 00 00 f0 66 0f c1 07 0f b6 d4 38 c2 75 04 5d c3 f3 90 <0f> b6 07 38 d0 75 f7 5d c3 66 0f 1f 84 00 00 00 00 00 66 66 66
Dec 17 16:45:16 watatsumi kernel: BUG: soft lockup - CPU#6 stuck for 23s! [umount.nfs4:30556]
Dec 17 16:45:16 watatsumi kernel: Modules linked in: usbtmc auth_rpcgss oid_registry nfsv4 tun joydev snd_hda_codec_hdmi x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crct10dif_common crc32_pclmul crc32c_intel ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd fuse nvidia(PO) iTCO_wdt iTCO_vendor_support uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_core snd_usb_audio videodev snd_usbmidi_lib snd_rawmidi media snd_seq_device arc4 evdev microcode psmouse serio_raw iwldvm mac80211 snd_hda_codec_realtek iwlwifi snd_hda_intel snd_hda_codec cfg80211 snd_hwdep drm snd_pcm jme jmb38x_ms rfkill mii snd_page_alloc memstick snd_timer i2c_i801 mei_me snd i2c_core soundcore mei thermal shpchp wmi lpc_ich processor battery ac button video pcspkr nfs lockd
Dec 17 16:45:16 watatsumi kernel: sunrpc fscache ext4 crc16 mbcache jbd2 sd_mod hid_generic usbhid hid ahci libahci libata ehci_pci firewire_ohci sdhci_pci xhci_hcd scsi_mod ehci_hcd sdhci firewire_core crc_itu_t mmc_core usbcore usb_common
Dec 17 16:45:16 watatsumi kernel: CPU: 6 PID: 30556 Comm: umount.nfs4 Tainted: P O 3.12.5-1-ARCH #1
Dec 17 16:45:16 watatsumi kernel: Hardware name: CLEVO P150HMx/P150HMx, BIOS 4.6.4 08/09/2011
Dec 17 16:45:16 watatsumi kernel: task: ffff8807c902e840 ti: ffff88064fe5c000 task.ti: ffff88064fe5c000
Dec 17 16:45:16 watatsumi kernel: RIP: 0010:[<ffffffff814f4f83>] [<ffffffff814f4f83>] _raw_spin_lock+0x23/0x40
Dec 17 16:45:16 watatsumi kernel: RSP: 0018:ffff88064fe5ddb0 EFLAGS: 00000202
Dec 17 16:45:16 watatsumi kernel: RAX: 0000000000002c2c RBX: f97a1072bc3dd003 RCX: ffffffff818c01e0
Dec 17 16:45:16 watatsumi kernel: RDX: 000000000000002b RSI: 0000000000000001 RDI: ffff880667e6d438
Dec 17 16:45:16 watatsumi kernel: RBP: ffff88064fe5ddb0 R08: 0000000000000000 R09: 0667f127400c0000
Dec 17 16:45:16 watatsumi kernel: R10: f97a1072bc3dd003 R11: 0000000000000001 R12: ffff88064fe5dd30
Dec 17 16:45:16 watatsumi kernel: R13: ffff88064fe5ddb0 R14: ffff880667f12730 R15: ffff880667f126a8
Dec 17 16:45:16 watatsumi kernel: FS: 00007fdbfd3b3780(0000) GS:ffff88082f580000(0000) knlGS:0000000000000000
Dec 17 16:45:16 watatsumi kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 17 16:45:16 watatsumi kernel: CR2: 00007f63631ff000 CR3: 00000006a0de3000 CR4: 00000000000407e0
Dec 17 16:45:16 watatsumi kernel: Stack:
Dec 17 16:45:16 watatsumi kernel: ffff88064fe5ddf8 ffffffff811e612c ffff880667f12730 0000000000000000
Dec 17 16:45:16 watatsumi kernel: ffff8807d797e000 ffff8807d797e0a0 ffffffffa143fe40 ffff880099c279c0
Dec 17 16:45:16 watatsumi kernel: ffff880674e30620 ffff88064fe5de20 ffffffff811a6a60 0000000000000025
Dec 17 16:45:16 watatsumi kernel: Call Trace:
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811e612c>] fsnotify_unmount_inodes+0x11c/0x1b0
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811a6a60>] generic_shutdown_super+0x40/0xf0
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811a6cd2>] kill_anon_super+0x12/0x20
Dec 17 16:45:16 watatsumi kernel: [<ffffffffa03eb18b>] nfs_kill_super+0x1b/0x30 [nfs]
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811a70bd>] deactivate_locked_super+0x3d/0x60
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811a76a6>] deactivate_super+0x46/0x60
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811c350f>] mntput_no_expire+0xef/0x150
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811c3596>] mntput+0x26/0x40
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811c36ad>] namespace_unlock+0xfd/0x110
Dec 17 16:45:16 watatsumi kernel: [<ffffffff811c4803>] SyS_umount+0x1c3/0x3a0
Dec 17 16:45:16 watatsumi kernel: [<ffffffff814fcfed>] system_call_fastpath+0x1a/0x1f
Dec 17 16:45:16 watatsumi kernel: Code: 05 e8 52 84 da ff 5d c3 66 66 66 66 90 55 65 48 8b 04 25 70 c7 00 00 48 89 e5 83 80 44 e0 ff ff 01 b8 00 01 00 00 f0 66 0f c1 07 <0f> b6 d4 38 c2 75 04 5d c3 f3 90 0f b6 07 38 d0 75 f7 5d c3 66
Dec 17 16:45:16 watatsumi kernel: BUG: soft lockup - CPU#7 stuck for 23s! [ifconfig:30557]
Last edited by alex.forencich (2013-12-18 02:02:58)

Hi Alex - autofs mounts on demand/request, and unmounts a filesystem after 10 minutes of non-use by default. If you set the timeout to zero (auto.master), it disables this timeout. If this is an NFSv4 umount bug, then I don't think this will help you as you'll have to umount at some stage (e.g. shutting down).

Deactivating Auto Fit on Object Frames

We have a document which was created using the autofit option enabled. We're looking for an easy way to disenable the autofit for all frames in the document. Is there a slicker way to do it than to select all the objects and change the options in the fitting frame options palette?

Select all objects (ctrl+A PC/ cmd+A mac)... then just uncheck AutoFit. This will disable AutoFit for all objects. This is two keystrokes... doesn't get much slicker than that.

How to configure Airport Extreme AFP disk sharing to host multiple users' home-directories (Lion, using autofs)

I have this working, but only by completely bypassing access control, using guest access with read+write permissions.
Do I need to buy Lion Server, to do this. All my past unix/linux experience says Lion Server should _not_ be necessary.
This seems like a simple & obvious setup objective, but it is proving to be harder than I would imagine.
Setup:
multiple users, sharing two mac mini's running OSX Lion
connected to an Airport Extreme (4th gen) with a USB disk shared (either via disk password, AEBS password, or using AEBS user's passwords).
After much experimentation and web research, I finally have managed to get the mini's to auto mount the Airport Extreme's AFP shared USB disk. Well almost... It only works if, on the Airport, I set the guest access permissions to read+write and select the "Secure Shared Disks" method to "With disk password" or "with Airport Extreme password". In other words, it only works if I essentially bypass/disable access control by using the guest authentication mechanism to the AFP shared disk.
On the Lion side of this, I am automounting the users directories via "autofs". The config files for this are
/etc/auto_master:
# Automounter master map
+auto_master            # Use directory service
/net                    -hosts          -nobrowse,hidefromfinder,nosuid
/home                   auto_home       -nobrowse,hidefromfinder
/Network/Servers        -fstab
/-                      -static
/-                      auto_afp
/etc/auto_afp:
# Automounter AFP master map
# https://discussions.apple.com/thread/3336384?start=0&tstart=0
/afp/users -fstype=afp afp://;AUTH=No%20User%[email protected]/Users/
Then, after rebooting and verifying read+write access to the /afp/users directories, I change each user's home directory: In System Preferences > System > Users & Groups, I right-click over the users to access the Advanced Options, changing the Home directory field to point at the AFP-mounted /afp/users/Users/* home directories.
I experimented with alternate UAM specifications, as well as both OSX and AESB users & passwords. Using guest access is the only thing that has worked.
Any pointers would be appreciated...

Based on lots more experimentation which confirms the information in a parallel discussion (cf. Automount share as non ROOT or SYSTEM user! https://discussions.apple.com/thread/3221944), I have concluded that the Lion 10.7.2 implementation of AutoFS mechanism is broken. I submitted a bug report via apple.com/feedback.
Work arounds..?
Earlier I wondered if installing Lion OSX Server was necessary. The more I contemplate this, the more I am convinced it _should_not_ be necessary. The client-server architecture is clear: my mac's are the file-server client's and the Airport Extreme is supposed to act as the file server. The only thing instaling Lion Server would do (besides enriching Apple.com) is enable me to configure one of the mac's as the file server. This would require it to be "always on" (thus enriching my electric utility as wel). Okay, an additional benefit would be configuring software RAID disks attached to the Lion server, but Time Machine has worked fine for me in the past, backing up to disks mounted on the Airport Extreme.
One solution is to create a disk partition for each user and instruct each user to connect / authenticate to the Airport Extreme AFP share at login. The multiplicity of partitions is necessary since the first user to mount the AFP share, takes ownership of it, blocking other users from accessing that disk partition. A user can "steal" ownership by reconnecting, but this will leave the other user's applications & open files dangling.
This disfunctional situation really *****. Before instaling Lion, I put a 64 GB SSD (solid state disk) in each of our mac's. I did this expecting to easily configure the /Users/* data on external networked storage. I'm having a dejavu "Bill Gates"-ware moment; problems like this were why I abandoned Windoz.
I will make a few more experiments using the depreciated /etc/fstab mechanism. Maybe that will bypass the broken-ness of AutoFS...? Alternately, I guess I could also try to run Kerberos authentication to bypass whatever is broken in AutoFS, but that would require a running a Kerberos daemon somewhere. Possibly I could configure a Kerberos service to run on both my mac's (without installing Apple's Lion Server)...?
Stay tuned...

Solaris 10 U8 autofs homes not working

On three fresh installs of U8, home directories are not automounting. Has this been changed in any way? This is using files based users. Autofs shows online and there are no errors in the SMF log. Any ideas?
Charles

bash-3.00# cat /etc/auto_master
# Copyright 2003 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
# ident "@(#)auto_master 1.8 03/04/28 SMI"
# Master map for automounter
+auto_master
/net -hosts -nosuid,nobrowse
/home auto_home -nobrowse
bash-3.00# cat /etc/auto_home
# Copyright 2003 Sun Microsystems, Inc. All rights reserved.
# Use is subject to license terms.
# ident "@(#)auto_home 1.6 03/04/28 SMI"
# Home directory map for automounter
+auto_home
bash-3.00# cat /var/svc/log/system-filesystem-autofs\:default.log
[ Nov 1 22:13:50 Disabled. ]
[ Nov 1 22:13:50 Rereading configuration. ]
[ Nov 1 22:13:52 Enabled. ]
[ Nov 1 22:14:09 Executing start method ("/lib/svc/method/svc-autofs start") ]
[ Nov 1 22:14:10 Method "start" exited with status 0 ]
[ Nov 1 22:38:49 Stopping because service disabled. ]
[ Nov 1 22:38:49 Executing stop method ("/lib/svc/method/svc-autofs stop 66") ]
[ Nov 1 22:38:54 Method "stop" exited with status 0 ]
[ Nov 1 22:41:56 Enabled. ]
[ Nov 1 22:42:10 Executing start method ("/lib/svc/method/svc-autofs start") ]
[ Nov 1 22:42:11 Method "start" exited with status 0 ]
[ Nov 1 23:01:16 Stopping because service disabled. ]
[ Nov 1 23:01:16 Executing stop method ("/lib/svc/method/svc-autofs stop 62") ]
[ Nov 1 23:01:21 Method "stop" exited with status 0 ]
[ Nov 1 23:04:43 Enabled. ]
[ Nov 1 23:04:53 Executing start method ("/lib/svc/method/svc-autofs start") ]
[ Nov 1 23:04:53 Method "start" exited with status 0 ]
[ Nov 1 23:06:00 Stopping because service disabled. ]
[ Nov 1 23:06:00 Executing stop method ("/lib/svc/method/svc-autofs stop 51") ]
[ Nov 1 23:06:05 Method "stop" exited with status 0 ]
[ Nov 1 23:09:04 Enabled. ]
[ Nov 1 23:09:22 Executing start method ("/lib/svc/method/svc-autofs start") ]
[ Nov 1 23:09:22 Method "start" exited with status 0 ]
[ Nov 1 23:15:15 Stopping because service disabled. ]
[ Nov 1 23:15:15 Executing stop method ("/lib/svc/method/svc-autofs stop 62") ]
[ Nov 1 23:15:21 Method "stop" exited with status 0 ]
[ Nov 1 23:18:25 Enabled. ]
[ Nov 1 23:18:39 Executing start method ("/lib/svc/method/svc-autofs start") ]
[ Nov 1 23:18:39 Method "start" exited with status 0 ]
[ Nov 1 23:21:07 Stopping because service disabled. ]
[ Nov 1 23:21:07 Executing stop method ("/lib/svc/method/svc-autofs stop 51") ]
[ Nov 1 23:21:12 Method "stop" exited with status 0 ]
[ Nov 1 23:24:11 Enabled. ]
[ Nov 1 23:24:26 Executing start method ("/lib/svc/method/svc-autofs start") ]
[ Nov 1 23:24:26 Method "start" exited with status 0 ]
Doesn't look like anything is weird here.
Charles

Autofs timeout while accessing to remote NFS mount

Following Apple recommendations, I switched to "Directory Utility" to configure NFS mounts. As far as I understand, if you do so, the mounts are handled by automount which is itself called by autofs. The good thing of this is that autofs is unmounting unused mounts (after a timeout of 3600 seconds as defined in /etc/autofs.conf). Any time you need the remote drive (Finder call, ls in Terminal..., opening file), autofs is remounting ressource. This is a nice behaviour... in theory.
I'm using some codes (written in IDL) that are reading and writing on that remote NFS server once every 5 minutes. Theoretically, autofs should be detecting these accesses and should keep the drive mounted. This is unfortunately not the case. The drive is unmounted 3600 seconds after I last accessed the mount through the Finder or with any other Application.
There is apparently no way to remove this "automated unmounting" feature. I tried to set the timeout delay to a very large number (1 day) but it still disconnects me after this delay, if I don't do anything else than running my IDL code. If I mount the NFS share with the "mount_nfs" command, it works perfectly, as it is not handled by autofs.
I wonder then if there is any recommandation on Apple's side in such a case, other than going back to traditional mount_nfs.

As you have discovered, automount/autofs is also an "auto-unmounter" and there is no way to remove that feature. Contrary to what one might think, the auto unmounting does NOT happen after a period of "inactivity" of the mount. This is because autofs has no way of knowing when an automounted file system was last accessed. So, instead it periodically attempts to unmount it - if it is busy it won't get unmounted - if it isn't busy it will get unmounted.
You can't disable this - but you can make the periodic unmounting so infrequent as to effectively disable the feature. Try setting the AUTOMOUNT_TIMEOUT interval to something really large - like 315360000 (which would be 10 years).
However, in theory, this auto-unmounting should not be a problem because if it does get unmounted then the next access to that file system should cause it to get mounted again. And all this should happen without the code that is accessing the automount knowing that it isn't always mounted. It should always be there when it is accessed. So, the usual response to someone asking how to disable the auto-unmounting is to ask why they think it is a problem.
(Oh, and you don't have to use "mount_nfs" - just "mount" should work to manually mount an NFS file system (that saves a little typing).)
HTH
--macko

Autofs won't automount

Hello everyone,
I followed the wiki for autofs step by step (minus the things I don't care about, I only need usb and cd/dvds to automount) and when I was done I still couldn't get it to actually automounting.
What could I do to see where the error is?

*************EDIT: SOLVED**************
I had probably forgotten '1' at the end of sdb1, now my /etc/autofs/auto.misc looks like this:
flashb -fstype=auto,async,nodev,nosuid,umask=000,gid=disk :/dev/sdb1
I also removed --timeout option in auto.master, and autofs is working fine now.
I have exact same problem.
More info:
1. Flash drive has a 1gb ext4 partition and works perfectly elsewhere.
$ lsblk /dev/sdb
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
sdb 8:16 1 954M 0 disk
└─sdb1 8:17 1 953M 0 part
$ sudo fdisk -l
Disk /dev/sdb: 1000 MB, 1000341504 bytes, 1953792 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00056ce1
Device Boot Start End Blocks Id System
/dev/sdb1 2048 1953791 975872 83 Linux
2. Modprobe'd autofs4, but doesn't show up in lsmod, is this normal?
$ modprobe autofs4 && lsmod | grep autofs4
3. Autofs config files:
/etc/autofs/auto.master
# Sample auto.master file
# Format of this file:
# mountpoint map options
# For details of the format look at autofs(5).
/media/autofs /etc/autofs/auto.misc --timeout=1
/etc/autofs/auto.misc
# This is an automounter map and it has the following format
# key [ -mount-options-separated-by-comma ] location
# Details may be found in the autofs(5) manpage
usbstick -fstype=auto,async,nodev,nosuid,umask=000 :/dev/sdb
cdrom -fstype=iso9660,ro,nodev,nosuid :/dev/cdrom
#floppy -fstype=auto,async,nodev,nosuid,umask=000 :/dev/fl
/etc/conf.d/autofs
#localoptions='rsize=8192,wsize=8192'
# e.g. --timeout=60
daemonoptions=''
There is this line in /etc/nsswitch.conf
automount: files
4. Daemon looks ok
$ sudo systemctl status autofs
autofs.service - Automounts filesystems on demand
Loaded: loaded (/usr/lib/systemd/system/autofs.service; disabled)
Active: active (running) since Sun 2013-04-14 14:42:54 AMT; 28min ago
Process: 2405 ExecStart=/usr/sbin/automount $OPTIONS --pid-file /run/autofs.pid (code=exited, status=0/SUCCESS)
Main PID: 2407 (automount)
CGroup: name=systemd:/system/autofs.service
└─2407 /usr/sbin/automount --pid-file /run/autofs.pid
Apr 14 14:42:54 work2 systemd[1]: Started Automounts filesystems on demand.
5. Permissions of /etc/autofs/auto.master /etc/autofs/auto.media /etc/autofs/auto.misc /etc/conf.d/autofs are all 644 ( -rw-r--r-- ).
Any help appreciated.
Last edited by axper (2013-04-24 18:56:18)

[CLOSED] Mounting CD/DVD with autofs

cat /etc/autofs/auto.master
/media /etc/autofs/auto.misc
cat /etc/autofs/auto.misc
cdrom -fstype=auto,ro,nodev,nosuid :/dev/cdrom
Automounting of data CDs works as advertised - problems start with DVDs and audio CDs. When DVD film or data DVD is inserted /media/cdrom is empty. With audio CDs I'm getting:
ls /media/cdrom
ls: reading directory .: Input/output error
total 0
and I cant see audio CD in Clementine neither. Could someone advise me how to solve this small problem?
EDIT:
I'm closing this thread as I gave up on autofs and I am a happy user of the devmon.
Last edited by asd01 (2012-05-04 20:41:25)

I thought that I might be wrong with the device name. As,
~ $ ll /dev/cd/
total 0
lrwxrwxrwx 1 root root 6 2009-06-05 16:32 cdrom-3:0:0:0 -> ../sr0
lrwxrwxrwx 1 root root 6 2009-06-05 16:32 cdrw-3:0:0:0 -> ../sr0
lrwxrwxrwx 1 root root 6 2009-06-05 16:32 dvd-3:0:0:0 -> ../sr0
lrwxrwxrwx 1 root root 6 2009-06-05 16:32 dvdrw-3:0:0:0 -> ../sr0
~ $
seems to lead all to the device /sr0, I changed the name of the above file to
/etc/hal/fdi/information/media-check-disable-storage_model_sr0.fdi
and restarted dbus and hal. Well, didn't work.
============
I found another post http://bbs.archlinux.org/viewtopic.php?id=55372 in the forum, which is somehow related to my problem, though restarting dbus and hal doesn't work for me. They suggest to start the window-manager with dbus-launch instead of exec (What has the Window-Manager to do with this??). So, I changed my .xinitrc to
ck-launch-session xfce4-session &
xfce4-panel -c &
dbus-launch xmonad
Well, didn't work.
Anyone has any idea? A direction to point me towards?
Cheers,
Thomas

How can I disable sending from one Mail account?

Hello. I have a gmail account that I use to subscribe to various newsletters and accounts. So it's essentially a read-only account for me. But I too frequently accidently send mail from that account. Is there a way to prevent mail from being sent from that account?

I want to do the same thing as the OP. I have tried making outgoing server none. And checking "always use this server so it prompts me to edit the message so that I manually select a different address to send from inthe drop down list. And selecting a different account for composing. Actually, all my outgoing emails keep coming from the one account I am attempting to disable. Got any other ideas?

Not null and enable or disable column in tabular form

Hi,
Using apex version 4.1 and working on tabular form.
ACT_COA_SEGMENT_MAS is Master table
and
ACT_SEGMENT_VALUES_MAS is detail table
I have entered 8 rows in master table and PARENT_SEGMENT_ID is column in master table which is null able. If i specified PARENT_SEGMENT_ID with value in master table then in detail table there is column PARENT_ID that should not be null and enable.
How i can enable or disable column when in master table PARENT_SEGMENT_ID column is null then in detail table PARENT_ID column should disable and vice versa.
I have created tabular form on Detail table. before insert into the tabular form Check in master table in first entry if PARENT_SEGMENT_ID is not null in first row of master table then in tabular form PARENT_ID should enable and not null able in corresponding to this first row id's lines in tabular form.
Same should check for second row in master table if PARENT_SEGMENT_ID is not null then entered rows with PARENT_ID into tabular form corresponding to 2nd id in master table should not nullable and column should enable in tabular form.
Thanks & Regards
Vedant
Edited by: Vedant on Jan 9, 2013 9:12 PM

Vedant,
You need to create you own manual tabular form and not use the wizard.
Using APEX_ITEM api you should be build you own form and you will be able to control how you wan to display the rows. (See Link [Apex Item Help|http://docs.oracle.com/cd/E37097_01/doc/doc.42/e35127/apex_item.htm#CACEEEJE] )
select case when PRIMARY_TABLE_COLUMN is null then APEX_ITEM.DISPLAY_AND_SAVE(3 , DETAIL_COLUMN ) else APEX_ITEM.TEXT(2,detail_column) end "ALIAS" from detail table
Hope that help.
Vivek

NOT disabling keyboard/trackpad on tablet fold...

This is probably the opposite of user problems regarding the keyboard/trackpad and turning the Yoga Pro 2 in tablet mode... Here's the situation:
I'm a Java programmer and I'm sharing my files with my home PC, so I can work from my laptop or desktop easily without transferring files back and forth.
It's no fun adjusting my typing to multiple different keyboards for different PCs, and overall I tend to prefer a trackpad over a mouse for what I do which makes using my lenovo yoga keyboard ideal for everything (majority of wireless keyboards also aren't backlit).
I'm using the program Mouse without Borders (from the Microsoft website) so that I can use my lenovo yoga keyboard/trackpad on my desktop.
What I want to do: keep my keyboard and trackpad enabled when putting the yoga into tablet mode. I've already figured out how to disable the touchscreen for such uses, but the only way I know to keep the keyboard and trackpad active is to uninstall the synaptics driver/software. Obviously that isn't an ideal solution to have to install and uninstall it every time I switch between PCs.
Is there any way to stop synaptics from disabling the keyboard and trackpad when in tablet mode? Preferrably something such as disabling something in device manager, not uninstalling and reinstalling software depending my use for the moment.

Please provide more information.
First, I have no idea what "Jimi to Jimi" means. This is probably just something you need to explain to me; a Google search didn't turn up anything useful.
You said that the keyboard and trackpad aren't working right. What does this mean, exactly? Regardless, the monitor you use should have no effect on the function of your other peripherals.

HT4528 My apple I'd is disable how do I get it working to download apps again

My apple ID is disable and wont let me download my apps back to my phone how do i fix the problem

Try to reset your password at http://iforgot.apple.com.
If that doesn't work, time to contact iTunes Support - http://apple.com/support/itunes/contact/

Got my password wrong twice and my mini is disable. I connected to iTunes, but can't get it to work. Can some one guide my through?

got my password wrong twice and my mini is disable. I connected to iTunes, but can't get it to work. Can some one guide my through?

If it's showing the red disabled screen due to incorrect passcodes then you may need to put the iPad into recovery mode : http://support.apple.com/kb/ht1808 - you should then be able to reset the iPad via your computer's iTunes and restore/resync your content to it

Disabled JMenuItem doesn show animated gif

Hi there
I would like to have a popup menu with actions that are enabled after they have finished with some background task taking some time. Basically this works fine for the enabling action on a shown popup. However, adding an animated gif as the icon or disabled icon does not show it in disabled state. In enabled state it works perfect. Please have a try with the sample code. You should see the disabled item for 2 secs and the icon is not showing up. After being enabled, it does. Invoking the menu again shows the animated gif in its last state left, but not moving any more.
I guess, repaints are not done appropriately in disabled state... Any ideas how to solve that would be highly appreciated :-)
Actually I used the icon at http://mentalized.net/activity-indicators/indicators/pascal_germroth/indicator.white.gif
Cheers
Daniel
public class Main
public static void main(String[] args)
    final JFrame frame = new JFrame();
    frame.addMouseListener(new MouseAdapter()
      public void mousePressed(final MouseEvent e)
        final JPopupMenu popup = new JPopupMenu();
        popup.add(new JMenuItem("Open..."));
        popup.add(new JMenuItem("Close"));
        final JMenuItem action = new JMenuItem("Long loading until enabled");
        action.setIcon(new ImageIcon("C:/spinner.gif"));
        action.setDisabledIcon(new ImageIcon("C:/spinner.gif"));
        popup.add(action).setEnabled(false);
        popup.show(e.getComponent(), e.getX(), e.getY());
        SwingUtilities.invokeLater(new Runnable()
          public void run()
            try
              Thread.sleep(2000);
              action.setEnabled(true);
            catch (InterruptedException e1)
    frame.setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
    frame.setSize(300, 200);
    frame.setVisible(true);
}Edited by: daniel.frey on Apr 22, 2009 7:50 AM

The problem is that you are causing the EDT to sleep, which means the GUI can't repaint itself. Read the section from the Swing tutorial on Concurrency to understand what is happening.

Disable autofs?

Similar Messages

Maybe you are looking for