Very Computer

I am having a weird Problem.

I made some changes to my smb.conf file.  I then restarted samba.  I had
problem logging in, so I ran the testparm program. Changes that I made
to the smb.conf  -such as changing security from user to domain and
encrypt passwords from no to yes.

I even tried rebooting -but to no avail.  What am  doing wrong for the
changes to to kick in?

Thanks

Mark Penkower

I am having a weird Problem.

I made some changes to my smb.conf file.  I then restarted samba.  I had

problem logging in, so I ran the testparm program. Changes that I made
to the smb.conf  -such as changing security from user to domain and
encrypt passwords from no to yes  - were not reflected in the dump.

I even tried rebooting -but to no avail.  What am  doing wrong for the
changes to to  not have kicked  in?

Thanks

Mark Penkower

Well, it looks as though you're updating a smb.conf file that Samba is not
using.  Find out which one it _is_ using and update that.
strings /usr/sbin/smbd | grep smb.conf
may get you what you want, but if not, then strings /usr/sbin/smbd | less
and carefully look through what comes from that.

Mark Post

Postmodern Consulting
Information Technology and Systems Management Consulting
To send me email, replace 'nospam' with 'home'.

On Mon, 19 Feb 2001 01:39:11 GMT, Mark Penkower staggered into the Black
Sun and said:

Quote:>I made some changes to my smb.conf file.  I then restarted samba.  I had
>problem logging in, so I ran the testparm program. Changes that I made
>to the smb.conf  -such as changing security from user to domain and
>encrypt passwords from no to yes.

[these changes were not made when Samba was restarted, as your other
post said]

Quote:>I even tried rebooting -but to no avail.  What am  doing wrong for the
>changes to to kick in?

Where does your Samba keep its config file?  The default config file is
specified at compile time; default is /usr/local/samba/lib/smb.conf ,
but RedHat compiles theirs to use /etc/samba/smb.conf and SuSE compiles
theirs to use /etc/smb.conf .  Make sure you're editing the right file;
run a "locate smb.conf" to make sure there aren't multiple files in
places you didn't expect them.  Also make sure that you saved your
changes to the file.  Or specify the file to use on the command line,
like "smbd -D -s /somewhere/smb.conf".  The way to get Samba to re-read
its config file is to do a "killall -HUP smbd nmbd" and this approach
works with most daemons.

--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /  Workin' in a code mine, hittin' Ctrl-Alt
http://www.brainbench.com     /   Workin' in a code mine, whoops!
-----------------------------/    I hit a seg fault....

My old Red Hat 6.0 and my new Red Hat 6.2.3 (both are really VA
Linux Systems' version of Red Hat) both keep smb.conf right on top
in /etc. I.e., the file in question is /etc/smb.conf . That also
seems to be where swat (man swat) expects to find it.

Quote:> and SuSE compiles
> theirs to use /etc/smb.conf .  Make sure you're editing the right file;
> run a "locate smb.conf" to make sure there aren't multiple files in
> places you didn't expect them.  Also make sure that you saved your
> changes to the file.  Or specify the file to use on the command line,
> like "smbd -D -s /somewhere/smb.conf".  The way to get Samba to re-read
> its config file is to do a "killall -HUP smbd nmbd" and this approach
> works with most daemons.

> --
> Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
> Brainbench MVP for Linux Admin /  Workin' in a code mine, hittin' Ctrl-Alt
> http://www.brainbench.com     /   Workin' in a code mine, whoops!
> -----------------------------/    I hit a seg fault....

--
 .~.  Jean-David Beyer           Registered Linux User 85642.
 /V\                             Registered Machine    73926.
/( )\ Shrewsbury, New Jersey
^^-^^ 7:35am up 21 days, 16:02, 4 users, load average: 1.91, 1.97,
2.03

Quote:> I am having a weird Problem.

> I made some changes to my smb.conf file.  I then restarted samba.  I had
> problem logging in, so I ran the testparm program. Changes that I made
> to the smb.conf  -such as changing security from user to domain and
> encrypt passwords from no to yes.

security = domain requiers you to have an M$ pdc controller...