quote:

I don't know what to say about your present permissions status. For all you know every Level 4 and 5 user at Apple Discussions has access to your machine when ever you are connected online now from all the Terminal advice you received there.

Don't think I haven't thought of that. Somebody armed with the info I've provided might have been able to hack in and superlock my hard drives, just to stick it to me for being thalo, who knows.

But I think I'm secure enough behind a hardware firewall and permissions. And I know enough unix (again, just enough to harm myself) to know what they were telling me to do. Changing ownership to ROOT is not going to open me up to attacks. If they had advised me to ignore ownership or set "everyone" to Read-Write, I would have been more suspicious.

Anyway, if it's this tough for me and the people I work with to get access to my files, WITH passwords, a vandal without passwords really has nothing to gain by trying to destroy my life. I don't care how much of a Mac Apologist they are.

The problems with Seabiscuit, remember, began with a boot drive crash. All Seabiscuit's drives were set up with sharing permissions based on that original server software install. When that drive failed, and I reinstalled, the job was to try and recreate on the system, all the share points and access to those volumes that were keyed to that first install.

In other words, when you login to the server via the Radiator, you have to give a user and password that Seabiscuit understands. When I gave my normal username and password after reinstalling OS X Server, despite the fact that it was IDENTICAL to my old one... I got squat. Couldn't connect. Also couldn't mount Radiator drives on Seabiscuit which I do from time to time as well. To get these two machines to share and play nice with each other, I did mess around with permissions without exactly knowing what I was doing. That was my sin. But whatever I did, eventually I was able to see the Seabiscuit drives on Radiator, and Radiator drives on Seabiscuit. At least from my normal admin login account.

And really all I did was look at the permissions in the Finder, and try to add my user to them, or make sure my user was an admin, or match the permissions of a drive I COULD access to drives I was having PROBLEMS sharing with. I think I only really pooched anything when I applied the permissions to contents... out of fear that while I could get in to the drive, I wasn't going to have Read-Write access to the FILES in them.

At this point, all I can think of to do is start over everywhere. A fresh server install on Seabiscuit, fresh boot drive install on Radiator. Try to begin again. Not touch any permission, ever. The only problem with that, is that it'll take me a whole weekend. And I've got work to do. So maybe this weekend, maybe next. Right now things are working, so might be leaving well enough alone for the time being.

Since the Safari update, I haven't crashed Safari. A good sign. Many of the crash reports I sent to Apple were from Safari. I also sent them logs, which Safari was filling up with unsafe javascript warnings.

I was hoping to buy a new Mac this month, but money is now starting to get tighter, so might have to postpone that again. But I think that's really the issue. I think I'll get better behavior on an 8-core Mac with a ton of RAM. I think throwing power at these problems is currently what Apple is doing to solve them. So why not me?

Share point access has little to nothing to do with Get Info permissions.

How did you set up the Server software? All your access should be set up through the Server Admin application. Share points Users. From your Client machine you can connect through the Go menu in the Finder. To connect the Server to the Client machine you have to turn on file sharing on the Client machine.

You can save the Server setup data to a file so in the future if the same thing happens you can just import the file and all the Server data is restored.

And there is no real difference between System files in Mac OS X and the Legacy in regards to moving preference files from one user to a new one to restore settings.

What I think happened to you is Nelson is controlling your machine through his Calendar application.

quote:

How did you set up the Server software?

Installed. Named the server identical to old name. Set it up as "standalone server." Set up an admin user and password identical to my old one. Set share points for all the drives in Seabiscuit. Enabled root account.

Went to try and connect from the Radiator using the "Go" menu. Nothing.

Groaned. Shook my head. Rolled my eyes. Read the manual. Began messing with permissions. The rest is history.

I'll have to figure out how to do that saving the Server setup data to a file, for next time.

Right now I'm just exhausted. And aside from one Quicktime crash today, I was able to get through today fairly crash free. But I am keeping an eye on the Console, and there are still a bunch of things that worry me. I'm getting this one a lot too:

3/21/08 8:01:11 PM com.apple.launchd[1] (org.postfix.master) Failed to count the number of files in "/var/spool/postfix/maildrop": No such file or directory

No idea. And still lots of Suitcase fusion log entries about "Break on _NSLockError() to debug."

Yeah, I'll bet this is all Nelson's fault. He boobytrapped Calendar 2.2 because he knows it would become my favorite app.

It sounds like you tried and or are logging into Seabiscuit as the System Administrator account of Seabiscuit. You do not use that account to log into the server from a client machine. The Server Admin app you need to set up a User that you will log in with from the Radiator. To keep it simple you could name the user what ever the User name and Password is for the Radiator.

The first console log has to do with your Time Machine restore. Here is a way for you to take full control of the log message.

The other console log also might deal with Time Machine maybe Fusions Vault isn't allowing Time Machine to back it up or something.

Thanks, actually I figured that one out myself. The console is looking for the directories, so I went to the terminal and put them there. What I didn't make was anything called "maildrop"... but the person in your link didn't do it either.

As for the other one, it doesn't look like Time Machine is involved there, it definitely seems to be Suitcase flipping out. And it does it ALL DAY whether Time Machine is backing up or not. Actually, it seems to go more nuts when I open Photoshop or InDesign or Illustrator... something that uses auto-activation.

Back to Seabiscuit for a minute. Actually I did TRY logging in to Seabiscuit as system admin from the Radiator, and THAT worked... I bet that's how the other admin user got in there, as a matter of fact. Where I was having trouble, was just logging in to the server with my Radiator thalo username. Which is an admin account, but not called "admin" like it is on the server.

On Seabiscuit you need to set up a User with the Server Admin software. You can set up a total of ten users. Once a user is set up you then give them access to what ever share points you want them to have access too. You can limit users down to a single folder if need be.

The Server file data backup is really simple. It is probably under the File menu titled something like export server file data backup. I am not sure of the exact particulars. I will have to check the office servers for the details.

I've definitely had some improvement since the Safari update. My application crashes have been reduced significantly. They still hit me once in a while, but it's nothing like it was.

Maybe I spoke too soon. Another round of GoLive crashes. The terrible kind. Sudden, frequent, and work-losing.

Did I mention too that the new interface of GoLive 9 is much tougher to work with? And there's CRAZY behavior working with tables. I mean sick. Things suddenly blasting apart, cells not cooperating... really terrible.