Difference between revisions of "Talk:Crond"

From WebOS Internals
Jump to: navigation, search
(Alternate event.d config)
Line 20: Line 20:
 
I could only get crond to run on startup with these parameters in mod-crond...
 
I could only get crond to run on startup with these parameters in mod-crond...
  
start on stopped finish
+
start on stopped finish<br>
 
stop on runlevel [!2]
 
stop on runlevel [!2]
  
 
--[[User:Xorg|Xorg]] 18:57, 16 December 2009 (UTC)
 
--[[User:Xorg|Xorg]] 18:57, 16 December 2009 (UTC)

Revision as of 11:57, 16 December 2009

Is /opt/bin/crontab -e the original cron file that we should not be editing? If so does the package install of of cron need to be updated?

Keep these things in mind when running the cron daemon that ships with the Pre.


  • The daemon reads files in /etc/cron/crontabs/
  • crontab -e edits files in /var/spool/cron/crontabs/
  • When crontab -e does an edit, it makes a temporary copy of the file, which is what the user actually edits, verifies the changes, and then replaces the existing file.
  • Changes should be made using a regular editor to /etc/cron/crontabs/*

WebOS 1.3.1

I can not seem to get crond running after updating to WebOS 1.3.1. Any able to get it working? I'll keep working at it later and report back if I discover something... --Dolio 12:09, 25 November 2009 (UTC)

Alternate event.d config

I could only get crond to run on startup with these parameters in mod-crond...

start on stopped finish
stop on runlevel [!2]

--Xorg 18:57, 16 December 2009 (UTC)