Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

(Samba) smbpasswd problem

  • 16-01-2003 4:38pm
    #1
    Lemming
    Registered Users, Registered Users 2 Posts: 14,149 ✭✭✭✭


    Hey guys,

    I seem to have a problem with smbpasswd. I'm logged in as root, not su'd in, and trying to run the following command:


    [LinuxBox]$->smbpasswd -a userX


    smbpasswd then goes through the motions of prompting me for a password, and then to retype this password.

    Then i get the following output:

    startsmbfilepwent_internal: unable to open file /usr/bin/smbpasswd. Error was Text file busy
    Cannot open file /usr/bin/smbpasswd. Error was Text file busy
    Failed to modify password entry for user userX

    Any ideas or thoughts?? I'm not very well versed in the arts of samba.


Comments

  • #2
    Draco
    Subscribers Posts: 1,911 ✭✭✭Draco


    Is there something else that has accessed the smbpasswd file and not freed it up?


  • #3
    Lemming
    Registered Users, Registered Users 2 Posts: 14,149 ✭✭✭✭Lemming


    I suspect it could be squid.

    I did the following command:
    [box]$-> ps -ef |grep "smb"

    and came up with several processes with squid trying on the smb_auth with another (all the same) machine.

    But the machine in question had iptables crap enabled since I was messign about learning how to use it and probably failed to authenticate and kept trying. That's possibly what caused the problem.

    BUT ....

    I rebooted the server (machine I'm trying to get samba working on) so the resources should have been released, no? :confused:


  • #4
    Jaden
    Registered Users, Registered Users 2 Posts: 2,393 ✭✭✭Jaden


    Why would Squid go anywhere near smbpasswd? I can't think of a reason, unless you are authing proxy requests, and I've never see that done.


  • #5
    dahamsta
    Banned (with Prison Access) Posts: 16,659 ✭✭✭✭dahamsta


    Have a look at these threads Lemming:

    http://lists.samba.org/pipermail/samba/2002-September/079674.html
    http://lists.samba.org/pipermail/samba/2002-April/071125.html

    adam


  • #6
    Lemming
    Registered Users, Registered Users 2 Posts: 14,149 ✭✭✭✭Lemming


    cheers Dahamsta. That did the trick nicely.

    The problem was rather subtle.

    Whomever had tried to configure the samba service before me had mistaken the /usr/bin/smbpasswd binary for the password file of the same name and set the smb.conf file to this location.

    Thus the binary was trying to write to itself. So I just changed the smbpasswd password file location in smb.conf and everything is now hunkydorey.


  • Advertisement
Advertisement