Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hey, my first post! To start, thanks for all the great info I've found on this site. I installed Slackware on an old laptop a few months ago, my first time using Linux, and I'm hooked! I've learned more in 2 months fiddling with Linux than years on Windows. I love it. My wife doesn't see me as much anymore though.
So, obviously I'm completely new, and I have a problem. I recently upgraded Samba from 3.0.7 to 3.0.9 and an error immediately crept up. First, samba refused to start at boot and a manual start produced this:
ERROR: Could not determine network interfaces, you must use a interfaces config line
I updated my smb.conf file with interfaces = eth0 192.168.2.16. That allowed samba to start but I still get "WARNING: no network interfaces found" in the log and when I use smbclient. It chews a few seconds and eventually I can access my shares Ok, also my fstab entry mounts Ok too, but I always get this warning in the log.
Everything worked fine before the upgrade. Any ideas what I broke?
My [global] smb.conf file:
workgroup = THECOMPLEX
server string = Samba Server
security = user
hosts allow = 192.168.2. 127.
load printers = yes
log file = /var/log/samba.%m
max log size = 300
socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
interfaces = eth0 192.168.2.16
By default Samba listens on of all the network interfaces on the systems, including the "loopback" interface (called lo) which has the IP address 127.0.0.1.
It sounds like Samba is unable to automatically figure out what network interfaces are on the system. So three thoughts:
a) Are you using DHCP on an interface ? (a modem or ADSL connection is also a network interface).
b) Double-check the configuration of the network interfaces for other anomalies.
c) Are you compiling Samba from source ? (if so try the Samba lists).
Not a Slackware user, so I can't help with configuring interfaces the Slackware way.
Thanks for the reply hob. I think I must have installed my Samba Package incorrectly. I've reversed course and gone back to my previous version until I can figure out what I did.
First thing I'd check is to verify that both versions use
the same installation directories for all files, and that all
files had been replaced, including config-files.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.