NFS - Tiger

I'm not sure which forum this needs to go into, so I'll put it into the General Tiger one. I have a bunch of mac minis, most of which have Tiger, 2 have leopard. I am trying to AutoMount NFS Shares on the Tiger machine, which is not working. I have the same setup for the leopard machines, and all is well with the world. My question is this, is there any way to upgrade the tiger machines to the leopard NFS Utilities (most likely including portmap(per).
Thanks.

HI JS and Welcome to Apple Discussions ..
I don't think Tiger has the same security levels as does Leopard... that might be why your Tiger machines (AutoMountNFS) isn't working. Hence, if there is a way to upgrade the Tiger based machines to Leopard NFS Utilities... I can't see how that could work. Sorry ... Can you upgrade so they are all on Leopard?
Carolyn

Similar Messages

  • NFS: Leopard Client - Tiger Server

    We have a 10.4.10 System running as a server for all user accounts. The home directories are exported to the clients via NFS. With Tiger everything works out fine, but I started experimenting with integrating Leopard Clients.
    When I try to log in with SSH I get this error +'Could not chdir to home directory /home/user: Input/output error'+
    When I try to ls the home, it's empty. I wonder why the mounted home directory appears to be empty?
    In former times, one could see the NFS mounts as a link to some automount/static..., in Leopard I miss this. There seems to be some massive changes to the automounter?
    Sorry for the bad english.
    zwitcher

    I have a Tiger Server 10.4.11 and have a client on Leopard 10.5.5. I was having the same issue you were having and was getting all question marks when logging in. The issue was resolved after I selected LDAP Mapping "From Server" instead of Open Directory. However, now I have a delay when Authenticating of 20 seconds.

  • Xserver Tiger Nfs trouble

    Hi,
    We have an Xserver with Tiger 10.4.11 associated to an Xraid and Xsan. The filesystem is shared with nfs on Linux computer (Fc8,Fc10).
    Recently we have trouble with the Nfs Share : some 32 bits clients can't write file on the filesystem ; I see some issue :
    - the first one is to pass the -nfsvers2 parameter, but another trouble comes with the file size limitation to 2Go.
    - I'd like to try another issue with the -client32 parameter but I don't see where put this option on the Xserve.
    Has anyone have those trouble yet and try this issues ?
    regards
    N. Ménard

    How easy would it be to perform an Archive and Install, just on your machine? It is easy enough, with one caveat:
    All your third party Contextual Menus, Prefernce Panes, and Application Support, etc, would disappear, and need reinstalled. Examples are keyboards needing drivers, or Stuffit, if you use it's contextual menu features.
    This might "clean out" the problem.

  • How can a mount a NFS share exported from OpenBSD?

    Hello Apple Discussions:
    I've been experimenting with NFS in a mixed OS environment, and have been successful exporting nfs share with tigerserver, and mounting it on both a powerpc linux system, and on a powerpc openBSD system.
    Likewise, I can export a NFS share from the linux powerpc box, and mount it on the openBSD box and on the tigerserver, although, the latter required using the options (ro,sync,insecure) in my exports file.
    However, when I export a share on the OpenBSD box, I can mount it on the linux box, but not on tigerserver.
    I would like for the OpenBSD box to export a NFS share securely, with read-write permissions, to the tigerserver.
    After reading so many tutorials, that it would be a page of links, just to list them all, I am pulling my hair out. However, I have found one thread that suggests, that perhaps what I'm trying to do is impossible:
    http://www.bsdforums.org/forums/showthread.php?t=54308
    Here it is suggested that the NFS won't work because tigerserver is not using UTF-8?
    I will have to say, that I was somewhat alarmed, that the only times I succeeded in mounting an nfs share exported from linux onto tigerserver, it was when the "insecure" option is used in the /etc/exports file. There doesn't seem to be an equivalent for the linux style exports option "insecure", in the bsd style options of --maproot=user:group1:group2.
    But I don't like using any options that say "insecure" anyways, so rather than trying to find out how to make openbsd "insecure", I would rather like to find out if there is a way to get tigerserver using UTF-8, at least when mounting NFS shares, if this is indeed the issue.
    Here are the more technical details. I've created a user on all sytems named "fives" with the userid of 5555 and the groupid of 5555. I made the user local user in the local net info domain, but I've tried it with an LDAP user as well. The folders I wish to export and the folders into which to mount them are all owned by user fives and group fives, and have permissions set to 0775. The ip addresses are OpenBSD=192.168.222.111 TigerServer=192.168.222.233 LinuxPPC=192.168.222.253. I've included the relevant NFS setup files and running processes below:
    ON THE OPENBSD BOX:
    #/etc/exports
    /fives -alldirs -network=192.168.222.0 -mask=255.255.255.0
    /exports/fives -mapall=fives:fives 192.168.222.233 192.168.222.253
    #/etc/hosts.deny
    ALL: ALL
    #/etc/hosts.allow
    ALL: 192.168.222.233 192.168.222.253
    #/etc/rc.conf.local
    portmap=YES
    lockd=YES
    nfs_server=YES
    #here's proof that the daemons are running on the OpenBSD box;
    rpcinfo -p localhost
    program vers proto port
    100000 2 tcp 111 portmapper
    100000 2 udp 111 portmapper
    100005 1 udp 863 mountd
    100005 3 udp 863 mountd
    100005 1 tcp 613 mountd
    100005 3 tcp 613 mountd
    100003 2 udp 2049 nfs
    100003 3 udp 2049 nfs
    100003 2 tcp 2049 nfs
    100003 3 tcp 2049 nfs
    100021 1 udp 895 nlockmgr
    100021 3 udp 895 nlockmgr
    100021 1 tcp 706 nlockmgr
    100021 3 tcp 706 nlockmgr
    # actually, I don't see statd, but haven't found the equivalent in openbsd. There's rpc.rstatd, and maybe it should be listed here, but there doesn't seem to be a way to launch it directly. This is a competitor with the UTF-8 theory about why it's not working.
    ON THE TIGER SERVER:
    # here's proof that tiger server sees the mounts:
    showmount -e 192.168.222.111
    Exports list on 192.168.222.111:
    /fives 192.168.222.0
    /exports/fives 192.168.222.233 192.168.222.253
    # here's the result of user fives' attempt at mounting a share:
    sudo mount -t nfs 192.168.222.111:/exports/fives /imports/fives
    mount_nfs: /imports/fives: Permission denied
    # yet user fives has no problem mounting same share on linuxppc box.
    What is different about OSX server? I thought it was supposed to speak NFS?
    ---argh... I'm steppin out for a pint.. Hopefully when I'm back it'll just work.

    One thing not mentioned is that if you decide on the multiple user approach, you can have your music folder in Shared Documents so you only store the tracks once.
    Each user is free to choose which of those tracks they want in their library.
    There is an Apple help article on multiple users.
    http://docs.info.apple.com/article.html?artnum=300432

  • Files saved to NFS share by MS word cause finder to loose sync w/filesystem

    I am posting this bug report(#4699323, opened Aug 24th, 2006) I have open with Apple because there is no indication that they have even noticed it. Please reply if you have similar problems, questions, or suggestions. Bug report follows.
    24-Aug-2006 04:17 PM Erik Meitner:
    Summary:
    Files saved to an NFS volume by Microsoft Word dissappear from the Finder. Many times "Ghosted" icons of "Word Work Files" are left behind.
    Steps to Reproduce & Actual Results:
    1. Mount an NFS volume from a server(Mac or Linux, doesn't matter. NFS options do not matter.) from the Finder or command line.
    2. Open a Finder window to the mount point.
    3. Create a word document(test.doc), save to the NFS mount point.
    4. Make sure both the Word window and Finder window are visible.
    5. Type a single letter, Save.
    6. "Word Work File L_200098113"(the number varies.) apears and test.doc dissapears from the folder. Then the icon for "Word Work File L_200098113" goes "ghosted" (test.dc IS still there, just not shown. You can verify this in the shell )
    7. Type a letter, Save.
    8. The work file dissapears and is replaces by "Word Work File L_200098113"
    9. Rinse, Repeat ad infinitum.
    Expected Results:
    File saved & Finder does NOT get out of sync with the filesystem.
    Regression:
    * Only happens on NFS volumes.
    * Only happens with MS Word.
    * It happens on Panther(10.3.9) and Tiger(up to 10.4.7)
    * "Fast saves" in Word has no effect.
    * The user has full access to the root of the NFS volume.(a .TemporaryItems folder IS being created)
    * Verified that problem happens with all Versions of Office 2004 from 11.2.3 to 11.2.6(current).
    * Happens with ALL users: admin, local, and non-local(LDAP authenticated, network homes).
    Notes:
    * The work files(with "ghosted" icons) never show up when listing the folder via the CLI.
    * The original(test.doc) always shows in the CLI.
    * Relaunching the Finder usually causes the "missing" files to show again, but not always.
    * Problem is exacerbated by users losing faith in the system, thus saving very frequently, guaranteeing that the problem will always happen.
    * Only workaround is to have users work on files "off the network" on a local disk.
    30-Aug-2006 01:45 PM Erik Meitner:
    Screen shot attached showing initial state of Finder.
    '1.tiff' was successfully uploaded
    30-Aug-2006 01:46 PM Erik Meitner:
    Screen shot attached showing state of Finder after 1st save.
    '2.tiff' was successfully uploaded
    30-Aug-2006 01:47 PM Erik Meitner:
    Screen shot attached showing state of Finder after 3rd save.(2nd save same as 1st)
    '3.tiff' was successfully uploaded
    01-Sep-2006 08:37 AM Erik Meitner:
    Relaunching the Finder will restore the icons to the proper state most of the time. One can also use this application to force a refresh of a folders contents: http://www.brockerhoff.net/nudge/index.html
    I am not sure of the internal workings of "Nudge", but it does seem to be the best hack available to get the Finder to work properly.
    01-Sep-2006 08:48 AM Erik Meitner:
    I should also add that this problem is repeatable on 15 different Macs of different models, all running 10.3.9 with the latest updates.
    11-Sep-2006 12:41 PM Erik Meitner:
    Problem is repeatable on all 6 of our Machines running Tiger(10.4.7) with all the latest updates.
    20-Sep-2006 02:25 PM Erik Meitner:
    The "Nudge" tool mentioned previously does not always work especially for some users who experience this problem the worst. It will only restore the file to a "ghosted" icon that is still inaccessable.
    Moving the file to a different folder and deleting the resource fork file is the only solution in this case.

    OS X 10.4.8 update has not altered the behavior of this bug. The Office 2004 11.30 update seems to have caused the problem to happen less frequently. I would say it now happens half as frequently.

  • Incorrect file sizes shown in Finder over NFS and permissions issues

    Hi there
    This is a problem that existed for me in Leopard and has not been resolved in Snow Leopard.
    I have an XSan with a Leopard server sharing over NFS and AFP. When I connect from a Leopard or Snow Leopard client over NFS the file sizes in Finder are incorrectly displayed. My Tiger clients work perfectly.
    Also, although it says I have read write access to the files over NFS I cannot save over an existing file when I make changes to it, I instead have to create a new version of it and remove the old one.
    Check the link to show a grab of one of the folders in question, the upper window is what the NFS shows me, the lower AFP. If you Get Info on the files over either connection the byte count is identical.
    http://www.the-9000.com/images/finder_anomaly.tiff
    Any info would be greatly appreciated.

    This is a problem that existed for me in Leopard and has not been resolved in Snow Leopard.
    Have you filed a bug report with Apple?
    http://developer.apple.com/bugreporter/
    If not, there's less of a chance they'll know about it and help fix it for you.
    Do things look OK from the command line in Terminal?
    It would probably be useful to use a tool like Wireshark to check out what each protocol is sending over the wire. That could at least narrow it down to being a client or server issue.
    Thanks
    --macko

  • Nfs mount created with Netinfo not shown by Directory Utility in Leopard

    On TIger I used to mount dynamically a few directories using NFS.
    To do so, I used NetInfo.
    I have upgraded to Leopard and the mounted directories
    are still working, although Netinfo is not present anymore.
    I was expecting to see these mount points and
    modify them using Directory Utility, which has substituted Netinfo.
    But they are not even shown in the Mount panel of Directory Utility.
    Is there a way to see and modify NFS mount point previously
    created by NetInfo with the new Directory Utility?

    Thank you very much! I was able to recreate the static automount that I had previously had. I just had to create the "mounts" directory in /var/db/dslocal/nodes/Default/ and then I saved the following text as a .plist file within "mounts".
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    <key>dir</key>
    <array>
    <string>/Network/Backups</string>
    </array>
    <key>generateduid</key>
    <array>
    <string>0000000-0000-0000-0000-000000000000</string>
    </array>
    <key>name</key>
    <array>
    <string>server:/Backups</string>
    </array>
    <key>opts</key>
    <array>
    <string>url==afp://;AUTH=NO%20USER%[email protected]/Backups</string>
    </array>
    <key>vfstype</key>
    <array>
    <string>url</string>
    </array>
    </dict>
    </plist>
    I don't think the specific name of the .plist file matters, or the value for "generateduid". I'm listing all this info assuming that someone out there might care.
    I assume this would work for SMB shares also... if SMB worked, which it hasn't on my system since I installed leopard.

  • Tiger Server boots but refuses all connections

    Hi,
    I've had a trusty old Powermac G4 (AGP) running Tiger Server (10.4.11) for almost a year now. We use it to serve OD, NFS homes, MySQL & printing. Apart from the occasional issues setting up the mobile home folders, it has been doing great. It has 896 MB of RAM and 3 HDD (two 500 MB and one 80MB one).
    However, after suffering a power outage, the machine has stopped accepting any kind of connection to it (ssh, web, vnc, OD, nfs,...). Morever, although it seems to boot ok, we can't get past the login screen. Neither network nor local accounts are accepted.
    I've booted from an external installation media to check the system drive (repair disk and permissions) and things are still not working.
    Any ideas?

    Access it from another FireWire Mac via Target Disk Mode and then follow my standard instructions:
    Backup first
    It is always best to have a full bootable backup before you install. If you fail to do this you will be unable to return to this OS if you decide you don't like the new OS. Also there is a slight chance that an install could lose everything on the Mac. The backup must be to an external hard disk or another Mac. Preferably use Carbon Copy Cloner to make a bootable backup of the whole disk. If you do not have a disk or partition without an OS it will probably not be practical to produce a bootable OS at this stage so backup to a sparse disk image for the time being and ensure that you have sufficient partitions in future.
    Erase before the install
    Once you have a bootable backup on an external disk it is best to erase the internal disk with the new installer DVD before you install. I prefer to split disks into two partitions with a full OS on each so that one can be used to maintain the other.
    During the install
    Preferably do not import any data or preferences from earlier OSs during the install process as this can reintroduce bugs.

  • Cannot write to NFS mount with finder

    hi folks
    i have moved from a G4 cube running 10.4.9 to a new iMac running os x 10.5.7 (including upgrading from the old machine)
    the NFS mounts i used to have with my G4 cube are not working properly; new mounts i've created aren't working properly either.
    i can read/open file OK, but when i try to drag & drop files onto the NFS mount using the finder i get errors:
    "You may need to enter the name and password for an administrator on this computer to change the item named test.jpg" [ stop ] [ continue ]
    clicking "continue" i get:
    "The item test.jpg contains one or more items you do not have permission to read. Do you want to copy the items you are allowed to read? [ stop ] [ continue ]
    Choosing continue again results in the file appearing in the NFS directory, but with 0 size, and a time stamp of 1970.
    if i try to copy the same file using the Terminal, it works fine - so it is not a simple NFS permissions problem - it is something particular to the Finder.
    i am able to create a folder inside the NFS director by using the Finder.
    i thought at first it might be related to the .DS_Store and similar files being written, so i tried turning off that behaviour:
    defaults write com.apple.desktopservices DSDontWriteNetworkStores true
    but that hasn't fixed the problem
    there are no obvious messages in any of the logs
    any suggestions or pointers on how to fix this?

    thanks for the reply
    these articles appear to relate to sharing a mac filesystem via NFS: exporting the data.
    i am referring to mounting a NFS filesystem from another server onto the mac (leopard) client
    the mounting works fine: it's just the finder which isn't behaving. the finder worked in tiger; isn't in leopard.

  • Leopard with LDAP/NFS

    I've just installed Leopard on a MacMini that is used as a desktop machine for a network of computers. We've got 3 MacMini's - 2 of which running Tiger (10.4.11) and now one running Leopard.
    The machine running Leopard is able to authenticate using LDAP (ie. I can login with my LDAP username/password, as well as my local 'admin' account on the machine), but the LDAP accounts aren't mounting via nfs. I've made sure that the Directory Utility has the nfs share setup and mounting to the place that it should be mounting too (/home - which is where the macs running Tiger mount stuff too), but I still can't seem to get it to work.
    A 'sudo ls -la /home' returns nothing!
    I've been getting a bunch of messages in system.log that look something like the following:
    Nov 15 23:05:39 kali loginwindow[348]: FolderManager: Failed looking up user domain root; url='file://localhost/home/jimmyk/' path=/home/jimmyk/ err=-120 uid=0 euid=11107
    Has anyone got suggestions on what I can do to fix this? I've had a quick look around on Google and can't find much to help me (apart from the fact that NetInfo has been moved into the new-look Directory Utility).

    Leopard has a new feature which reserves the /home for auto_fs
    You need to disable this first.
    See this thread:
    http://discussions.apple.com/messageview.jspa?messageID=5665487&stqc=true

  • 10.4.3 breaks nfs  gcc on client

    I am doing embedded development on an arm 9 board running Debian 3.
    I have the debian root nfsroot served from a PB G4 17" with 10.4.3
    This setup worked in OS X 10.4.2. After the upgrade to 10.4.3 it no longer works.
    The bug is a subtle one. If I compile a file using gcc on the arm 9 and the
    a.out gets saved to the nfs file system (served by my PB).
    The a.out file does not have execute permissions as it should.
    This makes it impossible to build anything that uses a big make file.
    The test is simple put the following in a file say foo.c
    int main(){return 0;}
    run
    gcc foo.c
    the result should be a file a.out with execute permissions.
    However in 10.4.3 it doesn't.
    If I run gcc foo.c a second time without first deleting a.out, a.out will
    then have execute permissions. I believe because it doesn't have to create
    the file this time so no race condition when it sets the permissions.
    Once I detected the problem it took me a while to believe it was nfs that
    was the culprit. However if I do the nfs mount on 10.3.9 there is no problem.
    If I do the same gcc on the local flash file system of the ARM 9 a.out
    has execute permissions. In every case the nfs parameters are identical.
    I run the test as root. I discovered this problem while trying to build
    python from src.
    Anybode have any idea how I can reconfigure 10.4.3 nfs server to behave
    like 10.4.2? or what changed so that I can experiment with my
    client configuration to compensate?
    here is the fstab entry on my linux client
    10.0.2.150:/nfs/nfsroot/ / nfs defaults,noauto 0 0
    I believe the nfs client default options are as follows
    rsize = 1024
    wsize = 1024
    timeo = 7
    retrans = 3
    acregmin = 3
    acregmax = 60
    acdirmin = 30
    acdirmax = 60
    flags = hard, nointr, noposix, cto, ac
    and my nfs server export
    nidump exports .
    /Data/nfsroot -maproot=root -network=10.0.2.0 -mask=255.255.255.0
    my client is using nfs version 2
    I did an ethereal dump and when a.out gets execute permissions there is
    a pair of packets SETATTR call and reply that changes the permissions.
    When it doesn't work there is no SETATTR packets. So somehow nfs is messing
    up the behavior of gcc.

    I found a work around. If I disable attribute caching then the gcc problem is fixed. To disable attribute caching use the "noac" nfs option. This does not work if sync and dirsync are also enabled. Don't know why sync and dirsync would have a deleterious effect but seems to me the nfs on 10.4.3 must be fragile.
    #These two worked on tiger 10.4.3
    exec -c "console=ttyAM0,115200 ip=10.0.2.155:10.0.2.150:10.0.2.1:255.255.255.0:ts7250 nfsroot=10.0.2.150:/Data/nfsroot,noac"
    #fstab entry they have to match
    10.0.2.150:/Data/nfsroot/ / nfs noac,noauto 0 0

  • Client side: is it safe to add a line to NFS StartupItem for a mount?

    (posted this on tiger client board, but realized that this is actually a better forum for this)
    I need to mount an nfs share at boot on my clients.
    I dont want to use fstab, because I need a specific mount location (dont want it to add the /private/Network.. symlink)
    Right now, I added my nfs_mount line to the end of the startup section of /System/Library/StartupItems/NFS/NFS
    Is this a safe place to add something like this, or is there a better way/place to add such a thing? (I dont want a future update to dissolve my setup.)
      Mac OS X (10.4.6)  

    Any future software update may overwrite that file and you'll lose your mount.
    A better solution would be to write your own StartupItem (you can just copy the existing NFS one if you like, just change its name and settings in its StartupParameters.plist file).
    Alternatively you can add the mount info to your NetInfo directory which should ensure the volume is mounted at boot time. I've not used this method myself (I've taken the custom StartupItem path), but Mike Bombich has a write up on how it works.

  • Disk images from NFS on 10.4 "may be damaged" on 10.5

    Disk images (.dmg files) created with hdiutil on OS 10.4 mount with warnings on OS 10.5. BUT - only if the source directory was on an NFS file system.
    Specifically:
    On OS 10.4.11, I can run:
    cd /path/to/nfs/directory
    echo "hello world" > hello.txt
    hdiutil create -srcdir hello.txt hello.dmg
    Then on the 10.5 machine, I double click on hello.dmg and it says:
    "The disk image you are opening may be damaged and could damage your system.
    Are you sure you want to open the disk image?"
    If I say OK, it shows me the hello.txt file I expect, but the warning is troubling.
    Running verify in Utilities -> Disk Utility results in this output:
    / begin quote:
    Verifying volume "hello.txt"
    Checking Non-journaled HFS Plus volume.
    Detected a case-sensitive catalog.
    Checking Extents Overflow file.
    Checking multi-linked files.
    Checking Catalog hierarchy.
    HasFolderCount flag needs to be set (id = 2)
    (It should be 0x10 instead of 0)
    HasFolderCount needs to be set (id = 16)
    (It should be 0x10 instead of 0)
    HasFolderCount needs to be set (id = 17)
    (It should be 0x10 instead of 0)
    Incorrect folder count in a directory (id = 2)
    (It should be 2 instead of 0)
    Checking volume bitmap.
    Checking volume information.
    The volume hello.txt needs to be repaired.
    Error: Filesystem verify or repair failed.
    / end quote
    Running 'repair' reports a similar error and fails.
    Any ideas why this is happening?
    Thanks.
    p.s. Running the same hdiutil command on 10.5 results in a .dmg that doesn't give me a warning. The type of input file/directory (hello.txt vs a big directory full of files) doesn't matter, but the warning only comes up if the input file/directory was on an NFS filesystem.

    I am having a similar problem.
    I just updated clients to Leopard.
    Xserve is still running Tiger.
    Now clients cannot search files on the server.
    Apple support said Tiger clients used "cat search" instead of spotlight.
    Now that clients are Leopard, clients try to search with spotlight,
    but Tiger Server cannot search with spotlight.
    He suggested looking for a 3rd party cat search for Leopard clients.
    Any suggestions?

  • Migrate data from old machine via NFS

    I'm giving my mother a new mac mini for christmas. Her current mac mini (G4) is running Tiger.
    I plan on copying the old data via a simple NFS setup (I don't have a fireware cable so migrate assistant will apparently not work. Please correct me if I'm wrong). Or alternatively, simply via samba/cifs. Opinions are welcome.
    Are there any folders in her home directory that I should not copy?
    Is there possibly any valuable data elsewhere on the old machine?

    Some Excellent Information here from Pondini...
    Setting-up a new Mac from an old one, its backups, or a PC
    Transferring files from one User Account to another
    Using Migration Assistant on Lion
    Migration Assistant tips and tricks

  • 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

Maybe you are looking for