Tag Info

Hot answers tagged

2

The ._ files are AppleDouble files that are used to store metadata like extended attributes, ACLs, file flags, and resource forks. To delete them, run: find . -name ._\* -delete You can see if files have extended attributes, ACLs, or file flags with ls -l@eO. The ._ files are usually created because files have extended attributes. You can use xattr -c to ...


2

I have not tried this myself, and I realize the OP prefers native solutions, but nonetheless: There's an app called Asepsis that works by redirecting creation of those files into a special folder, i.e. in a way preventing them from appearing.


2

I'm having the exact same problem on my client. Looking at a WireShark trace, there is always a 45 second delay in opening the connection the the file share (OSX Server 3.1.2). Using SMB1 (CIFS) does the same thing and WireShark confirms SMB vs. SMB2. Any other ideas out there?


1

You can try this: find . -d -name "* " -type d -exec bash -c 'TO=$(echo "{}" | sed "s/.$//"); FROM=$(echo "{}"); mv "${FROM}" "${TO}"' \;


1

You could also add the alias as a Login item: go to System Preferences > Users & Groups, and click on Login Items. You can then drag a mounted network drive, or a drive alias, into the Login Items list.


1

Samba no more, for Lion Server mount.cifs needs extra options, "nounix,sec=ntlmssp" [root@50centos ~]# [root@50centos ~]# yum install samba-client samba-common cifs-utils ... [root@50centos ~]# mkdir /mnt/lion_smb [root@50centos ~]# mount -t cifs -o MikeCochran,trustno1,nounix,sec=ntlmssp //198.252.206.140/smb_share /mnt/lion_smb/ ...


1

I would set up a user to automatically log in and lock the screen immediately with a password (or as close to immediately as you care.) That will mount the external drive and start up sharin for all users. Alternatively, you could drop the $20 on OS X server and have it mount shares at boot like you rightly expect a server to behave.


1

The solution in our case was to make the user account "mobile" on the local mac (we were having problems with a domain user not being allowed access to an smb share on a domain member server). It was a problem on any Mavericks version where the domain user was not mobile.


1

The way to do it is to add the shared volume(s), not the machine to the "Favorites" section of the Finder sidebar. Connect to the server using the Finder menu item and mount all the volumes the user requires. Go to the machines Finder folder and you will see icons for all the mounted volumes. Drag them one by one into "Favorites". As an added bonus you will ...


1

The two places that come immediately to mind are the favorites section of Go to Server... so you might clear that out. Secondly, look in the Login Items pane of Users & Groups preference pane. Also, if more than one user logs in to the Mac, be sure to eject the share before fast user switching (or logging out all users but one) to prevent their mount ...


1

I will admit, I hadn't noticed that the defaults write command stopped working in Mavericks. However, when I DO clean network mounts, instead of your one liner find and rm, I use this: dot_clean . The manfile explains: dot_clean -- Merge ._* files with corresponding native files. I don't use the -m flag, but you may find it helpful in your situation. ...


1

Just tried, and this does work in Mavericks (at least for disabling .DS_Store not network shares): defaults write com.apple.desktopservices DSDontWriteNetworkStores -bool true You just need to remember to restart Finder as well: killall Finder


1

I've found the solution. Two commands are needed in sequence: sudo launchctl load -w /System/Library/LaunchDaemons/com.apple.smbd.plist sudo defaults write /Library/Preferences/SystemConfiguration/com.apple.smb.server.plist EnabledServices -array disk


1

You need to understand how mounting works. In short what you want is to: Mount your smb:// drive on a certain location. Use your file:// command as you always do. When you use 'Connect to Server' - ⌘K, your drive should be mounted somewhere in /Volumes/. So now you can use file://Volumes/drive-name. For normal use, like this, a mounted network ...


1

I've had to do this as well, and I have an Applescript I wrote and cobbled together from working sources to request the user's password and then use mount_smbfs to mount to a specific location (with folders already set up). This prevents stale passwords from quickly locking out the account, and also prevents passwords in the script body. I do hard-code the ...


1

Mavericks just introduced support for SMB2. http://www.apple.com/osx/whats-new/features.html#core SMB3 is a planned feature of the next version of OS X, Yosemite.


1

To further this: The SMB2 support in OS X 10.9 is rather buggy. It occasionally completely locks up requiring restart. At work, we've enforced SMB1 only, which can be done either by connecting with the cifs:// protocol, but since this can be hard to enforce for non-technical users, you can also write a preference file to either ...


1

1.) Your situation is not related to the open command. Before one can pass a remote share filepath as part of an argument, the share must first be established at a mount point. Here's an illustration to show what happens--or doesn't happen--using the simplest of commands: ls smb://myshare._smb._tcp.local/path/to/file/my_file.pdf Indeed, referencing a file ...


1

Here's one suggestion: http://superuser.com/questions/775539/custom-names-for-smb-shares-on-osx I've used a similar method to mount volumes using sshfs to particular mount points for iTunes and calibre and the like.


1

auto_fs method The two shares will be mounted automatically. Please create a Share folder and two folders Development and Live inside of that in your User folder and change your auto_master with sudo nano /etc/auto_master to /etc/auto_master # # Automounter master map # +auto_master # Use directory service /- ...


1

Are you using Windows 7/8 or XP? I know that when I at home switched from XP to Window 7, I needed to change the windows workgroup settings... It sounds like you don't have the proper workgroup assigned.



Only top voted, non community-wiki answers of a minimum length are eligible