Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix for User not found error with Cronicle #3

Merged
merged 1 commit into from
Oct 17, 2019
Merged

fix for User not found error with Cronicle #3

merged 1 commit into from
Oct 17, 2019

Conversation

wangchaosjtu
Copy link

fixes "User does not exist" when the user is not a local user

@jhuckaby
Copy link
Owner

Thank you, but what bug is this fixing exactly? The output of the two commands for a non-existent user is exactly the same for me. This:

/usr/bin/getent passwd | grep nonexistentuser

And this:

/usr/bin/getent passwd nonexistentuser

Both output nothing, and the getpwnam() function returns null. Can you explain what this PR does?

@wangchaosjtu
Copy link
Author

wangchaosjtu commented Oct 17, 2019

Thank you for getting back to me, Our company uses active directory and sssd to manage the users, if a user is not set up locally, getent passwd will not list it, thus grep will not work. getent passwd user will fetch the info from the directory.

@jhuckaby
Copy link
Owner

Ah ha, I see what you mean. Got it, thanks! Merging!

@jhuckaby jhuckaby merged commit 61ef6cc into jhuckaby:master Oct 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants