What is inflating folder size on Leopard Server?

I have one folder in a 10.5.8 server that shows a size of 46GB. Inside are 6 1GB files and nothing else, visible or invisible.
The disk passes fsck -fy, so it isn't a directory problem. Thoughts and fixes?

Where is the folder located, and have you used Terminal to check out the actual contents of the folder (hidden files, etc.)??
-Doug

Similar Messages

Mail folder size

Hi,
I am moving from Outlook to apple mail. one of my outlook mail folders hat around 4GB. Whats the max folder size in Apple Mail?
Thank youi for your answer,
best regards
Robert

Ok, I've been working a little on the problem at hand.
If I use the "Rebuild" command on the mailbox, I get duplicates of all message.
I decided then to use the script found on www.homepage.mac.com/aamann/ (great tool btw) to remove duplicate message. The script take a little time for the 800 so messages but finds all the duplicates and moves them to a "duplicate" mailbox from where you can trash them. Trash, empty trash in Mail, quit Mail, relauch Mail...
The mbox folder now contains the right number of message, but the size is still bigger than expected. Digging in, the mbox folder contains two folder (Message + Attachments) as opposed to only one (Message) in Leopard. By observation, it is clear that the attachments (found embedded in the message file in the Message folder) can also be found in the the Attachments folder... therefore the reason for the apparent doubling size of the "Mail" folder!
Ok, now there is some sort of solution (rebuild, duplicate removal) but that doesn't sort out the fact that attachments are found in two places, thus eating up twice the disk space.
Still need help!
Bisondesprairies

Leopard Server and Blackberry

Hi All, We are considering migrating from Exchange to Leopard Server for our small business mail/calendar/file sharing/wiki needs.
But, we have a requirement to be able to support the blackberry for mail/calendar. What are our options for interfacing Leopard Server's mail & calendar with our blackberry users? Currently we use a hosted Exchange provider that delivers this service.
Thanks in advance!

Apple needs to address the issue of incorporating mobile devices into a small business environment. Leopard Server provides many innovative, valuable and useful features for small businesses, but it is analogous to a top-of-the-line car in which the seat position and radio stations all reset each time you get out. It's great while you're in the car, but the process of leaving and coming back is a big pain.
Apple has not put forth any suggested solution for wirelessly syncing calendars, let alone contacts, to mobile devices. All current solutions require client-based synchronization, involve many different vendors, and provides too many opportunities for failure and lack of support. For example, one could do this:
Spanning Sync on desktops/laptops to sync iCal with Google Calendar
GooSync to sync Google Calendar with Palm Treos
Google Sync to sync Google Calendar with BlackBerry devices
Google Calendar would be used merely to sync iCal with mobile devices wirelessly
We need a solution that is based around Leopard Server at the center. In other words:
Mobile devices sync calendar and contacts directly with Leopard Server
Desktops/laptops sync calendar and contacts directly with Leopard Server
There are plenty of other features that need implementation or refinement (e.g., simpler and more rubust sharing of contacts, better webmail interface), but wireless synchronization tops the list.

I've got Snow Leopard Server, but don't need the server functions. What to do?

This is somewhat complicated, so please bear with me. My Mac Pro was running OS X 10.5 and required updating. But we have legacy Power PC apps (mainly FreeHand) that we want to continue using, even though Mountain Lion doesn't support them.
As a solution, I'm going to run Snow Leopard Server in emulation on Parallels 8 Desktop. I would rather have used plain old Snow Leopard instead of the server version, but Apple's EULA only allows 10.6 Server to run in emulation.
So, I got Snow Leopard Server and have used it to upgrade 10.5. Eventually, (once I get everything working properly), I'll upgrade that to Mountain Lion and use SL Server in Parallels emulation to run the old Mac apps we can't do without.
But I've run into a problem I didn't anticipate: I don't have a clue about running a server.
I'm having trouble setting it up so the other Mac user in my department can access a shared folder. Also, I want the login window to display the list of users, but that option is grayed out.
What I'd like to do is strip out all the server functions and just run as if 10.6.8 was a standard version of Snow Leopard, which I'm familiar with. If that's not practical, please explain how to get sharing to work since that's the main problem.
I've tried turning off the services listed in the Server Preferences (iCal, Mail, etc.) but that hasn't fixed the problems. I think there may be server functions running that I haven't found preventing me from fixing the problems. Or it could be something else entirely (as I said, no clue).

