Setting umask on NFS mounts under OS X 10.6

I don't see any up to date information on setting umasks with 10.6. We use NFS SAN storage for several folders, mounted using the new NFS Mounts feature of Disk Utility and the SAN and Mac are playing nicely for UID and GID mapping even using our Active Directory LDAP groups and accounts.
However, it creates everything as 755 (umask 0022, the system default) and I'd like to change that umask to 002 to create 775's instead. Nothing for 10.4 or 10.5 seems to apply here (NSUMask, etc.) and it doesn't appear to be a NFS Mount option, either.
NFSv4 and ACLs are not really a good option for me since it's a multiprotocol SAN environment we want to keep NFSv3 permissions bits for UNIX/Linux/MAC and ACLs for Windows. Any ideas how to set the default umask, or at least a way to set the umask for each mount?

xzi wrote:
Yes, I tried that, it does not appear to work on 10.6 that's my point.
I'm sorry, but I just can't figure out "etc". All I can do is keep asking if you have tried this or that. Have tried both variations of that config file and it didn't work? Have you tried instructions in this document, which seems updated for Snow Leopard?
Have you considered that you may have already tried the correct solution, but simply didn't do it correctly? Have you tried with logging-out and back in? With rebooting?

Similar Messages

Cannot access external NFS mounts under Snow Leopard

I was previously running Leopard (10.5.x) and automounted an Ubuntu (9.04 Jaunty) Linux NFS mount from my iMac. I had set this up with Directory Utility and it was instantly functional and I never had any issues. After upgrading to Snow Leopard, I set up the same mount point on the same machine (using Disk Utility now), without changing any of the export settings, and Disk Utility stated that the external server had responded and appeared to be working correctly. However, when attempting to access the share, I get a 'Operation not permitted' error. I also cannot manually create the NFS mount using mount or mount_nfs. I get a similar error if I try to cd into /net/<remote-machine>/<share>. I can see the shared folder in /net/<remote-machine>, but I cannot access it (cd, ls, etc). I can see on the Linux machine that the iMac has mounted the share (showmount -a), so the problem appears to be solely in the permissions. But I have not changed any of the permissions on the remote machine, and even then, they are blown wide open (777) so I'm not sure what is causing the issue. I have tried everything as both a regular user, and as root. Any thoughts?
On the Linux NFS server:
% cat /etc/exports
/share 192.168.1.0/24(rw,sync,nosubtree_check,no_rootsquash)
% showmount -a
All mount points on <server>:
192.168.1.100:/share <-- <server> address
192.168.1.101:/share <-- iMac address
On the iMac:
% rpcinfo -t 192.168.1.100 nfs
program 100003 version 2 ready and waiting
program 100003 version 3 ready and waiting
program 100003 version 4 ready and waiting
% mount
trigger on /net/<server>/share (autofs, automounted, nobrowse)
% mount -t nfs 192.168.1.100:/share /Volumes/share1
mount_nfs: /Volumes/share1: Operation not permitted

My guess is that the Linux server is refusing NFS requests coming from a non-reserved (<1024) source port. If that's the case, adding "insecure" to the Linux export options should get it working. (Note: requiring the use of reserved ports doesn't actually make things any more secure on most networks, so the name of the option is a bit misleading.)
If you were previously able to mount that same export from a Mac, you must have been specifying the "-o resvport" option and doing the mounts as root (via sudo or automount which happens to run as root). So that may be another fix.
HTH
--macko

Branded 9 Container NFS mounts

Does anybody have any information on how the P2V install handles exisiting NFS mounts that were in the vfstab file? After my installation there were all commented out and changed to reflect different mount points under export.
Thanks.

Just to follow up on this:
All of my strange problems (NFS unable to mount, iSCSI unable to login, vi hanging, VNC console session blank) were related to using jumbo frames on a switch that didn't support them. I had MTU=9000 set on my interfaces to try and speed up iSCSI/NFS and it turns out that causes a lot of funky network issues if your switch doesn't support it properly. The funny thing is that ping and all sorts of network tools ran flawlessly...
Be careful with jumbo frames... just a word of warning.

