|
|
Server share points, ownership, and Get Info
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 <i>another user,</i> anything you create or touch on that machine will <i>not</i> be owned by the user you're logged into your local machine as.
Server share points, ownership, and Get Info
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.
It'll time out
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...
It'll time out
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
It'll time out
The 2 minute time out is per connection. 2 lost connections 4 minutes...
It'll time out
Some else who needs to read more slowly....
It'll time out
Two minutes on crack.....
Server share points, ownership, and Get Info
> In a small environment, the databases can be maintained manually quite easily. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|