|
|
Removal of hostconfig file will prevent OS X booting
Samba does not delete or replace the /etc/hostconfig file. The SMBSERVER in the /etc/hostconfig flag may be changed by the Sharing preference panel. If you enabled samba via the sharing pref panel and your /etc/hostconfig file was lost, then you should definitely report this as a bug to Apple. If you edited /etc/hostconfig yourself, then you probably screwed something up or your editor had a bug.
Removal of hostconfig file will prevent OS X booting
Just to clarify...
Hint's fine...
I think the hint and related comments make a good archive and discussion, and I see no need to replace what you sent in. I did, however, add some emphasized text around the "third party" bit in the original hint...it seemed clear to me when I read it, but apparently it's not as clear as I thought it was!
Removal of hostconfig file will prevent OS X booting
No, it was identifiably the 3rd party software, not samba, which hosed the /etc/hostconfig file. The samba software itself never reads the contents of /etc/hostconfig. Instead the value of SMBSERVER is parsed from /etc/hostconfig at boot by the startup script /System/Library/StartupItems/Samba/Samba. The point is that one shouldn't blame samba for this--let the developer of the 3rd party implementation know about it--but it's simply wrong to start blaming widely used, stable product (SAMBA) when it isn't the fault.
While we're on the samba topic...
Does anyone know if Apple fixed the finder-hang when servers (like samba, ftp, etc) suddenly disappear due to dropped or changed network connection? While I've put off upgrading to 10.2.4, this problem continues to ruin my day on a regular basis, and if 10.2.4 fixes it, that alone will make the download worth the time.
While we're on the samba topic...
This is still a problem in 10.2.4.
While we're on the samba topic...
Yes and no. The Finder will hand, but after 2-3 minutes, it will time out and show you an error message. You just have to wait. Now, the question is, how do you change the timeout period to something more reasonable, like 45 seconds. Or better yet, don't tie up the Finder with just the reconnect task. DUH, it's a multi-threaded, multi-tasking OS. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:HintsNo new hintsComments last 2 daysLinks 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 |
|