DON'T MAKE A MOUNTAIN (lion?) OUT OF A MOLEHILL!
Several points in response to your post, in chronological order, not necessarily in order of importance:
• It was a common Urban Myth that Snow Leopard (client's) EULA prohibited its virtualization in Lion or Mt. Lion on a Mac! That myth has been largely debunked in the last 18 months.
Here are detailed instructions on how to install Snow Leopard client into Parallels 7 or 8:
http://forums.macrumors.com/showthread.php?t=1365439
That being said, and being the author of the aforementioned thread, I STRONGLY recommend that, where possible, you use Snow Leopard Server in favor of Snow Leopard client. This will side step some later corruption problems that can arise from the improper use and shutting down of this Parallels partition.
Historically, this thread was written when Apple sold Snow Leopard Server for $499+ or ceased sales altogether. Now, Apple has rendered the (now diminishing) debate over the EULA moot, by its recent release of Snow Leopard Server to the US & Canadian community for $20; leaving those who cannot purchase SLS (or get someone to purchase it for them) to continue to follow the instructions in my thread (or asking me to purchase SLS for them and forward it to them; my preferred course of action!).
• I ALWAYS recommend that data files be stored on the real Mac's HDs and NOT in a virtualized world. This is easy to accomplish and establishes a backup regimine (Time Machine, etc.) that will protect the users data. Lost applications are easily restored from their installer discs.
• In practice I find that using SLS in Parallels 8 is the same as using SL client in Parallels. I have even removed the Server apps from the Dock so as to not be confused by them.
So, your solution is to establish a "shared folder" on the hard drive of the Mac that is hosting Parallels. When in SLS in Parallels you will have access to your shared folder, ironically through Parallels' "Shared Folders" feature that is now present in Mac OS Guest installs on version 8 (see the "Shared Folders" SERVER on the right side of the screenshot, below).
When using Freehand MX or other PowerPC apps, save your data files into your shared folder through access to it by Parallels' Shared Folders. Other users on your network will have access to the SAME data files, through their customary use of file sharing to access your shared folder from your Mac's hard drive.
IGNORE the Server applications in the Applications folder...
Freehand MX running in Snow Leopard Server installed into Parallels 8 for use in Lion or Mt. Lion:
[click on image to enlarge]
Postscript: your post was so easy to follow!

Discoveries while trying to setup Leopard Server - Help! What am I doing ??

I have documented 2 scenarios and i would like some help with proper build procedures. Until today I have been using the host record I asked my ISP who also hosts Pri/Sec for my company domain to setup. It wasn't until this morning that I realized that they didn't setup a PTR record so because of that I did a RDNS lookup on my static IP and today I programmed that into the host/domain fields thru my build so that there was proper RDNS for the setup. Which looks like this rrcs-0-0-0-0.central.biz.us.rr.com zero's being an actual static IP.
Scenario 1- Install Leopard onto MacMini with Standard install and use Apple Airport extreme for NAT firewall/router. Ok so I have done this about 4-6 times to try and get this right.
A. Install Leopard and let OS auto config Airport-N for port mapping.
B. Airport WAN is static IP from ISP and LAN is 10.0.1.1, Mini LAN is 10.0.1.2 Airport is DHCP provider on LAN.
C. Mini hostname is set to rrcs-0-0-0-0 and domain is set to central.biz.us.rr.com
D. After the system was rebooted after install I immediately got an error because the server prefs told me it could not find server rrcs-0-0-0-0.central.biz.us.rr.com which was weird because it is a brand new build. but since I setup the computer name to be mac-srvr I was able to remove the FQDN and input mac-srvr.local and then I could sign in. ---- I think this happened because when I am trying to log into the server prefs it's going out and performing a lookup and returning an error because from inside the FQDN reverse is actually the WAN interface of the Airport and not the LAN of the mini even though I told the mini to be the FQDN. Hope that makes sense and someone can tell me if I am right and then how to fix it .
E. When I connected the MacBook and setup a user on the LAN side and then immediately disconnected from LAN and performed Dialup to the internet I was able to use the VPN for the first time which is great but but but the ichat would not work as I kept getting certificate errors and the ical from what I remember was good.
So major issues here in this scenario is that internally the server is setup as rrcs-0-0-0-0.central.biz.us.rr.com and services don't seem to be able to find that computer. And second ichat does not accept the default certificate and or cannot connect to the ichat server.
Scenario 2 - Install Leopard onto MacPro with Standard install nic0-wan with static ip 0.0.0.0 and nic1-lan with static of 192.168.1.1
A. Install Leopard and set hostname=rrcs-0-0-0-0 and domain=central.biz.us.rr.com with computer name of mac-srvr.
B. Upon server reboot and the second interface is not giving out IP's, I found that the range was from 192.168.1.2-254 and the default search domain was example.com because I Ieft that field blank during install and so I had to stop DHCP and setup someting like company.office and restart and all is was good.
C. Once Macbook was on LAN and services setup properly I then disconnected and I was not able to VPN into the network like on the macmini unless I opened up the server admin and went the vpn console and then enabled pptp with another range. I could then PPTP vpn but not L2TP which should have worked out of the setup. But when I do PPTP I cannot gain access to server resources via smb://192.168.1.1 which is what the server automatically creates when you run server gateway assistant.
D. The ichat and or L2TP VPN does not work unless I actually go into the Server Admin and disable it which I have another posting in VPN/Networking support about this for a 3rd build showing the same issues.
So major issues here are that services such as ichat, L2TP does not work unless I disable firewall, PPTP does work but does not pass traffic onto the LAN or I can't log into the server shares.
So if anyone has any insight, I am about 20 rebuilds in trying to get just one working properly over the past 3 days. And if anyone has a step by step that would be even better lol. I have all the Apple Server Docs as I attended a training seminar recently so I am well versed in the generic documentation but there is nothing in the server admin or any other apple doc that states this is what you need and how to do it as far as setup goes with setting up your Leopard server if you don't have external DNS and or if you just want to have a fake dns setup like fakeserver.fakedomain.office as we do with SBS. So any help would be good.

Found that if I clean up DNS for my domain with PTR and A then everything started working properly after a rebuild.

Leopard Server - Web User folder - Access forbidden

Hi,
we migrated our users from a Tiger server to a Leopard yesterday. Now all of them have 'access forbidden' errors on their web.server.com/~username folders.
There are read-only permissions on their sites folder and we can access the default server home page.
I have seen the posts for deskop 10.5.4 stuff for personal web sharing but that doesn't apply here.
Any ideas?

I should say that the _www user/group is a system user/group, and therefore its hidden from the typical list of users and groups. I don't have a Leopard server in front of me, but there is a way to view system users and groups in the list. Hopefully your engineer knows it off the top of his head.

Snow leopard server for net boot and software updates only what needs to be running to use it?

Snow leopard server for net boot and software updates only what needs to be running to have it work right?

Netboot and Software Update, at its simplest. Mac OS X Server also expects to have functional IP networking and DNS services (somewhere) on the LAN (and if you're behind a NAT gateway, then the DNS server(s) are on your LAN and not out at your ISP), or things get weird. SUS (usually) works out of the box, outside of cases where there's an outbound firewall. Netboot can be more effort to setup, in terms of what you're loading into the clients.

What is the migration path to Lion Server from Mac Mini Snow Leopard Server

I've currently got a mac mini server happily serving wikis/blogs... what is the update path to Lion Server?

excellent resource! thanks!
my mac mini server got stuck after lion install but before running server set up...
I had to reset the PRAM (http://support.apple.com/kb/ht1379) before I could get control of the server back.

What is the correct way to teach leopard server mail about junk mail?

All my clients are using apple mail and they basically taught their own client each their own way of filter junk mail. This works ok...but after upgrading to Leopard Server I think the server can be trained with junk mail data too? If so, anyone know how to set it up? I only see options to mark mail as junk mail on the server side, nothing about training.

I have done it on a mac os 10.4 server, it works great. Have a look here
http://osx.topicdesk.com/content/view/37/58/
regards

What client-style apps can you run on Leopard Server?

I have a small network and therefore want my Leopard server to also support a small number of OSX applications: iTunes (including iTunes sharing), DVD Player, Safari, Mail, etc. to allow me to use it as an occasional workstation for small tasks.
Is this possible? I assume Leopard Server has all the underpinnings of Leopard, but it's not clear on the Apple web site.
Other than risking server stability, are there any other issues with doing this?
Thanks.

I would agree with the assessment that Tiger Server is roughly as stable as Tiger Client where running 'client' applications (I would refer to them as GUI-based apps run from the console). I can't comment on the stability of Leopard Server in the same regard; haven't had it out of the box long enough yet.
You have to ask yourself how much stuff you really want to run on the server; if it's a business-critical server that you can't afford much downtime on, then installing a lot of applications will start to work against you. In addition to eating up processor and memory resources that could be used by Mail, Web service, etc., GUI-based apps may make your server somewhat more crash-prone.

Leopard Server 10.5.4 + SMB + Windows XP Clients

Hello!
I got quite some interesting problems with my Xserv under Leopard Server 10.5.4 with Windows XP Clients.
The server runs as an open directory master and a standalone server for smb.
Shares are setup for AFP and SMB clients, ACLs are set up with read+write access for the user's group. So far everything works, users can connect from their Macs (OS X 10.3.x - 10.5.4) without problems.
My problem are the windows clients.
Connecting works fine, and apart from one permission bug (more on that later) they can access all files and do everything the macs can do.
Problem 1:
Users cannot rename files if they don't have write permission at the POSIX-level as either owner or group on the enclosing folder. ACLs do not matter at this point, if the user connects through SMB he cannot rename files or folders.
No big problem, I just put all users into one group and set this group as the POSIX-group and do a chmod -R g+w on all shares.
Inheritate this settings for SMB-connections works.
But not for AFP-connections. Every new folder a mac-client creates comes with permissions 755. So I changed UMasks on the clients to 002, and at least folders created by the finder now have the right permissions of 775.
Folders created by "new folder" on most applications load/save dialogs still come as 755 which screws up renaming for windows-clients.
Folders created when expanding a zip-file also behave this way.
The only solution I found for this was to make a cronjob that does a chmod -R g+w on the shares. Not that great.
Another "fun" feature with POSIX-permissions and SMB:
Files inside a folder. Files+Folder have an ACL set up that specifically denies deleting files+folders for a user. This users group has POSIX-permissions with write access to the enclosing folder. Window's explorer will let that user delete files and folders without any complaint about missing permissions to do so. They even disappear from the explorer-window, but are not actually deleted.
If you refresh the view, the files+folders are there again.
If the user instead has no POSIX-permission that grants him write-access, but an ACL that grants him delete, explorer happily deletes the files the user wishes to. And these files actually get deleted.
If the user has no write POSIX-permission and no ACL-permission to delete files, explorer complains about missing rights to delete files/folders.
I tried adding "acl check permissions = no" to smb.conf, but that didn't change this behaviour.
Problem 2:
Sometimes, when copying "large" files to a server share with windows explorer (from 50 MB upto 3 GB), the user immidiately gets an error message: "Cannot copy. The specified network name is no longer available."
The copied file shows up at once in the destination directory and has the correct file size, but only contains "garbage". Half a second later the same copy works and the file is actually copied successfully.
Sometimes this error shows up while a large file is copied and if you browse through other shared folders while the copy takes place.
Most often it will show up when you copy&paste with explorer.
I am stomped and have no idea where to search for a solution to this one.
I tried changing ethernet cables (premade and selfmade), the network switch, ethernet port of the Xserv ... connected a workstation directly to the Xserv - no change.
DNS works, all clients+Xserv have static IPs and the same settings for DNS-Server. Name resolution works, as does reverse resolution.
I even tried using a windows server 2003 as a WINS-Server without success for this problem.
There are no event log entries on the clients when this happens, and smbd.log on the server shows
read failure for 4 bytes to client 192.168.1.137. Error Connection reset by peer
I used wireshark to monitor what exactly happens when this shows up, but it just happens out of nowhere ... the clients just sends a TCP_RST. No unusual things before or after the TCP_RST.
I ran some tests with samba 3.0.32 and samba 3.2.x under linux 2.6.x - no such errors at all.
I tried installing Leopard Server on my Mac Pro, same behaviour.
I ran some batch-scripts that would copy large and small files in excess from/to the server from 4 different windows xp clients for a whole weekend 24 hours - not a single error. As soon as I use windows explorer to copy a file this error has a chance of showing itself.
Problem 3, more of an application bug:
Adobe InDesign CS2 (Windows again ;)) cannot export a PDF to a shared folder if the filename is longer than 8 characters. It starts exporting and after reaching 100% it just stops with the error "PDF cannot be exported." If the filename is shorter than 8 characters, all works fine. Exporting locally or to other samba servers (linux) or windows servers (2003) works fine. Copying this files to the share works, too.
Exporting any other filetype from IDCS2 (eps, inx, jpeg ...) works regardless of filename length. So does saving InDesign-files.
InDesign CS1 and CS3 do not show this, so I guess it's safe to assume this one is Adobe's problem
Did anyone experience similar problems or even better has a solution to some of these?
The real showstopper is problem #2, at least for us.
Thanks in advance and excuse my poor english skills!

I tried several new approaches, but nothing worked so far.
The update to 10.5.5 made things worse. Connections are dropping all over the place, when saving from Adobe programs in particular.
Printing from clients to a Xerox Phaser 5500 works, but choosing a different paper size than the default chosen in the cups admin interface goes all wrong and either prints on the default paper size, but down/upscaled to the chosen paper size or prints on the chosen paper size and down/upscaled as if you were printing to the default paper size. (e.g. default paper size is A4, you choose A3 with an A3 document. Document prints on A4 and is downscaled to A4, or prints on A3 and is downscaled to A4.)
There is no way I can keep this thing in production much longer. I tried reinstalling again, but that did not change any behaviour. Another nice "feature": InDesign disables "edit original" when the path to the linked file contains any directoryname with more than 8 characters in length.
Coupled with a sometimes disappearing "dirserv" (it just stops working until I reboot the whole computer) the decision stands to move away from the Xserve.
Leopard Server 10.5.x just does not seem to work well with windows clients.
We will migrate to a windows server 2003 running ExtremZ-IP for the macintosh clients this weekend. Too bad that Apple does not allow Bootcamp to work on Xserves, at least the hardware would have been useful then.
(As a nice finishing touch, the harddisk partition where all data resides did become corrupt over the weekend. "The volume Daten could not be repaired."
Disk Utility and first aid did show nothing on friday ... saturday after no work being done on the partition this error shows up. The only solution I could find was to reformat the partition and restore from a previous backup. Another weekend down the drain. Sorry for the rant, but 6 weekends in a row is enough.)

Wiped my entire macbook drive and now snow leopard won't install over snow leopard server, HELP!

I ordered, what I thought, was Snow Leopard a while ago because I was running Leopard and I wanted to get the app store so I could move onto Lion and then Mountain Lion. I ordered the disc over the phone and the woman sent me the Snow Leopard Server instead of just Snow Leopard, I didn't think much about it so I clean installed it and ran it on my unibody macbook for a while. I didn't see much use for the disc anymore seeing that everything was downloadable at this point, so I sold the disc on Ebay and carried on. The server edition started to slow my computer down due to all of its excess applications and what not, and I read online that Lion and Mountain Lion are also very slow on the old unibody Macbooks so I ordered a regular Snow Leopard disc, now available online, and tried to install it. My computer said Snow Leopard cannot be installed over Snow Leopard server so I went to disc utitlity and wiped my entire drive while the OS X Snow Leopard disc was running and trying to install. I went back to the install window and it still said OS X Snow leopard cannot be installed over Snow Leopard Server so I shut down my computer and tried to turn it back on and I all I got was a blinking folder with a question mark in it, what do I do????????
P.S. All of my content is backed up on an external harddrive so I am all good with that.

Drive Preparation
1. Boot from your OS X Installer Disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu.
2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, click on the Partition tab in the DU main window.
3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.
4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
5. Set the format type to Mac OS Extended (Journaled.) Click on the Security button, check the button for Zero Data and click on OK to return to the Erase window.
6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
7. After formatting has finished quit DU and return to the installer. Complete the Snow Leopard installation.

Is it possible to limit the folder size of the Shared folder?

I have setup quotas for all users who login to our Snow Leopard Server.
I would now like to setup the Shared folder that is located in the Users folder to have a maximum data limit. That way, a user can't just dump data into the Shared folder and completely fill the server.
Does anyone know if that's possible or if there is a better way to create a shared folder that is has a data limit?
Thanks!
Kurt

Thank you Linc Davis for your reply!
I have studied the information in that tutorial. It seems that it is discussing how to setup quotas for individual users and groups on a given volume. However, what I'm trying to accomplish is setting the limit on a specific folder.
OS 10.6 Server already has a feature that I have enabled that sets quotas for each of my user's Home folder. However, each of them ALSO have access to a shared folder on the server that is not within their own Home folder. Thus, the individual quotas do restrict the specific size of this Shared folder.
So I'm wondering if you (or anyone) knows of a way to set a limit, not on a specific user or group, but on a specific folder? I need to figure out how to enable a setting that basically says: "This shared folder cannot grow bigger than 20GB no matter who uses it," for example.
Thanks!!

Can't rename folders on Snow Leopard Server

I have 10.6.8 Snow Leopard Server running on a new Mac Mini server. Attached I have a Pegasus Raid storing all my files. I have a sharepoint set up for every project we work on but a couple act strangely. Users can create and delete folders but can not rename them once created. In order to rename they must drag the folder onto the desktop, rename and then replace the folder on the server. All permissions are set up identical to the other sharepoints which work fine. I have had a couple so-called "experts" look at the permissions in both the terminal and Server Admin. Everyone seems stumped. Any ideas?

Thanks for the input but I finally soved the problem. Here is what I found...
Although I had given users/group the ALLOW/FULL CONTROL premission with a sharepoint, I discovered that in Server Admin if you double-click on the User or Group name under the ACL permissions that a drop down box appears. This box allows you to fine tune the ACL but it appears that by default all of the boxes are not checked even though I granted the user Full Control. After checking all of the boxes I was able to create and rename folders in my share as expected.
This also had an similar effect if I denied Full Control. Some of the boxes remained unchecked and it left holes in my system where denied users could still access some files. Again by checking all boxes these holes were closed.
Does anyone know how to change the default so that all boxes are checked when assigning the Full Control permission?

Moving accounts from Snow Leopard Macs to Mac mini with Snow Leopard Server

I got my brand spanking new Mac mini today with Snow Leopard Server! So far, we (at home) were managing our accounts on individual iMacs and a MacBook Pro. While I will be getting into the innards of account migration, management etc. I thought I'd post a quick question here; Currently I have an iMac with three user accounts on it (wife and two kids). I also have my own personal MacBook Pro with my account (the only Admin account) on it. We'll soon be getting another iMac for our daughter (who currently has an account on the existing iMac). My idea in getting the Mac mini was to move to and centrally manage all the user accounts in the household on the Mac mini server. What is the best way to accomplish this? What is the best way to move the existing accounts on to the server?
Additionally, I'll be looking into connecting the two stationary iMacs with Powerline Ethernet (where one runs Ethernet over existing electrical wires in the walls). My other option would be to rely on wireless network (I don't think this would be a good idea for if I am going to be placing the user accounts on the server and there needs to be a constant on, reliable connection between the server and the client computers as they will be talking to each other a lot!). Any thoughts on Powerline? (I am not looking forward to installing Ethernet cabling behind walls :o))
What say the wise men of Mactopia?!
Thanks,
Kenneth.
P.S. I had earlier accidentally posted this in the corresponding section of Mac OS X instead of the Mac OS X Server forum.

