Page 1 of 2 1 2 LastLast
Results 1 to 20 of 26

Thread: Crazy Scary permissions florf?

  1. #1
    Join Date
    Feb 2001
    Location
    on the landline, Mr. Smith
    Posts
    7,787

    Default

    So all of the talk in jacob's thread about the Server permissions bug(s) got me looking at our Server box - QS 733 running 10.2.6 Server, upgraded all way from 10.1.3 Server. I unchecked admin from one user (the only other "admin" account), deleted a couple of non-admin users that I knew were long dead, and also deleted some netboot users long dead as well. Normal admin stuff done in the Workgroup Manager app, nothing fancy or manual in the terminal...

    I decided to repair permissions and run disk utility on the two volumes that are on a second drive while I am there. Both are reported fine with no errors or problems, but one will not remount. OK, no problem I will just reboot.

    Reboot. neither volume mounts. Fearing a failing HD or snarfed up directory, I run DW 3 from CD, which sees and reports all volumes as fine (repairs very minor errors).

    Reboot. neither volume mounts. OK, maybe a bad drive, cable, or OS trouble. Machine is booting to the first volume fine, everything else looks good, just the second drive (two volumes) won't mount.

    So I throw the drive in question in another G4 running Jag, and what-da-ya-know, it mounts fine, everything looks perfect. I decide to backup the first drive (users and other data/sharepoints) via CCC on a FW drive that I always use with this G4.

    Whoa, FW drive won't mount now, but Disk Utility sees it, just like the florfed drive.

    OK, repair permissions again and reboot. Nothing.

    Start looking at permissions manully; Mac HD (boot drive) has No group whatsoever. Blank. And there is no "admin" in the group list.

    If I select "staff", reboot, and the FW drive mounts, but not the second internal drive... If I login as root, the drive does not mount. After backing up, I try to reinstall 10.2.6 Server (cause I *know* I don't know how to manually set system permissions), but can't get the RAM disc to mount: error 95.

    (to be continued...)

    __________________

    Charlie Don't Surf!

    [This message was edited by unclemac on Sat October 11, 2003 PT at 12:07.]

  2. #2
    Join Date
    Feb 2001
    Location
    on the landline, Mr. Smith
    Posts
    7,787

    Default

    OK, so let's recap: second drive won't mount, a struggle to mount a FW drive, and the update RAM disk won't mount... what is going on?

    I open the updater on a second machine, transfer the installer back and run it to reinsyall 10.2.6 Server. No problems.

    Reboot. Same thing - volumes don't mount. Repair permissions *again*, reboot, same thing. Reboot again and log in as root...

    Sucess! All volumes mount. So... maybe the problem is related to something specific to my "admin" acount. So I create a new admin account, reboot, and *poof* the two volumes are gone again.



    Reboot as root, and the volumes are back.



    I have done a bit of testing and all looks good for users connecting so far, and in fact the permissions for the 50 Gigs of files on the two volumes of the "here-it-is, whoops-no-its-not" drive appear to be correct and unchanged through all of that.

    At this point, all that I can think of (that I have not tried) is updating to 10.2.8 Server, which is merely blind hope. Not that deperate - yet.

    What on earth, perhaps related to permissions not repaired by "repairing permissions", or maybe a user pref, can cause drives not to mount?



    __________________

    Charlie Don't Surf!

    [This message was edited by unclemac on Fri October 10, 2003 PT at 22:42.]

  3. #3
    Join Date
    Jun 2002
    Location
    Campbell, CA, USA
    Posts
    732

    Default

    Is it possible that the drive's mounted, but just not showing up in Finder? (This is one them WAGs, not a certainty 'cause I ain't never actually seen this.)

    You didn't say how it was that you observed it not mounted. Did you check only in Finder or also in Terminal? In a terminal session (Terminal app or via ssh to the machine), enter the mount command, with no other options, and it reports all mounted volumes of any type. Does it report the volumes mounted even when you can't see 'em in Finder?

    I don't believe that "who's logged in" affects what's mounted (but see Note 2, at the end).
    ----

    First thing to check: did repair permissions (I've never trusted that program!) set the user, group, and filemode of the /Volumes directory such that your "admin" users can't read/execute through it? Do this in Terminal (possibly need to be root):

    ls -ld /Volumes

    (that's "ell-ess dash-ell-dee"). Output should look like:

    drwxrwxrwt  12 root  wheel  408 Oct 10 22:06 /Volumes

    If the permissions on the /Volumes directory won't allow an "admin" user to walk through it, Finder (an app running as the logged-in user) won't be able to read its contents and that's the bug. Finder has no idea what's mounted.

    Fix: as root:

    chmod 1777 /Volumes

    and rerun the ls to verify your fix.

    ----

    Here comes a description of how mounts work in Un*x OSes and another possible cause...

    You need two things for a mount: a file-system (on a local disk volume or network-served) and a directory on which to mount it (called the "mount-point"). The mount-point directory must pre-exist, at which point

    mount file-system /path/to/mount-point

    causes references to the /path/to/mountpoint/ directory to be switched from its parent disk to the "root directory of the mounted file-system". User access to file paths below the mount-point directory proceed seamlessly down the mounted file-system's hierarchy.

    A. Some Un*x OSes make the transition to the root of the mounted file-system without evaluating permissions of the underlying directory (on the parent file-system) on which it's mounted. This used to be the case on all of the Unices I toyed with.

    B. At some point or from a branch of Un*x I wasn't familiar with in the old days, access to the root of the mounted file-system switched to being gated first of all on the permissions of the underlying mount-point directory, then on the permissions of the root directory of the mounted file-system after that.

    So here's a theory: If, underneath the mounted file-systems, their mount-point directories have user, group, and filemode settings which don't allow your "admin" accounts to execute them, accounts in group "admin" won't be able to traverse to the root of the mounted file-system.

    The hard part is to examine the directory underneath the mount point. I'd say log into the system as root when no one else is using it, hop into Terminal, manually unmount the volume (eg. umount /Volumes/Data and then, if umount complains that it's in use, umount -f /Volumes/Data which cancels all programs accessing it, then unmounts it), then use ls -l /Volumes to see what the permissions are of the mount-point directory. eg. for /Volumes/Data:

    umount /Volumes/Data
    ls -l /Volumes
    mount /Volumes/Data

    and locate the the permissions for Data, or to get directly to the specific listing of /Volumes/Data, you could

    ls -ld /Volumes/Data

    while it's unmounted.

    Do the permissions make sense?

    If not, then something may be haywire with the startup scripts which carry out mounting all disks. These scripts actually create the mount-point directories under /Volumes (via the mkdir command) prior to issuing each mount. If they're not making globally-accessible directories, it's a bug in the startup scripts.

    ----

    Note 1: The automount daemon will mount a user's NFS home directory if you're set up for that, but that doesn't apply to local mounts. Also, those automounted NFS mounts, once referenced, stick around until explicitly umounted, as when the shutdown scripts run.

    Note 2: It's barely conceivable that some fancy config option allows for local volumes to be mounted at login and dismounted at logout of specific accounts, but again I've never heard of such a thing.

    ----

    Jazzbo

    [This message was edited by Jazzbo on Sat October 11, 2003 PT at 8:28.]

  4. #4
    Join Date
    Feb 2001
    Location
    on the landline, Mr. Smith
    Posts
    7,787

    Default

    Ha! I was callin' ya with my brain...


    By not mounting I mean yes, not showing up in the finder... but also:

    1)The drive and both partitions are visible but "grayed out" in Disk Utility, and the "mount volume" option is available in the pull down menu, but does not work (nothing happens). I can "check" or "repair" the drive, which apprears to work on both voumes, and reports they are "OK".

    2) In ASP, both HDs are visible, but there is no volume info for the second, non-mounting drive.

    3) The user and group management app - Workgroup Manager - does not see the two volumes (for AFP and SMBA), which are (were) sharepoints.

    Oh, and I forgot to mention earlier - when the desktop loads after a reboot I get a system warning: You have inserted a disk that is unrecognizable... etc., with only an "Ignore" button. As if the OS can can see it, but not read it... except of coarse when I boot/login as root, then no warning, all drives mount, and everything seems AOK.

    Did not attempt anything in the terminal yet, usually my last option

    I will reread your post, and may be able to get at the machine over the weekend, but maybe not before Monday...

    THANK YOU for your support!

    Put it on my tab... how will I ever repay the Gurus?



    Anybody think this has anything to do with the drive? Does not seem like it, but I don't pretend to know the ins-and-outs of HDs, HD drivers, and such things.

    The fact that the FW drive and RAM disk also acted strange took my attention elseware: OS.

    __________________

    Charlie Don't Surf!

  5. #5
    Join Date
    Jan 2001
    Location
    Mobius Strip
    Posts
    13,045

    Default

    Sounds like OS X's buggy disk arbitration (but is that part of IOKit kext or the partitions OS X creates and uses?). The folks at SoftRAID complain that there are problems with the "plumbing" at this stage of the game.

    SoftRAID doesn't use Apple partition scheme, which has meant that they aren't bootable for now, but might avoid problems and be more robust, too.

    I'm sure you can display the partition tables, for what help that is, from terminal. ATTO ExpressStripe gives you a graphic view of the drives and volumes (making it easier for me to identify the name/number of each drive and volume).

    10.0 provided for reinstalling. Now, if you want to refresh the system, you use the combined updater to hopefully repair or restore the system to how Apple wanted it.

  6. #6
    Join Date
    Feb 2001
    Location
    on the landline, Mr. Smith
    Posts
    7,787

    Default

    Hi TZ,

    I just turned in a PO before this happend for SR 3, now that it has been on the scene a while and all reports I have seen have been positive...

    Weighing the pros and cons: If I tranfer all data from drive/volumes in question to a pair of shiny new SATA drives (SR 3 mirrored) *could* that add too many varibles? Makes me nervous; new drives, and new SATA controller, and SR 3?

    None of which I have used yet... Playing with fire?

    I don't mind some risk, I'll just have to make about 4 seperate backups before I march forward with new hardware...

    __________________

    Charlie Don't Surf!

  7. #7
    Join Date
    Jan 2001
    Location
    Mobius Strip
    Posts
    13,045

    Default

    Charlie,

    I'd take up the thread on SATA in your case to another forum, thread.

    If you are still using PATA drives, SATA is one option (poor man's scsi) but I wouldn't do it NOW.

    In fact, I wouldn't recommend SATA and SR3 if you have a project (video, scientific) that runs for hours (overnight operations) with a lot of intense disk activity. I remember when, say, doing airflow wing design calculations would require a full week of computer time.

    Too bleeding edge. Make sure the swimming pool is FULL before diving in!

  8. #8
    Join Date
    Feb 2001
    Location
    on the landline, Mr. Smith
    Posts
    7,787

    Default

    right.

    Let's go over here to kick around hardware that is seperate (I hope) from this issue.

    __________________

    Charlie Don't Surf!

  9. #9
    Join Date
    Feb 2001
    Location
    on the landline, Mr. Smith
    Posts
    7,787

    Default

    ...This problem beating me.

    OK Jazz, from the terminal, logged in as root:

    "ls -ld /Volumes" returns "drwxrwxrwt 3 root wheel", so things are OK, yes? And no change: volunes mount when I reboot/log in as root, but not as admin.

    quote:
    These scripts actually create the mount-point directories under /Volumes (via the mkdir command) prior to issuing each mount. If they're not making globally-accessible directories, it's a bug in the startup scripts.



    Have not checked this yet, but if it is the bug you mentioned, what's the fix? Reinstall?



    Here's where it get's more crazy. At some point, the internal CD ROM (OEM Lite-on combo drive) stopped mounting! I used it on Friday to run DW 3, but now no CDs mount in the Finder, including a factory 10.2.3 Disc. Tried booting to CD by holding down the "C" key, and it booted back the the HD....

    Just for grins I performed an Open Firmware reset - no change.

    Through about a dozen reboots, all stayed the same: root = mount, admin = no mount

    Still stumped: what would cause internal slaved ATA, external FW, RAM disk, and now interal CD not to mount???

    I also repaired permissions again, really just to see what would happen. No change, but here are the results, just in case it lends a clue:

    2003-10-13 13:10:43 -0700 - Repair of privileges has started
    We are using special permissions for the file or directory ./System/Library/Filesystems/hfs.fs/hfs.util. New permissions are 33261
    Permissions differ on ./System/Library/ServerSetup/Configured, should be drwxrwxr-x , they are drwxrwx---
    Owner and group corrected on ./System/Library/ServerSetup/Configured
    Permissions corrected on ./System/Library/ServerSetup/Configured
    Permissions differ on ./System/Library/ServerSetup/UnConfigured, should be drwxrwxr-x , they are drwxrwx---
    Owner and group corrected on ./System/Library/ServerSetup/UnConfigured
    Permissions corrected on ./System/Library/ServerSetup/UnConfigured
    User differs on ./private/var/db/locate.database, should be 0, owner is -2
    Permissions differ on ./private/var/db/locate.database, should be -rw-r--r-- , they are -r--r--r--
    Owner and group corrected on ./private/var/db/locate.database
    Permissions corrected on ./private/var/db/locate.database
    Group differs on ./private/var/run/utmp, should be 0, group is 1
    Owner and group corrected on ./private/var/run/utmp
    Permissions corrected on ./private/var/run/utmp
    User differs on ., should be 0, owner is 502
    Group differs on ., should be 80, group is 20
    Owner and group corrected on .
    Permissions corrected on .
    2003-10-13 13:15:24 -0700 - The privileges have been repaired on the selected volume.

    I have noticed that the permissions on the boot drive do not stick (in the Get Info box using the Finder). Again today - at least the third time since I began looking - the "Owner" was set to System (I had expected it would be set to the original Admin), and the "Group" was blank.

    Currently backing up everything to tape.

    Trying to decide if I should risk attempting upgrading to 10.2.8, as there is only so much I can really do in the terminal - even with remote access to bits of Jazzbo's brain (thanks!), but that could actaully make it worse. Everything seems to be working fine, as long as I log in as root...but it makes me very nervous not having actually solved the problem.

    If I upgrade, and things go badly, I can always reinstall from CD and upgrade back to 10.2.6 (.5?). I would have to reinstall anyway if I wanted to go back to 10.2.5, so not *that* big of risk. Have to think about it for a while....

    What about a virus, trojan, etc? Last I heard there are none for OS 10, but anything out there that for Unix that *might* hit an OS 10 box???

    __________________

    Charlie Don't Surf!

    [This message was edited by unclemac on Mon October 13, 2003 PT at 14:52.]

  10. #10
    Join Date
    Jun 2002
    Location
    Campbell, CA, USA
    Posts
    732

    Default

    Hiya, Uncle Mac,

    Yessir, the permissions on the /Volumes directory as you found them are correct and not the blocker.

    In the output of the repairing permissions, though:

    1. hfs.util

    We are using special permissions for the file or directory ./System/Library/Filesystems/hfs.fs/hfs.util. New permissions are 33261

    is ridiculous. '33261' as a filemode ("permissions") doesn't mean anything. Please run

    ls -ld /System/Library/Filesystems/hfs.fs/hfs.util

    and post the output back. Merely by its filename (an "HFS utility"??) one wonders if screwy permissions on it could be a blocker in the arena of discovering what HFS volumes are mounted (or mounting them anew).

    Permissions on mine look (appropriately):

    -rwxr-xr-x  1 root  wheel  43716 Oct  4 13:53 /System/Library/Filesystems/hfs.fs/hfs.util

    To match that (as root):

    chown root:wheel /System/Library/Filesystems/hfs.fs/hfs.util
    chmod 755/System/Library/Filesystems/hfs.fs/hfs.util
    ls -ld /System/Library/Filesystems/hfs.fs/hfs.util

    (the last step to check your work).

    2. The ServerSetup directories

    The "Configured" and "UnConfigured" directories complaints are

    should be drwxrwxr-x , they are drwxrwx---

    which means that no one other than the owner and users in whatever group those files have can access them at all, pre-repair and assuming the repairing program actually fixed them.

    I don't know what these directories are for. Run these two commands, please,

    ls -ld /System/Library/ServerSetup/Configured
    ls -ld /System/Library/ServerSetup/UnConfigured

    and verify that the permissions strings at the beginnings are drwxrwxr-x,

    3. locate.database

    User should be 0, is -2. User 0 is root; "-2" is the "nobody" user.

    I'm not sure what /var/db/locate.database is, but I guess it's used by the lookupd to cache NetInfo and DNS entries. Mine seems to run fine with permissions -r--r--r-- and owned by "nobody", and I doubt this file plays into your problem.

    4. /var/run/utmp

    Group should be 0, is 1. Well, group 0 (nidump group .) is "wheel" and group 1 is "daemon". Nothing serious here.

    5. /

    Yep, it's going after your root directory, and reporting it as . (dot).

    The owner is 502, group is 80; should be owned by 0, group 20.

    Well, uid number 502 is, by convention, the second assigned when you create accounts (nidump passwd . and look for the entry with 502 as field 3 to know which account has that uid number).

    Group 80 is 'admin' and group 20 is 'staff'.

    My guess is that ls -ld / will now report

    drwxrwxr-x  1 root  staff  1360 Oct  4 13:53 /

    This is/was most definitely not the problem or users wouldn't be able to login at all.


    Side note on those permissions for the root directory:

    If you run a stock SMTP server on these OS X machines (10.1 and 10.2) and have group-write enabled as per repairPermissions, /usr/sbin/sendmail (which is both the SMTP listener and the injector for new mail messages) will distrust its configuration directory (/etc/mail), complaining that "A directory on the path to sendmail.cf is group-writable". I've also seen one machine with a globally-writable root directory (drwxrwxrwx) and, needless to say, sendmail didn't like that one bit. Fix? chmod go-w / to turn off group and other write access to your root directory, and do that every time you "repair" (and thus break) permissions.

    Jazzbo

    [This message was edited by Jazzbo on Mon October 13, 2003 PT at 21:00.]

    [This message was edited by Jazzbo on Mon October 13, 2003 PT at 21:01.]

  11. #11
    Join Date
    Jan 2001
    Location
    Mobius Strip
    Posts
    13,045

    Default

    You guys are so over my head and into this, but I say this on

    MacOSXHints

    QUOTE:
    "When backing up my "Home" directory before upgrading to a new hard-drive, I was unaware of the various Unix permissions that had to be conserved, in order to do this successfully. When reinstalling this backup into my newly reinstalled OS X 10.2.8 system folder on my new hard-drive, I found that most of my files and many of my applications were unusable. I had copied the backed up files using the Root account, and apparently this had changed all the permissions such that the files were now owned by Root, not by me!

    A bit of frantic Unix research on a local Mac bulletin board followed (Revelation BBS, in Vancouver BC), where I found a tip contributed by Derek M. Warren, who came up with the following. This has (apparently) worked to restore full usability to my entire "Home" folder and files. In the Terminal app, type:

    % sudo su
    % chown -R myname /Users/myname

    The first line gives you root level access; the second line restores the correct ownership of the home folder. Replace myname with your actual short username, of course.

    This seemed to work okay (fingers crossed!)

    robg adds: Some things to keep in mind -- Carbon Copy Cloner will create backups with permissions intact, and you might also be able to recover from something like this by running Apple's Restore Permissions (in Disk Utility), though I'm not sure it looks at ownership of the Users folder.

    / END QUOTE

    [This message was edited by TZ on Tue October 14, 2003 PT at 10:11.]

  12. #12
    Join Date
    Feb 2001
    Location
    on the landline, Mr. Smith
    Posts
    7,787

    Default

    Over your head...

    Jeeze, howda think I feel?




    Thanks though for the info, just digging in on this today.

    Oh yeah, and an update from yesterday afternoon:

    While digging through in Workgroup Mangager, I noticed that two the files that are unique/visible to WM on server - the "VolumesSettingFolder", and the "Volumes" folder were set to a non-admin user as owner, and no Group! No way I did that, and not sure what they should be set to. I never messed with any stuff outside of the users I set up, and their stuff; these are OS files.

    Getting ready to install Server on another G4 just as a test so I can compare a fresh install to what I have going now...

    First I will get started on Jazz's instructions.
    __________________

    Charlie Don't Surf!

    [This message was edited by unclemac on Tue October 14, 2003 PT at 11:21.]

  13. #13
    Join Date
    Feb 2001
    Location
    on the landline, Mr. Smith
    Posts
    7,787

    Default

    Here we go J -

    #1

    [Central:~] root# ls -ld /System/Library/Filesystems/hfs.fs/hfs.util
    -rwxr-xr-x 1 root wheel 43716 Mar 18 2003 /System/Library/Filesystems/hfs.fs/hfs.util

    and then:

    [Central:~] root# chown root:wheel /System/Library/Filesystems/hfs.fs/hfs.util

    [Central:~] root# chmod 755/System/Library/Filesystems/hfs.fs/hfs.u

    [Central:~] root# chmod 755/System/Library/Filesystems/hfs.fs/hfs.util
    usage: chmod [-R [-H | -L | -P]] mode file ...

    [Central:~] root# ls -ld /System/Library/Filesystems/hfs.fs/hfs.uti

    [Central:~] root# ls -ld /System/Library/Filesystems/hfs.fs/hfs.util -rwxr-xr-x 1 root wheel 43716 Mar 18 2003 /System/Library/Filesystems/hfs.fs/hfs.util


    #2

    [Central:~] root# ls -ld /System/Library/ServerSetup/Configured drwxrwxr-x 3 root admin 102 Jan 17 2003 /System/Library/ServerSetup/Configured

    [Central:~] root# ls -ld /System/Library/ServerSetup/UnConfigured



    __________________

    Charlie Don't Surf!

    [This message was edited by unclemac on Tue October 14, 2003 PT at 14:32.]

  14. #14
    Join Date
    Feb 2001
    Location
    on the landline, Mr. Smith
    Posts
    7,787

    Default

    So here is current status...

    After performaning commands as per last post, no real change. Noticed this - perhaps a clue:

    I reboot, login as root, mystery volumes mount.

    I logout and login as admin, mystery volumes don't mount.

    I logout and login as root, mystery volumes don't mount.

    I reboot, and log in as root, mystery volumes mount.

    So....

    Something tied to startup procedure, that does not run with a login/logout. So when I login as admin, I kill acccess even for root, and only a reboot will restore... maybe a clue?

    Just finished installing 10.2.6 Server on a backup G4, going to see if I can compare some of the file permissions.

    __________________

    Charlie Don't Surf!

    [This message was edited by unclemac on Tue October 14, 2003 PT at 14:35.]

  15. #15
    Join Date
    Jan 2001
    Location
    Mobius Strip
    Posts
    13,045

    Default

    I KNOW I read a thread on bbs.xlr8yourmac.com about someone having these mystery volume problems. 3 months ago, maybe less.

    Looking for something in the "/Volumes" directory or a syblink or link to a volume that is no longer present????

  16. #16
    Join Date
    Jan 2001
    Location
    Mobius Strip
    Posts
    13,045

    Default

    http://www.macdevcenter.com/pub/a/ma...acforunix.html

    Great article. Top Ten Unix Tips.
    Terminal App and Unix link on left.

    There's always a need to pick up a few pointers. Or books.

  17. #17
    Join Date
    Jun 2002
    Location
    Campbell, CA, USA
    Posts
    732

    Default

    I've been thinking over this "no group whatsoever. Blank." and the "no admin group in the list" bits from your original post (and the more recent reference). Then, that clicked in with removing admin privs for a user. A brandy-new possibility!

    Just suppose that instead of removing "admin" privs for a user -- which would change the user's group affiliation away from group 80 (admin) to something else -- that the entry defining group 80 was deleted from the group tables.

    Belaboring the semi-conscious horse, the group number is what's stored on-disk to show file group affiliation. The group number is what's read from the passwd (accounts) table to see what a user's primary group is. The group number is cross-referenced through the group table to come up with its name (or the other way around, if you know the name and need to find out its number).

    If the group table from the NetInfo database no longer had an entry associating group number 80 with the name "admin", it wouldn't show up on selector lists.

    Try this:

    nidump group .

    and see if there's an entry for the admin group (field one) relating it to gid number 80 (field 3).

    There's a second group table, used only during the boot process until the lookupd is launched to serve the table from NetInfo. Do this:

    cat /etc/group

    and see if the entry for the admin group is present in this file.



    When you're doing the inspection and see "no group affilated with __fill_it_in__", how are you examining it? Command-I in Finder? Try this instead:

    ls -ld __drag_n_drop_the_thingy_from_Finder__

    and see if, in the "group" field (fourth, just after the owning username) there's a number instead of a group name. That'd put it on ice that the entry giving a name to that group-id number is missing from your NetInfo group table.



    If the admin group is missing from your NetInfo db, I think I can coach you through re-adding it via /Applications/Utilities/NetInfo Manager. It's even easier to get it back into the /etc/group file that's used prior to lookupd getting launched.

    Jazzbo

  18. #18
    Join Date
    Feb 2001
    Location
    on the landline, Mr. Smith
    Posts
    7,787

    Default

    Here ya go:

    "nidump group ." returns the following(matt = admin user):

    nobody:*:-2:
    nogroup:*:-1:
    wheel:*:0:matt
    daemon:*:1:root
    kmem:*:2:root
    sys:*:3:root
    tty:*:4:root
    operator:*:5:root
    mail:*:6:
    bin:*:7:
    staff:*:20:root(...and complete list of users...)
    guest:*:31:root
    utmp:*:45:
    uucp:*:66:
    dialer:*:68:
    network:*:69:
    www:*:70:
    admin:*:80:root,matt
    unknown:*:99:
    DisUsersDontTouch::-7:

    ---------------------------

    And "cat /etc/group" returns the following:

    nobody:*:-2:
    nogroup:*:-1:
    wheel:*:0:root
    daemon:*:1:root
    kmem:*:2:root
    sys:*:3:root
    tty:*:4:root
    operator:*:5:root
    mail:*:6:
    bin:*:7:
    staff:*:20:root
    smmsp:*:25:
    guest:*:31:root
    utmp:*:45:
    uucp:*:66:
    dialer:*:68:
    network:*:69:
    www:*:70:
    mysql:*:74:
    sshd:*:75:
    admin:*:80:root
    unknown:*:99:

    --------------------

    I edited out the user groups that I thought were not relavant - let me know if something is missing that might need to be verified...

    Question: Should "admin" in the second group (or any other user/group for that matter) also include the actual admin user (matt)?

    Thanks Jazz!

    [This message was edited by unclemac on Tue October 14, 2003 PT at 23:21.]

  19. #19
    Join Date
    Feb 2001
    Location
    on the landline, Mr. Smith
    Posts
    7,787

    Default

    OK. For the drag and drop trick, keep in mind it's the boot drive Server is running on, so I get this:

    ls -ld /
    drwxrwxr-x 37 root admin 1258 Oct 15 19:34 /


    Is that what you expected to see?



    Quote:

    "...and see if, in the "group" field (fourth, just after the owning username) there's a number instead of a group name."

    ...not sure where to look; lost me on this.



    And just because I was curious, here are the two mystery volumes, dragged and dropped:

    [Central:~] root# ls -ld /Volumes/IT\ Dept
    drwxrwxr-x 20 matt IT Group 680 Oct 13 15:20 /Volumes/IT Dept

    [Central:~] root# ls -ld /Volumes/Marketing\ Dept
    drwxrwxr-x 50 matt Marketin 1700 Oct 9 16:13 /Volumes/Marketing Dept

    [This message was edited by unclemac on Wed October 15, 2003 PT at 9:31.]

  20. #20
    Join Date
    Feb 2001
    Location
    on the landline, Mr. Smith
    Posts
    7,787

    Default

    Jazzbo's thoughts got me to thinking about NetInfo...

    So while looking around - no touchy! - I came across this, which looks odd, although I have no idea what it *should* be.

    When I click on /mounts, this is the detail in the lower half of the window:

    vfstype______url
    dir__________/Network/Servers
    name_________***not a UTF8 string***
    opts_________(net,url==afp://;AUTH=NO%20USER%20AUTHENT@192.168.100.5/ Public)


    Very strange.... What't that IP all about?

    The IP scheme fits our internal private block, but this box is on a 216 block, and *nothing* is on the IP listed, so no idea where that is coming from. Found out that "UTF8" has to do with text/font/language stuff, so perhaps not related...

    But, hello, what do we have here!?

    /users/matt had this info:

    home_loc_____'<home_dir><url>afp://192.168.100.5/Users/</url><path>matt</path></home_dir>'

    And all the other uses I have checked so far have the same.




    What the heck does that mean? And even if this is seriously screwed up, is it even part of the volume mounting issue?


    Thanks!

    [This message was edited by unclemac on Wed October 15, 2003 PT at 10:59.]

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •