anders_02
asked on
samba shares take long time to refresh
Im using samba 2.0 on my linux server. when i'm adding or deleting a share in the smb.conf file and then save it, it takes a long time for my win98 machine to get that info.
if i delete a share it will be available for 10 more minutes before it disappear....is it supposed to be like that or do i have to change some settings?
if i delete a share it will be available for 10 more minutes before it disappear....is it supposed to be like that or do i have to change some settings?
....i'm using the slackware distribution...
i'm loading samba via inetd and i tried to restart inetd but that didn't help...
i'm loading samba via inetd and i tried to restart inetd but that didn't help...
When you say "if i delete a share it will be available for 10 more minutes before it disappear", do you mean you see it through browsing the network from a 98 machine after you've restarted inetd?
If so, I doubt you can actually access it (even you you may see it in the browse list). Try to doubleclick on the share and you'll probably get an error.
For a possible explanation, see http://www.microsoft.com/win32dev/netwrk/browse1.htm (particularly the section titled "Browser Failures with Microsoft Networking).
If so, I doubt you can actually access it (even you you may see it in the browse list). Try to doubleclick on the share and you'll probably get an error.
For a possible explanation, see http://www.microsoft.com/win32dev/netwrk/browse1.htm (particularly the section titled "Browser Failures with Microsoft Networking).
ASKER
well, it's true...
i can access the deleted share for a couple of minutes, even after i've restarted inetd...(and killed the old one)
maybe i can shut down samba in another way? (i can still access the shares after killing inetd, so i guess smaba is never shut down, just restarted...)
i can access the deleted share for a couple of minutes, even after i've restarted inetd...(and killed the old one)
maybe i can shut down samba in another way? (i can still access the shares after killing inetd, so i guess smaba is never shut down, just restarted...)
use this string of commands to shut down any trace of samba after you make an smb.conf change:
killall -HUP smbd
killall -HUP nmbd
killall -HUP `cat /var/run/inetd.pid`
Then try to re-access the server. See what happens.
killall -HUP smbd
killall -HUP nmbd
killall -HUP `cat /var/run/inetd.pid`
Then try to re-access the server. See what happens.
ASKER
yep, it's working!
thanx for helping!
just propose an answer and you'll get your points
thanx for helping!
just propose an answer and you'll get your points
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
As root:
In redhat /etc/rc.d/init.d/smb restart
Otherwise:
killall -HUP smbd
killall -HUP nmbd