[Samba] Samba configuration issues
Joel at HammersHome.com
Thu Apr 18 16:43:02 GMT 2002
If it wasn't Redhat's, no chance it will install your startup scripts
This starts up my smbd and nmbd on my caldera 2.4 box just fine.
case "$1" in
kill -SIGHUP `cat /usr/local/samba/var/locks/smbd.pid`
kill -SIGHUP `cat /usr/local/samba/var/locks/nmbd.pid`
echo start stop reload
You just don't need anything fancy to start these daemons. Put this script
anywhere you want, just as long as it runs after networking is up.
Also be aware that if you mix and match different ways to install samba
(rpm's from Redhat, other places, and source), you may wind up with
different versions of samba scattered around your system with configuration
files, lock files, log files, and God knows what else in different locations. THIS IS BAD.
The two simplest approaches are:
1. Always use Redhat's rpm's.
2. Remove all samba rpm's and install from source from samba.org. If you do
the latter, ALL (as far as I can tell) your files will be in /usr/local/samba, which makes
administration of samba a bit easier.
On Thu, Apr 18, 2002 at 03:59:25PM -0500, Allen Crawford wrote:
> The first question I have is how come when installing from an RPM it doesn't
> set Samba to run at startup automatically? I read some documentation
> somewhere that said it should. But it didn't on either version for me.
More information about the samba