Bug 146964 - crond ORPHAN (no passwd entry) on NIS+ system
Summary: crond ORPHAN (no passwd entry) on NIS+ system
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: crontabs (Show other bugs)
(Show other bugs)
Version: 3.0
Hardware: ia32e Linux
Target Milestone: ---
Assignee: Jason Vas Dias
QA Contact: Brock Organ
Depends On:
Blocks: 170445
TreeView+ depends on / blocked
Reported: 2005-02-03 01:11 UTC by Paul Pluzhnikov
Modified: 2007-11-30 22:07 UTC (History)
1 user (show)

Fixed In Version: vixie-cron-4.1-3_EL3
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-02-04 15:49:45 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Paul Pluzhnikov 2005-02-03 01:11:09 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3)

Description of problem:
On a system configured to use NIS+, I can login (as user devtest) and
do 'crontab -e' to set up a cron job.

Crond however refuses to run this job:

Feb  2 16:40:07 dev1 crontab[24872]: (devtest) BEGIN EDIT (devtest) 
Feb  2 16:40:19 dev1 crontab[24872]: (devtest) REPLACE (devtest) 
Feb  2 16:40:19 dev1 crontab[24872]: (devtest) END EDIT (devtest) 
Feb  2 16:41:00 dev1 crond[1371]: (devtest) ORPHAN (no passwd entry) 

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Set up the system with NIS
2. Login as user without local /etc/passwd entry
3. Use 'crontab -e' to set a cron job
4. Observe that the job does not run

Actual Results:  crond does not run scheduled jobs.

Expected Results:  crond should run jobs for users for which
getpwnam() returns a valid entry.

Additional info:

Comment 1 Jason Vas Dias 2005-02-03 15:12:26 UTC
This problem is fixed in the latest version of CRON for RHEL-3,
vixie-cron-4.1-3_EL3, which is currently undergoing QA testing
and which should be in RHEL-3-U5 . Meanwhile, you can download
it from:
Please try this version - it should fix the problem - and let me know.

Comment 2 Paul Pluzhnikov 2005-02-03 17:53:30 UTC
Yes, the vixie-cron-4.1-3_EL3 package fixes this.

Comment 3 Jason Vas Dias 2005-10-14 15:37:25 UTC
This bug is fixed with vixie-cron-4.1-8_EL3, available from:
and should be considered for inclusion in RHEL-3-U7 .

Note You need to log in before you can comment on or make changes to this bug.