Unwanted shared NFS mount to Host.local on restart?

I've noticed lately that when I restart my machine, I get a listing in the Shared sidebar in Finder for Hostname.local. It's an NFS mount to some directory called "shared". I haven't tracked it down in the file system yet...
Any idea where this is coming from or how I'd get rid of it? It's kind of unnerving to see-- I don't think I've knowingly set up this mountpoint, and it has the feel of something trying to work around filesystem security. The mounted directory is empty, however...

check in system preferences ->login items or under finder pref to uncheck it.

Vi error on nfs mount; E212: Can't open file for writing

Hi all,
I've setup a umask of 0 for testing on both NFS client (Centos 5.2) and NFS server (OSX 10.5.5 server).
I can create files as one user and edit/save out as another user w/o issue when directly logged into the server via ARD.
However, when I attempt the same from an NFS mount on a client machine, even as root I get the following error using vi;
"file" E212: Can't open file for writing
Looking at the system.log file on the server, I see;
kernel[0]: add_fsevent: no name hard-link! dropping the event. (event 2 vp == 0xa5db510 (-UNKNOWN-FILE)).
This baffles me. My umask is 0 meaning files I create and attempt to edit as other users are 777, but I cannot save out edits unless I do a wq! in vi. At that point, the owner of the file changes to whomever did the vi.
This isn't just a vi issue as it happens using any editor, but I like to use vi.
Any help is greatly appreciated. Hey, beer is on me!

Hi all,
Thanks for the replies
I've narrowed it down to a Centos client issue.
Everything works fine using other Linux based OS's as clients.
Since we have such a huge investment in Centos, I must figure out a workaround. Apple support wasn't much help as usual however they were very nice.
There usual response is "its unsupported".
If Apple really wants to play in the enterprise of business space, they really need to change there philosophy. I mean telling me that I shouldn't mount home directories via NFS is completely rediculus.
What am I supposed to use then, Samba of AFP? No, I don't think so. No offense to Microsoft but why would I use a Windows based file sharing protocol to mount network shares in a Nix env???

Problems setting up an NFS server

Hi everybody,
I just completed my first arch install. :-)
I have a desktop and a laptop, and I installed Arch on the desktop (the laptop runs Ubuntu 9.10). I had a few difficulties here and there, but I now have the system up and running, and I'm very happy.
I have a problem setting up an NFS server. With Ubuntu everything was working, so I'm assuming that the Ubuntu machine (client) is set-up correctly. I'm trying to troubleshoot the arch box (server) now.
I followed this wiki article: http://wiki.archlinux.org/index.php/Nfs
Now, I have these problems:
- when I start the daemons, I get:
[root@myhost ~]# /etc/rc.d/rpcbind start
:: Starting rpcbind [FAIL]
[root@myhost ~]# /etc/rc.d/nfs-common start
:: Starting rpc.statd daemon [FAIL]
[root@myhost ~]# /etc/rc.d/nfs-server start
:: Mounting nfsd filesystem [DONE]
:: Exporting all directories [BUSY] exportfs: /etc/exports [3]: Neither 'subtree_check' or 'no_subtree_check' specified for export "192.168.1.1/24:/home".
Assuming default behaviour ('no_subtree_check').
NOTE: this default has changed since nfs-utils version 1.0.x
[DONE]
:: Starting rpc.nfsd daemon [FAIL]
- If I mount the share on the client with "sudo mount 192.168.1.20:/home /media/desktop", IT IS mounted but I can't browse it because I have no privileges to access the home directory for the user.
my /etc/exports looks like this:
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
/home 192.168.1.1/24(rw,sync,all_squash,anonuid=99,anongid=99))
/etc/conf.d/nfs-common.conf:
# Parameters to be passed to nfs-common (nfs clients & server) init script.
# If you do not set values for the NEED_ options, they will be attempted
# autodetected; this should be sufficient for most people. Valid alternatives
# for the NEED_ options are "yes" and "no".
# Do you want to start the statd daemon? It is not needed for NFSv4.
NEED_STATD=
# Options to pass to rpc.statd.
# See rpc.statd(8) for more details.
# N.B. statd normally runs on both client and server, and run-time
# options should be specified accordingly. Specifically, the Arch
# NFS init scripts require the --no-notify flag on the server,
# but not on the client e.g.
# STATD_OPTS="--no-notify -p 32765 -o 32766" -> server
# STATD_OPTS="-p 32765 -o 32766" -> client
STATD_OPTS="--no-notify"
# Options to pass to sm-notify
# e.g. SMNOTIFY_OPTS="-p 32764"
SMNOTIFY_OPTS=""
# Do you want to start the idmapd daemon? It is only needed for NFSv4.
NEED_IDMAPD=
# Options to pass to rpc.idmapd.
# See rpc.idmapd(8) for more details.
IDMAPD_OPTS=
# Do you want to start the gssd daemon? It is required for Kerberos mounts.
NEED_GSSD=
# Options to pass to rpc.gssd.
# See rpc.gssd(8) for more details.
GSSD_OPTS=
# Where to mount rpc_pipefs filesystem; the default is "/var/lib/nfs/rpc_pipefs".
PIPEFS_MOUNTPOINT=
# Options used to mount rpc_pipefs filesystem; the default is "defaults".
PIPEFS_MOUNTOPTS=
/etc/hosts.allow:
nfsd: 192.168.1.0/255.255.255.0
rpcbind: 192.168.1.0/255.255.255.0
mountd: 192.168.1.0/255.255.255.0
Any help would be very appreciated!

