Bug 8735 - Cause for NT_STATUS_NO_SUCH_USER should be reported more prominently
Summary: Cause for NT_STATUS_NO_SUCH_USER should be reported more prominently
Status: NEW
Alias: None
Product: Samba 3.6
Classification: Unclassified
Component: User & Group Accounts (show other bugs)
Version: 3.6.3
Hardware: All All
: P5 minor
Target Milestone: ---
Assignee: Jeremy Allison
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-01 11:19 UTC by Robert Dahlem
Modified: 2012-02-03 18:03 UTC (History)
1 user (show)

See Also:

Attachments
Raw patch for 3.6.x and master (733 bytes, patch)
2012-02-02 21:51 UTC, Jeremy Allison 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Dahlem 2012-02-01 11:19:47 UTC 
I made a mistake: on a share I configured "force user = xyz" but xyz wasn't in /etc/passwd (misspelling). The result is NT_STATUS_NO_SUCH_USER, which left me clueless in the first place.

I needed to up the log level to 5 to see
"Get_Pwnam_internals didn't find user [xyz]!"

I propose to report this more prominently (on a lower debug level) to make this kind of misconfiguration easier to solve.

Maybe this could be detected by testparm too.
Comment 1 Jeremy Allison 2012-02-02 21:51:44 UTC 
Created attachment 7288 [details]
Raw patch for 3.6.x and master

Would the attached fit the bill ?

Jeremy.
Comment 2 Robert Dahlem 2012-02-03 09:17:17 UTC 
(In reply to comment #1)

Crashes for missing groups.
I changed "*lp_force_group" to "lp_force_group", then it worked.

Thanks!
Comment 3 Jeremy Allison 2012-02-03 18:03:54 UTC 
Thanks - compiled, but not tested :-).

Jeremy.