[KLUG Members] Re: Quick samba q
Adam Bultman
members@kalamazoolinux.org
Sat, 2 Feb 2002 14:43:56 -0500 (EST)
Check this out: Same configuration: Reboot into stock kernel, and samba
works. So, I recompile MY kernel (2.4.16) again, and add more. Doesn't
work. Recompile again, adding just about everything I would ever need. No
dice. Get linux-2.4.17 from another box, compile it like I do normally,
and it worksl ike a gem. I gues it's just one of those idiosyncrasies of
linux.
adam
On 2 Feb 2002, Bryan J. Smith wrote:
> On Fri, 2002-02-01 at 19:04, Adam Bultman wrote:
> > Upgraded to samba 2.2.2-10. Still the same issue, even with
> > a new conf file. Added the interfaces command, still nothing.
> > REmoved the interfaces command, still nothing. Same problems,
>
> Just removing the line uses the defaults. If the default is "yes" then
> you still have a problem. Try putting "bind interfaces only = no" and
> see if it works (don't forget to restart Samba after you do). It could
> be something with 100 different parameters.
>
> Either way, I don't think its a big deal.
>
> > and I think I'm going to give up with this one.
>
> Well, it's your choice. Oplocks are just a performance consideration
> (at the cost of data integrity). I usually turn them off on shares
> where a lot of writing is occurring to Access databases, but its good
> for read-only shares for executables and databases.
>
> > Might be time for a reinstall anyway.
>
> Re-installing Linux does NOT do a damn thing. It's not Windows.
> Everything that has to do with Samba configuration is in that smb.conf
> file. If you re-install nothing will change.
>
> A better alternative would be to delete the smb.conf, and then pull up
> SWAT which will write a brand new one, from the defaults.
>
> -- Bryan
>
>
--
Adam Bultman
adamb@glaven.org