Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Server share points, ownership, and Get Info' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Server share points, ownership, and Get Info
Authored by: lee1 on Aug 18, '03 03:27:41PM
I'm unclear as to why this is a hint, exactly. This is the expected behavior. If you log in to a remote machine as another user, anything you create or touch on that machine will not be owned by the user you're logged into your local machine as.

It seems to me that was exactly his point; more specifically, that the Finder fails to recognize the correct ownership and permissions. Perhaps you need to read the hint more slowly.

Personally, I avoid mounting remote volumes, because the Finder is so bad at dealing with them. The only times I've had to reboot recently were when I made the mistake of trying to use personal file sharing; if there is a lack of response of the server or anything about the mounted volume that the Finder doesn't like, I get the eternal beachball, and the locked-up Finder quickly brings down the entire GUI. There is no force-quitting or Finder-relaunching available. This is in 10.2.4.



[ Reply to This | # ]
It'll time out
Authored by: spudly on Aug 18, '03 04:46:30PM

This will time out after 2 minutes and you'll get your Mac back without rebooting. An annoyance held over from a bygone era i know but hopefully will change in 10.3...



[ Reply to This | # ]
It'll time out
Authored by: Ganymede on Aug 18, '03 11:17:38PM
2 minutes? Excuse me, more often than not OSX never comes back. Despite the grandiose claims of stability, herein lies the nether region where OSX is, for me at least, not only a crashing bore but an unbearable waste of time - I've resorted to holding down the power button until it reboots more than on all my other Macs combined (I started with a 128K, when you were just a gleam in -oops, don't go there).

I'll agree it's unfortunate to run classic apps (old, perhaps geriatric?) while using a VPN tunnel to aging PC networks in order to talk to far away VAXes, especially as I'm neither networking expert nor unix guru (and my employer's tech support staff won't/don't/can't support home workers on Macs). But the relentless, eternal beachball is unforgivable. I know that success must lie just beyond the pane of this looking glass! Yet I've been unable to make VPC or VNC work - even on my local Mac network.

Is there an OSX time-out setting I can adjust somewhere, so I can avoid permanent deep-space?


Ganymede

[ Reply to This | # ]
It'll time out
Authored by: stevanreese on Aug 19, '03 08:58:26AM

The 2 minute time out is per connection. 2 lost connections 4 minutes...



[ Reply to This | # ]
It'll time out
Authored by: lee1 on Aug 19, '03 04:14:57PM

Some else who needs to read more slowly....

I did mention that the hung Finder starts taking out the rest of the GUI, and that force-quitting doesn't work. In light of this, what magic do you think is going to happen after my two minutes are up?



[ Reply to This | # ]
It'll time out
Authored by: n9yty on Aug 19, '03 05:10:49PM

Two minutes on crack.....


Well, two minutes is not the answer. As others have said... I have exactly ONE connection I mount on my laptop at work. If I forget to unmount it before I leave for the day (from a MacOS X Server 10.2) and I go home and wake up the computer, I'm hosed.

I let it sit for over two hours one day with the spinning beachball... No luck at all.

The only thing I've found to be of any help at all is if you first notice the problem in an app other than Finder (when they try to write to disk is when the problem hits), and you still can switch your network connection over to where the server is, SOMETIMES it will reconnect and continue normally. However, when I go home, this is never an option, and so a reboot is the only fix.

This is the only remaining type of "crash" or "freeze" I encounter on MacOS X, at least with the work I do.



[ Reply to This | # ]