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

Error message for wrong or non specified user in /etc/crontab (RHBZ#1374264) #68

Closed
hhorak opened this issue Oct 26, 2020 · 1 comment
Closed

Comments

@hhorak
Copy link

hhorak commented Oct 26, 2020

This was initially reported as https://bugzilla.redhat.com/show_bug.cgi?id=1374264

Description of problem:

Error message "ERROR (getpwnam() failed)" when no user specified for jobs in /etc/crontab is not
so helpful at the first.
Maybe it will be more nice to have something like "no/wrong user-name specified for this job", or similar.

Steps to Reproduce:
Put some job in /etc/crontab without "user-name"

*/1 * * * * echo "bla" > /tmp/bla

Actual results:

Error message : Error message "ERROR (getpwnam() failed)

Expected results:

Error message : no/wrong user-name specified for this job

--- Additional comment from Tomas Mraz on 2016-09-08 12:56:43 UTC ---

You've actually specified an user - user 'echo'.

And the user name is part of the message - see the 'echo' here:
Sep 8 14:53:01 vespa crond[1023]: (echo) ERROR (getpwnam() failed)

The reason why the getpwnam() failed can be various, it can be also that remote user identity server does not answer to queries.

So the message could be:
getpwnam() failed - user unknown or user identity resolution failure

--- Additional comment from Stefan Dordevic on 2016-09-08 13:13:33 UTC ---

(In reply to Tomas Mraz from comment #2)

You've actually specified an user - user 'echo'.

And the user name is part of the message - see the 'echo' here:
Sep 8 14:53:01 vespa crond[1023]: (echo) ERROR (getpwnam() failed)

Yes, exactly.

The reason why the getpwnam() failed can be various, it can be also that
remote user identity server does not answer to queries.

So the message could be:
getpwnam() failed - user unknown or user identity resolution failure

It makes sense to me.

@t8m
Copy link
Member

t8m commented Oct 26, 2020

This is already fixed. The current message is getpwnam() failed - user unknown. See b836b57

@t8m t8m closed this as completed Oct 26, 2020
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

No branches or pull requests

2 participants