Thanks, I finally got it working.
I realized that even though both machines had the same group, my Ubuntu machine (client) group has GID 1000, while the Arch one has GID 1001. I created a group that has GID 1001 on the client, and now everything is working.
I'm wondering why my Arch username and group both have 1001 rather than 1000 (which I suppose would be the default number for the first user created).
Anyway, thanks again for your inputs.

How to umount a busy NFS mount in solaris 2.6?

How can I umount a busy NFS mount in solaris 2.6 without rebooting the machine? I've tried to check what processes that might hold the mount with the command 'fuser -c /home/user' but it reports nothing.
I wish I had solaris 8 so I could use 'umount -f'...
Can anyone help me?

If your nfs mount is under autofs' control, you would run into issue. Give this a try.
# /etc/init.d/autofs stop
# fuser -ck /home/user
# umount /home/user

Are nfs mounts allowed in vfstab after a flash archive restore?

I am restoring a server using a flash archive. The vfstab on the original server contains an entry for an nfs mount. It looks like during the push of the archive to the new server, the vfstab gets saved to vfstab.orig and the nfs mount is removed from vfstab. So I added a finish script to add the nfs mount back to vfstab and now the server gets hung during S73nfs.client during reboot.
Are nfs mounts not allowed in vfstab after a flash archive restore?

One option is to secure the OBP with a password.
At the OK prompt, set the security-mode to "command" and then set a password. Careful not to loose this password. With this set the only option is to "boot" without supplying the firmware password.
Commands:
# halt
ok setenv security-mode = command
ok setent security-password <enterpasswd>
ok reset-all

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

Permanent NFS Mount

Hi
I'm trying to figure out how to create a permanent NFS mount on my 10.5.6 Server hosts. Using Directory Utility seems to only create autofs mounts - which I've had trouble with in the past on other platforms, so I'm not very trusting of it.
/etc/fstab.hd is apparently ignored, so I'm not sure how else to get a permanent mount. Is it even possible on Leopard Server?
Thanks.

