[Bug 304] New: samba has issues with current pam.d I think....
bugzilla-daemon <[email protected]>
| Newsgroups | gmane.linux.arklinux.bugs |
|---|---|
| Message-ID | <[email protected]> |
https://bugzilla.arklinux.org/bugzilla/show_bug.cgi?id=304
Summary: samba has issues with current pam.d I think....
Product: Ark Linux
Version: Dockyard
Platform: i586 (PC, Intel)
OS/Version: All
Status: NEW
Severity: High
Affects: Overall Usability
Component: samba
AssignedTo: [email protected]
ReportedBy: [email protected]
QAContact: [email protected]
Description of Problem:
I'll let this console output speak for itself:
[root@uriel root]# smbadduser greeneg
Adding: greeneg to /etc/samba/smbpasswd
do_file_lock: failed to lock file.
startsmbfilepwent_internal: unable to lock file /etc/samba/smbpasswd. Error
was Interrupted system call
Unable to open passdb database.
do_file_lock: failed to lock file.
startsmbfilepwent_internal: unable to lock file /etc/samba/smbpasswd. Error
was Interrupted system call
add_smbfilepwd_entry: unable to open file.
Failed to add entry for user greeneg.
Failed to modify password entry for user greeneg
----------------------------------------------------------
ENTER password for greeneg
New SMB password:
Retype new SMB password:
do_file_lock: failed to lock file.
startsmbfilepwent_internal: unable to lock file /etc/samba/smbpasswd. Error
was Interrupted system call
Unable to open passdb database.
Failed to find entry for user greeneg.
Failed to modify password entry for user greeneg
Version-Release number of selected component (if applicable):
samba-3.0.2a-1ark
How Reproducible:
Every time.
Steps to Reproduce:
1. try adding a user for samba via either webmin or console.
2. watch as it blows up successfully.
Expected Results:
One should be able to add a user to /etc/samba/smbpasswd without having it
fail.
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
You are the QA contact for the bug, or are watching the QA contact.