Bug 151141 - Problems running user cronjobs in a networking environment
Summary: Problems running user cronjobs in a networking environment
Status: RESOLVED FIXED
: 151098 160260 (view as bug list)
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: Other (show other bugs)
Version: Beta 7
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: Beta 8
Assignee: Mads Martin Joergensen
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-15 11:47 UTC by Christian Andretzky
Modified: 2006-03-23 09:06 UTC (History)
4 users (show)

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
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 Christian Andretzky 2006-02-15 11:47:06 UTC 
I could see that user cronjobs (stored in /var/spoll/cron/tabs/'username') are not executed after a restart of the machine if the user is defined not local.
The reason seems to be that cron - if started - checks if the user cronjobs are legal. But at this time the networking environment is not running and the user could not be validated and the cron job is never executed.

Restarting cron after the network (and the network based authentication) is up solves the problem.
Comment 1 Michael Gross 2006-02-15 12:25:06 UTC 
Werner: At least for the current release (if this still is the case), the order of the boot scripts should be changed accordingly. I'm setting this to 10.1.
Comment 2 Michael Gross 2006-02-15 13:16:22 UTC 
*** Bug 151098 has been marked as a duplicate of this bug. ***
Comment 3 Hendrik Vogelsang 2006-02-17 13:41:51 UTC 
Thorst anything against adding Should-Start $network into cron? afaics cron only runs in runlevels where $network is there also
Comment 4 Dr. Werner Fink 2006-02-23 11:29:53 UTC 
insserv oinly execute the dependcy orders it does not set them.
IMHO someone should add `$network' to Should-Start of /etc/init.d/cron.
Comment 5 Hendrik Vogelsang 2006-02-28 16:55:47 UTC 
submitted for next beta
Comment 6 Andreas Schwab 2006-03-11 13:56:21 UTC 
Still does not work in beta7.  Cron needs to start after ypbind or any other directory service.
Comment 7 Andreas Schwab 2006-03-11 14:18:49 UTC 
You shouldn't mix Should-Start with X-UnitedLinux-Should-Start, or the latter will be ignored.
Comment 8 Michael Gross 2006-03-23 09:06:37 UTC 
*** Bug 160260 has been marked as a duplicate of this bug. ***