I also found that nested / heirarchical mounts don't work with the Apple version of Sun's automounter. I thought for sure if I made a ``multiple mounts'' entry they would work since AIUI in this case the automounter gets to see the whole proposed subtree at once from a single Directory Services lookup, but no, it doesn't work either. There are ``multiple mounts'' examples on both Apple's man page and Sun's, but on Sun's page the example is nested and on Apple's it isn't. I guess that's a kind of transparency, but a rather CYA-ish kind that leaves us out here wagging our jaws quite a bit when we expect it to behave like other automounters.
However! nested mounts with the 'net' option DO work. ?!
and in this case unlike the traditional Sun ``multiple mounts'' case, the automounter must build the tree with multiple Directory Services lookups not just one. How can it even do that? Is it Searching the directory instead of doing a simple Lookup?
I can load all the mounts into Open Directory as separate, nodes, or whatever you call them, like this:
cat > nested-example
0x0A 0x5C 0x3A 0x2C dsRecTypeStandard:Mounts 3 dsAttrTypeStandard:RecordName dsAttrTypeStandard:VFSType dsAttrTypeStandard:VFSOpts
terabithia\:/arrchive/incoming:nfs:nosuid,nodev,hard,intr,net
terabithia\:/arrchive/Radio:nfs:nosuid,nodev,hard,intr,net
terabithia\:/arrchive/backup:nfs:nosuid,nodev,hard,intr,net
terabithia\:/arrchive/ebooks:nfs:nosuid,nodev,hard,intr,net
terabithia\:/arrchive/fonts:nfs:nosuid,nodev,hard,intr,net
terabithia\:/arrchive/movies:nfs:nosuid,nodev,hard,intr,net
terabithia\:/arrchive/music/Antoine:nfs:nosuid,nodev,hard,intr,net
terabithia\:/arrchive/music/Lauren:nfs:nosuid,nodev,hard,intr,net
terabithia\:/arrchive/music/Roger:nfs:nosuid,nodev,hard,intr,net
terabithia\:/arrchive/music/jen:nfs:nosuid,nodev,hard,intr,net
terabithia\:/arrchive:nfs:nosuid,nodev,hard,intr,net
^D
dsimport -g nested-example /Local/Default I -u someadminuser
and they will show up under /Network/Servers/terabithia/arrchive. I can no longer choose the mountpoint myself, which is a disadvantage for more than vanity---with the Solaris automounter, it's possible to build a single nested tree on the client out of filesystems pulled in from a bunch of different NFS servers, while the Mac's 'net' naming convention straightjackets me into only rebuilding trees that exist within one NFS server.
Also, this works on 10.4, too, though in that case of course you use netinfo or niload fstab instead of dsimport.
Now can someone explain why 'net' suddenly works so much better? And is there a hidden downside to using it?

Since update to 10.4.10 NFS-mounts stopped mounting

