samba - Feb 2008 - Making Samba change the Unix Password (/etc/shadow)

Hello all,

I am trying to change the linux login password through the smbpasswd
command by placing following  parameters in smb.conf file:

unix password sync = Yes
passwd program = /usr/bin/passwd %u
passwd chat = "*enter old password*" %o\\n "*Enter NEW
password*"
%n\\n "*reenter New passwd*" %n\\n "*password changed*"

But its not changing the unix password.

Where I am going wrong?

-- 
Thanks and Regards,
PARAG . A . KALRA

Good judgment comes from experience, and experience comes from bad judgment

http://discoverlinux.blogspot.com
Debian Linux! A Dawn of New Era!

Hi Rubin,

I made the changes suggested by you but still its not working.

--
Parag Kalra

On Feb 5, 2008 3:29 AM, Rubin Bennett <rbennett@thatitguy.com> wrote:
>
> On Tue, 2008-02-05 at 02:26 +0530, Parag Kalra wrote:
> > Hello all,
> >
> > I am trying to change the linux login password through the smbpasswd
> > command by placing following  parameters in smb.conf file:
> >
> > unix password sync = Yes
> > passwd program = /usr/bin/passwd %u
> > passwd chat = "*enter old password*" %o\\n "*Enter NEW
password*"
> > %n\\n "*reenter New passwd*" %n\\n "*password
changed*"
> >
> testparm is your friend :)  It should complain about the passwd command,
> and for good reason; it shouldn't be there.  Use:
> pam password change = yes
> instead, and get rid of the passwd program and passwd chat lines.
>
> HTH,
> Rubin
>
> > But its not changing the unix password.
> >
> > Where I am going wrong?
> >
> > --
> > Thanks and Regards,
> > PARAG . A . KALRA
> >
> > Good judgment comes from experience, and experience comes from bad
> judgment
> >
> > http://discoverlinux.blogspot.com
> > Debian Linux! A Dawn of New Era!
> --
> Rubin Bennett
> RB Technologies
> http://thatitguy.com
> rbennett@thatitguy.com
> (802)223-4448
>
> "They that can give up essential liberty to obtain a little
> temporary security deserve neither liberty nor safety"
>  --Benjamin Franklin, Historical Review of Pennsylvania, 1759
>
>
>

-- 
Love,
PARAG . A . KALRA

Good judgment comes from experience, and experience comes from bad judgment

http://discoverlinux.blogspot.com
Debian Linux! A Dawn of New Era!

Did you restart samba (/etc/init.d/smb restart)?

You need to at least do a reload (/etc/init.d/smb reload) for config
file changes to be read.

Rubin

On Tue, 2008-02-05 at 08:09 +0900, Michael Heydon wrote:
> Parag Kalra wrote:
> > Hi Rubin,
> >
> > I made the changes suggested by you but still its not working.
> >
> > --
> > Parag Kalra
> >
> > On Feb 5, 2008 3:29 AM, Rubin Bennett <rbennett@thatitguy.com>
wrote:
> >
> >   
> >> On Tue, 2008-02-05 at 02:26 +0530, Parag Kalra wrote:
> >>     
> >>> Hello all,
> >>>
> >>> I am trying to change the linux login password through the
smbpasswd
> >>> command by placing following  parameters in smb.conf file:
> >>>
> >>> unix password sync = Yes
> >>> passwd program = /usr/bin/passwd %u
> >>> passwd chat = "*enter old password*" %o\\n
"*Enter NEW password*"
> >>> %n\\n "*reenter New passwd*" %n\\n "*password
changed*"
> >>>
> >>>       
> >> testparm is your friend :)  It should complain about the passwd
command,
> >> and for good reason; it shouldn't be there.  Use:
> >> pam password change = yes
> >> instead, and get rid of the passwd program and passwd chat lines.
> >>
> >>     
> PAM is far from universal, there are plenty of OSes and distros that do 
> not include PAM. The man page doesn't say anything about passwd program
> being depreciated, why would testparm complain about it?
> 
> Are you getting anything in the logs when trying to reset the password? 
> Have you tried enabling passwd chat debug (you may have to up your log 
> level as well)? If you want to keep using passwd instead of PAM, could 
> you write a wrapper/replacement for passwd that logs everything that 
> happens?
> >> HTH,
> >> Rubin
> >>
> >>     
> >   
> 
> *Michael Heydon - IT Administrator *
> michaelh@jaswin.com.au <mailto:michaelh@jaswin.com.au>
-- 
Rubin Bennett
RB Technologies
http://thatitguy.com
rbennett@thatitguy.com
(802)223-4448

