[Samba] Samba configuration issues (solved)

[Allen Crawford]

All the installations I performed were RPMs from Red Hat, or more likely, a
Red Hat mirror site.  The first one I tried, 2.2.3a was definitely from Red
Hat.

Thanks for the info.  I'll probably just leave my daemons running from
/etc/rc.local then since that runs last.

As for my problem, I figured it out this evening when I got home.  I was on
the right track.  Step one was fixing my smb.conf file to have the smb file
parameter point to /etc/samba/smbpasswd instead of the /usr/bin/smbpasswd
program.  I confused myself on that one.  The second step was running
"smbadduser allen:allen" to add my UNIX:NT account into the smbpasswd
encrypted password file.  I once again had to change my /usr/bin/smbpasswd
file permissions, but after doing that and generating the user ID,
everything is working great.

Thanks for your help,
Allen

----- Original Message -----
From: "Joel Hammer" <Joel at HammersHome.com>
To: "Allen Crawford" <AllenC at mailcode.com>; <samba at lists.samba.org>
Sent: Thursday, April 18, 2002 6:41 PM
Subject: Re: [Samba] Samba configuration issues


> Whose rpm?
> If it wasn't Redhat's, no chance it will install your startup scripts
> properly.
> This starts up my smbd and nmbd on my caldera 2.4 box just fine.
>
> #!/bin/bash
> case "$1" in
>  start)
>   killall smbd
>   killall nmbd
> /usr/local/samba/bin/smbd -D
> /usr/local/samba/bin/nmbd -D
>   ;;
>
>  stop)
>   killall smbd
>   killall nmbd
>  ;;
>  reload)
>  kill -SIGHUP `cat /usr/local/samba/var/locks/smbd.pid`
>  kill -SIGHUP `cat /usr/local/samba/var/locks/nmbd.pid`
>  ;;
>  *)
>  echo Usage:
>  echo start stop reload
>  ;;
> esac
> exit 0
>
> 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.
>
> Joel
>
>
> 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.
>