Since the update to 10.4.10 (with or without the security update, didn't matter) my NFS-mounts from a Linux-machine via a WLAN-router and Airport to my MacBook Pro.
It did work, although apple-typically unreliable, until the 10.4.10 update.
rpcinfo -p machine shows:
program vers proto port
100000 2 tcp 111 portmapper
100000 2 udp 111 portmapper
100005 1 udp 797 mountd
100005 1 tcp 800 mountd
100005 2 udp 797 mountd
100005 2 tcp 800 mountd
100005 3 udp 797 mountd
100005 3 tcp 800 mountd
schowmount -e machine:
Exports list on dream:
/var/mnt/hdd/Bilder 192.168.233.9/255.255.255.0
/var/mnt/hdd/Tools 192.168.233.9/255.255.255.0
/var/mnt/hdd/movie 192.168.233.9/255.255.255.0
/var/mnt/hdd/Musik 192.168.233.9/255.255.255.0
/hdd/usbstick 192.168.233.9/255.255.255.0
showmount -d machine:
Directories on dream:
/var/mnt/hdd/Bilder
/var/mnt/hdd/Musik
/var/mnt/hdd/movie
192.168.233.9/255.255.255.0
Therefore everything looks ok at the Linux-side, another Linux-machine is able to mount the shares without problems.
The console.log shows:
NFS Portmap: RPC: Program not registered
NFS Portmap: RPC: Program not registered
Jul 15 18:11:50 alu automount[280]: Attempt to mount /automount/Servers/dream/hdd/Musik returned 1 (Operation not permitted)
Jul 15 18:11:50 alu automount[280]: Attempt to mount /automount/Servers/dream/hdd/Bilder returned 1 (Operation not permitted)
Jul 15 18:11:50 alu automount[280]: Attempt to mount /automount/Servers/dream/hdd/Tools returned 1 (Operation not permitted)
Jul 15 18:11:50 alu automount[280]: Attempt to mount /automount/Servers/dream/hdd/movie returned 1 (Operation not permitted)
NFS Portmap: RPC: Program not registered
NFS Portmap: RPC: Program not registered
[...Masses of those lines]
NFS Portmap: RPC: Program not registered
2007-07-15 18:14:55.992 NetInfo Manager[499] * -[NSCFString substringFromIndex:]: Range or index out of bounds
NFS Portmap: RPC: Program not registered
NFS Portmap: RPC: Program not registered
NFS Portmap: RPC: Program not registered
NFS Portmap: RPC: Program not registered
[.... masses of those lines]
I tried with NFS Manager - no luck.
I checked the Netinfo-DB - no luck.
I rebooted the MacBook Pro - no change.
I rebooted the Linuxmachine - no change.
I typed "mount -t nfs ..." into a terminal - no luck.
It is working with Linux - what prevents Apple to get it to work, too?

This error appeared once and never again since.
But NFS-mounts still fail. A friends Titanium, still on 10.4.9, has the normal problems with airport-connection-stability and believed-server-connection-losses but it connects like a charm to that server the Aluminium doesn't like.
I reinstalled 10.4.10, rebooted several times, repaird permissions, searched system.log and console.log but couldn't find a message pointing to a problem (with the exception of a message about a failing startup of my flying butress firewall.
Here you have the latest system.log (deleted some lines for security reasons only):
Jul 16 16:35:22 alu SystemStarter[1322]: authentication service (1332) did not complete successfully
Jul 16 16:35:22 alu SystemStarter[1322]: Printing Services (1325) did not complete successfully
Jul 16 16:35:24 alu Parallels: Unloading Network module...
Jul 16 16:35:24 alu Parallels: Unloading ConnectUSB module...
Jul 16 16:35:24 alu Parallels: Unloading Monitor module...
Jul 16 16:35:28 alu SystemStarter[1322]: BrickHouse Firewall (1338) did not complete successfully
Jul 16 16:35:29 alu SystemStarter[1322]: The following StartupItems failed to properly start:
Jul 16 16:35:29 alu SystemStarter[1322]: /System/Library/StartupItems/AuthServer
Jul 16 16:35:29 alu SystemStarter[1322]: - execution of Startup script failed
Jul 16 16:35:29 alu SystemStarter[1322]: /System/Library/StartupItems/PrintingServices
Jul 16 16:39:57 localhost kernel[0]: hi mem tramps at 0xffe00000
Jul 16 16:39:58 localhost kernel[0]: PAE enabled
Jul 16 16:39:58 localhost kernel[0]: standard timeslicing quantum is 10000 us
Jul 16 16:39:58 localhost kernel[0]: vmpagebootstrap: 254317 free pages
Jul 16 16:39:58 localhost kernel[0]: migtable_maxdispl = 71
Jul 16 16:39:58 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Jul 16 16:39:58 localhost kernel[0]: 89 prelinked modules
Jul 16 16:39:58 localhost kernel[0]: ACPI CA 20060421
Jul 16 16:39:58 localhost kernel[0]: AppleIntelCPUPowerManagement: ready
Jul 16 16:39:58 localhost kernel[0]: AppleACPICPU: ProcessorApicId=0 LocalApicId=0 Enabled
Jul 16 16:39:58 localhost kernel[0]: AppleACPICPU: ProcessorApicId=1 LocalApicId=1 Enabled
Jul 16 16:39:58 localhost kernel[0]: Copyright (c) 1982, 1986, 1989, 1991, 1993
Jul 16 16:39:58 localhost kernel[0]: The Regents of the University of California. All rights reserved.
Jul 16 16:39:58 localhost kernel[0]: using 5242 buffer headers and 4096 cluster IO buffer headers
Jul 16 16:39:58 localhost kernel[0]: Enabling XMM register save/restore and SSE/SSE2 opcodes
Jul 16 16:39:58 localhost kernel[0]: Started CPU 01
Jul 16 16:39:58 localhost kernel[0]: IOAPIC: Version 0x20 Vectors 64:87
Jul 16 16:39:58 localhost kernel[0]: ACPI: System State [S0 S3 S4 S5] (S3)
Jul 16 16:39:58 localhost kernel[0]: Security auditing service present
Jul 16 16:39:58 localhost kernel[0]: BSM auditing present
Jul 16 16:39:58 localhost kernel[0]: disabled
Jul 16 16:39:58 localhost kernel[0]: rooting via boot-uuid from /chosen: 4EF96DEE-9FCF-4476-AD53-58BEA0AA953E
Jul 16 16:39:58 localhost kernel[0]: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict>
Jul 16 16:39:58 localhost kernel[0]: USB caused wake event (EHCI)
Jul 16 16:39:58 localhost kernel[0]: FireWire (OHCI) Lucent ID 5811 PCI now active, GUID 0016cbfffe66af32; max speed s400.
Jul 16 16:39:58 localhost kernel[0]: Got boot device = IOService:/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/SATA@1F,2/AppleAHCI/PRT2 @2/IOAHCIDevice@0/AppleAHCIDiskDriver/IOAHCIBlockStorageDevice/IOBlockStorageDri ver/FUJITSU MHV2100BH Media/IOGUIDPartitionScheme/Customer@2
Jul 16 16:39:58 localhost kernel[0]: BSD root: disk0s2, major 14, minor 2
Jul 16 16:39:59 localhost kernel[0]: CSRHIDTransitionDriver::probe:
Jul 16 16:39:59 localhost kernel[0]: CSRHIDTransitionDriver::start before command
Jul 16 16:39:59 localhost kernel[0]: CSRHIDTransitionDriver::stop
Jul 16 16:39:59 localhost kernel[0]: IOBluetoothHCIController::start Idle Timer Stopped
Jul 16 16:39:59 localhost kernel[0]: Jettisoning kernel linker.
Jul 16 16:39:59 localhost kernel[0]: Resetting IOCatalogue.
Jul 16 16:39:59 localhost kernel[0]: display: family specific matching fails
Jul 16 16:39:59 localhost kernel[0]: Matching service count = 0
Jul 16 16:39:59 localhost kernel[0]: Matching service count = 21
Jul 16 16:39:59 localhost kernel[0]: Matching service count = 21
Jul 16 16:39:59 localhost kernel[0]: Matching service count = 21
Jul 16 16:39:59 localhost kernel[0]: Matching service count = 21
Jul 16 16:39:59 localhost kernel[0]: Matching service count = 21
Jul 16 16:39:59 localhost kernel[0]: display: family specific matching fails
Jul 16 16:39:59 localhost kernel[0]: Previous Shutdown Cause: 0
Jul 16 16:39:59 localhost kernel[0]: ath_attach: devid 0x1c
Jul 16 16:39:59 localhost kernel[0]: mac 10.3 phy 6.1 radio 10.2
Jul 16 16:39:59 localhost kernel[0]: IPv6 packet filtering initialized, default to accept, logging disabled
Jul 16 16:40:00 localhost lookupd[47]: lookupd (version 369.6) starting - Mon Jul 16 16:40:00 2007
Jul 16 16:40:03 localhost DirectoryService[55]: Launched version 2.1 (v353.6)
Jul 16 16:40:05 localhost diskarbitrationd[45]: disk0s2 hfs 9AC36BC8-2C3E-3282-B08D-9C22EC354E35 Alu HD /
Jul 16 16:40:07 localhost kernel[0]: yukonosx: Ethernet address 00:xx:xx:xx:xx - deleted
Jul 16 16:40:07 localhost mDNSResponder: Couldn't read user-specified Computer Name; using default “Macintosh-00.........” instead
Jul 16 16:40:07 localhost kernel[0]: AirPort_Athr5424ab: Ethernet address 00:xx:xx:xx:xx - deleted
Jul 16 16:40:07 localhost mDNSResponder: Couldn't read user-specified local hostname; using default “Macintosh-00..........” instead
Jul 16 16:40:08 localhost mDNSResponder: Adding browse domain local.
Jul 16 16:40:09 localhost lookupd[70]: lookupd (version 369.6) starting - Mon Jul 16 16:40:09 2007
Jul 16 16:40:09 localhost configd[43]: AppleTalk startup
Jul 16 16:40:09 alu configd[43]: setting hostname to "alu.local"
Jul 16 16:40:13 alu kernel[0]: Registering For 802.11 Events
Jul 16 16:40:13 alu kernel[0]: [HCIController][setupHardware] AFH Is Supported
Jul 16 16:40:15 alu configd[43]: AppleTalk startup complete
Jul 16 16:40:15 alu configd[43]: AppleTalk shutdown
Jul 16 16:40:15 alu configd[43]: AppleTalk shutdown complete
Jul 16 16:40:18 alu configd[43]: AppleTalk startup
Jul 16 16:40:20 alu mDNSResponder: getifaddrs ifa_netmask for fw0(7) Flags 8863 Family 2 169.254.113.87 has different family: 0
Jul 16 16:40:20 alu mDNSResponder: SetupAddr invalid sa_family 0
Jul 16 16:40:23 alu SystemStarter[51]: BrickHouse Firewall (102) did not complete successfully
Jul 16 16:40:27 alu configd[43]: AppleTalk startup complete
Jul 16 16:40:29 alu configd[43]: executing /System/Library/SystemConfiguration/Kicker.bundle/Contents/Resources/enable-net work
Jul 16 16:40:29 alu configd[43]: posting notification com.apple.system.config.network_change
Jul 16 16:40:29 alu lookupd[169]: lookupd (version 369.6) starting - Mon Jul 16 16:40:29 2007
Jul 16 16:40:31 alu mDNSResponder: getifaddrs ifa_netmask for fw0(7) Flags 8863 Family 2 169.254.113.87 has different family: 0
Jul 16 16:40:31 alu mDNSResponder: SetupAddr invalid sa_family 0
Jul 16 16:40:31 alu /System/Library/CoreServices/loginwindow.app/Contents/MacOS/loginwindow: Login Window Application Started
Jul 16 16:40:31 alu SystemStarter[51]: The following StartupItems failed to properly start:
Jul 16 16:40:31 alu SystemStarter[51]: /Library/StartupItems/Firewall
Jul 16 16:40:31 alu SystemStarter[51]: - execution of Startup script failed
Jul 16 16:40:33 alu loginwindow[182]: Login Window Started Security Agent
Jul 16 16:40:48 alu configd[43]: target=enable-network: disabled
Jul 16 16:44:14 alu /System/Library/PrivateFrameworks/Apple80211.framework/Resources/airport: Currently connected to network WZ
Jul 16 16:45:40 alu automount[222]: Can't get NFS_V3/TCP port for dream
Jul 16 16:45:40 alu automount[222]: Can't get NFS_V2/TCP port for dream
Jul 16 16:45:40 alu automount[222]: Attempt to mount /automount/static/mnt returned 1 (Operation not permitted)

Removing desktop icon of NFS mounted drive

Hi,
I have an NFS mounted drive (on a linux server) on my mac mini, running OS 10.4. I don't want the icon to appear on the desktop. Is there any way to remove this?
The reason is as follows:
- the NFS mounted directory is of the form servername:/home which contains home directories for all the students. This is mounted to /Volumes/servername. The students home directories are set to /Volumes/servername/userid. Thus, in the finder, their home directory shows up correctly, and they can browse their network files.
- However, /Volumes/servername is shown as a mounted disk icon on the desktop, and if students open this, they get a list of everyone's home directories, which they have to scroll through to reach their own home directory. This gives them immediate access to other people's home directories. Granted, these should all be locked and inaccessable to them, but if anyone has messed up their permissions, everyone will instantly be able to see that there is no red X by the home directory, and they can browse in.
- I realise people can browse in anyway, through the Finder, but its just nice not to make it quite so obvious to them.
So... any ideas on how to remove this desktop icon? Note that it needs to be removed for all users (a hundred or so students, logging in through LDAP).
Thanks!
Richard Grant
Mac Mini Mac OS X (10.4.3)

I have figured this out now...
If you mount the directories at the point /home (or at least ask it to - in fact it mounts it somewhere in /private) then the desktop icon is not displayed by default.
Richard

NFS Mounted Directory And Files Quit Responding

I mounted a remote directory using NFS and I can access the mount point and all of its sub-directories and files. After a while, all of the sub-directories and files no longer respond when clicked; in column view there is no longer an icon nor any statistics for those files. If I go back and click on Network->Servers->myserver->its_subdirectories, it will eventually respond again.
I have found no messages in the system log. And nfsstat shows no errors.
I am using these these mount parameters with the Directory Utility->Mounts tab:
ro net -P -T -3
Any idea why the NFS mounted directories and files quit responding?
Thanks.

I may have found an answer to my own question.
It looks like automount will automatically unmount a file system if it has not been accessed in 10 minutes. This time-out can be changed using the automount command. I am going to try increasing this time-out value.
Here is part of the man page:
SYNOPSIS
automount [-v] [-c] [-t timeout]
-t timeout
Set to timeout seconds the time after which an automounted file
system will be unmounted if it hasn't been referred to within
that period of time. The default is 10 minutes (600 seconds).

Removing NFS mounts after upgrade

In Tiger, I had set up a number of static NFS mounts to a Linux server using NetInfo. After upgrading to Leopard, these static links are no longer working, but the newly created automounts using Directory Utility work fine. I've been trying to remove the old entries using dscl without success. I have a number of entries in /Local/Default/Mounts, eg:
$ dscl localhost -read /Local/Default/Mounts/doobage:\/home\/michael
dsAttrTypeNative:type: nfs
AppleMetaNodeLocation: /Local/Default
GeneratedUID: B719E4FA-33F7-449A-AD63-0452515F0FF2
RecordName: doobage:/home/michael
RecordType: dsRecTypeStandard:Mounts
VFSLinkDir: /server/michael
I've tried deleting these using the dscl -delete command, eg:
$ sudo dscl localhost -delete /Local/Default/Mounts/doobage:\/home\/michael
Password:
delete: Invalid Path
<dscl_cmd> DS Error: -14009 (eDSUnknownNodeName)
I suspect that I'm simply using the wrong key name, however, there aren't any examples of deletion in the dscl man page. Can someone please point out where I'm going wrong?
Thanks,
-Michael

Try to escape the Slash with a double backslash.
Message was edited by: sica187

Best NFS mount options from Linux to Xsan?

So we are adding Linux clients to our network and I'm looking to learn the best NFS mount options to put in the fstab file. Right now they are set "defaults 0 0" and we are having problems. I assume because they are hard mounting. This is from the /proc/mounts file for one of the clients connecting to the Xsan:
10.X.X.X:/snet /snet nfs rw,relatime,vers=3,rsize=65536,wsize=65536,namlen=255,hard,proto=tcp,timeo=600, retrans=2,sec=sys,mountaddr=10.X.X.X,mountvers=3,mountport=706,mountproto=udp,ad dr=10.X.X.X 0 0
Xsan 2.2, 2 MDCs running 10.6.4, Promise Array.

So we have finally solved this. It turns out that the defaults work just fine. Our issues were solved by changing which MDC was hosting the export, dividing up the workload a bit, our primary was running out of RAM.
Secondly, I added intr and soft to the NFS options, the smoothed things out further.

Setting umask on NFS mounts under OS X 10.6

Similar Messages

Maybe you are looking for