"They that can give up essential liberty to obtain a little
temporary security deserve neither liberty nor safety"
  --Benjamin Franklin, Historical Review of Pennsylvania, 1759

> Several posters have said that the Realtek 8168 and 8169 chips have caused 
> slow file transfers with Samba.  They solved their problem by changing to 
> another NIC.
Well, it's worth trying. I'll schedule the mainteinance with my client
and
let you guys know. Any restrictions with D-Link DGE-530T?

Thanks,

Giovani
>
> Dale
>
> Giovani Moda - MR Inform?tica wrote:
>> Hello list.
>>
>> I'm new here, and I'm joining because I'm having a problem
wich I can't
>> figure out the solution myself. Here's what's happening:
>>
>> A Samba 3.0.24 is serving files to seven Windows XP clients. Three of 
>> those clients run an application with a BDE database. The problem is
that
>> when running this application on Samba, it gets very, VERY slow,
causing
>> it to hang. I have noticed also an unusual low speed when receiving
files
>> from the samba server over network. When sending files to the server,
the
>> speed is OK. Since the databases used by that apllication have about
50Mb
>> each, the problem must be caused by that slow speed on receiving files 
>> from the server.
>>
>> I've twiked the configuration a bit, and came to this results:
>>
>> socket options = SO_RCVBUF=65535 SO_SNDBUF=65535 TCP_NODELAY 
>> IPTOS_LOWDELAY - Very slow on reading, fast when writing
>> socket options = TCP_NODELAY IPTOS_LOWDELAY - still slow on read, but a
>> little better. Fast when writing
>> socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=32768 -
significant
>> improvement when reading files, but the application still hangs due to 
>> the slow speed. Fast when reading.
>> socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=32768 
>> SO_RCVBUF=32768 - same as above, but writing speed shows deterioration.
>>
>> Other significant parameters:
>>
>>   max connections = 50
>>   dos filetimes = yes
>>   max open files = 4000
>>   nt acl support = yes
>>   preserve case = yes
>>   strict locking = no
>>   deadtime = 15
>>   unix charset = iso8859-1
>>   display charset = cp850
>>   oplocks = no
>>   kernel oplocks = no
>>   level2 oplocks = no
>>  local master = yes
>>   os level = 64
>>   domain master = yes
>>   time server = yes
>>   preferred master = yes
>>   domain logons = yes
>>   name resolve order = wins bcast host lmhosts
>>   wins support = yes
>>   wins proxy = yes
>>   dns proxy = no
>>
>>
>> So, I went for socket options = TCP_NODELAY IPTOS_LOWDELAY 
>> SO_SNDBUF=32768 and got these results:
>>
>> Copying a 45678592 bytes throug samba, it takes from 45 to 60 seconds
to
>> transfer. The same file though FTP takes only 3.9 seconds. I know FTP
is
>> the fastest protocol and cannot be compared to samba, but still,
that's a
>> HUGE difference.
>>
>> As a desperate measure, I've copied the whole database to a XP
machine,
>> shared the folder to the network, mapped it to the other stations, and 
>> the application runs perfectly again.
>>
>> Conclusion: there's definitely a problem when reading files from
samba
>> server. It's not network related, since FTP is really fast, and
when
>> serving the database from XP, the speed is OK too. The server is a
brand
>> new Core 2 Duo E4500, 2GB RAM, 160 GB HD SATAII, NIC Realtek r8169 
>> connected to a DES-1008D Gigabit Switch. The distro in question is FC5 
>> fully updated.
>>
>> As a related topic, I've came across a situation (two times and
couting)
>> when writing files to the samba server is painfully slow. On both
cases,
>> setting SO_RCVBUF=1 has resolved the problem. I don't know why, but
it
>> did. Both times, the server was connected to a D-Link DES-1024 switch. 
>> Switching NIC's and cables had no effect, but SO_RCVBUF=1 solved it
>> instantly. Could it be related tho this version of samba and the
problem
>> I'm having now?
>>
>> Any thoughts?
>>
>> Thanks,
>>
>> Giovani Moda
>>
>