Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
In this case ORPHAN has nothing to do with processes!!!
I am also getting this weird error, however I checked passwd/shadow files and those users don't exist anymore. I also deleted their entries in /var/spool/cron/<user>. Any other ideas how to get rid of these?
This thread is really old but is in top5 of google hits so...
This will occur if there's a file in the /var/spool/cron directory
that doesn't match up to a username and UID. So if you find /var/spool/cron/bob --you must be able to 'id bob' I found this as a result of creating a backup file for root /var/spool/cron/root.20100324 (today's date). Since there is no UID for user "root.20100324' then it's considered ORPHAN.
Make sense? Here's the code --this conditional has probably not changed for years...
if (strcmp(fname, "*system*") && !(pw = getpwnam(uname))) {
/* file doesn't have a user in passwd file.
*/
log_it(fname, getpid(), "ORPHAN", "no passwd entry");
goto next_crontab;
}
The other dead giveaway is when you do an ls in the dir and it shows a uid instead of a username. ls automatically grabs the username from /etc/passwd (or wherever eg ldap) if it exists.
On our centos systems, we had to restart nscd, restart cron, (in that order). Cron needs needs it's own entry to check it's self to see if it's
lost contact with the ldap server.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.