Ok so the esiest way to explain this is to tell you what i just went through.
I have 3 user accounts. All the accounts are network Users meaning that there home folder are kept on the server. I was having a problem with Time Machine giving me error 41 and error 11. After scratching my head for 2 days I ended up copying (Drag-n-Drop) the Home Folders to an External Hard Drive. I then proceeded to erase both of the internal hard drives on the mac mini and did a fresh local install of the Server OS.
Everything was fine at that point. Now this is where Snow Leopard stopped being nice.
I went and Created the user account again using WGM. I let WGW create the home folder and the 9 folder inside. I made sure the short names were the same and the passwords were the same as they were previously.
However, once i Copied files from the external drive to the home folders the permissions copied as well, Which i guess should be expected. So now at this point apparently the UID's of the newly created users wasn't the same as they were before the clean install. I have multiple instances of root listed in the ACL for several folders and also had several instances of System listed sporadically.
Now, This isn't to say that you can't drag n drop because now That I have it all squared away and everything is now working ok, I would probably still drag n drop the home folder off to an external disk, but only because I now know what to do to clean things up.
if you drag and drop be sure to use the CHOWN command and theCHMOD commands afterwards. Take a look at this MacFixIt article: http://reviews.cnet.com/8301-13727_7-20013630-263.html?tag=mncol;title
If you copy your local imac users to the home directory on the server you may want to follow the steps on the URL I gave plus you will most likely also have to do the following. In a nutshell you are going to use the chmod command to strip all the ACL Permissions then you are going to use the chown command to re-specify the correct owner and the correct permissions for the network user.
!) Go into ServerAdmin and click on Sharing
2) Go to the users folder you are using and select the user you are going to work with.
3) Click on the Permissions option
4) click on the +sign at the bottom (this will open the users & groups list to the right)
5) Drag the current user from the users list to the owner permissions line under posix section
5a) Click Save
6) Click on the Gear button at the bottom
7) Check the box for Owner Name and Owner Permissions.
8) Uncheck the box for Access Control List then click ok
Once you've gone through that rigmarole you can go back into ServerAdmin and fix the permissions for public and Sites folder which should only take a minute or so.
So the moral of this story and as I found out when i ended up calling Enterprise support is that the act of dragging and dropping user home directories from one server to another, or as in your case, from a local machine to a the server isn't anything that apple recommends or supports. you might want to read through the man pages for "Ditto" or so apple tells me, but honestly now that you know, the steps above aren't all that bad. It's true Knowing IS half the battle!
have Fun!
P.S. FWIW If you run into problems and have to call Enterprise Support be prepared for them to tell you to refer to the user Guides. So reading those would be to your advantage even though they aren't the easiest things to understand unlike apple's consumer products user guides

What is inflating folder size on Leopard Server?

Similar Messages

Maybe you are looking for