According to man(5) in SUSE 10, a crontab @reboot entry is supposed to run, when the computer boots. However, I can't seem to get it to do anything. Is there something I'm missing? Is there some magic incantation that I have to say? tnx jk
James Knott wrote:
According to man(5) in SUSE 10, a crontab @reboot entry is supposed to run, when the computer boots. However, I can't seem to get it to do anything. Is there something I'm missing? Is there some magic incantation that I have to say?
tnx jk
Forgot to mention, I'm editing /etc/crontab directly with vi, as that's apparently the only way to edit that file.
On 10/9/05, James Knott
James Knott wrote:
According to man(5) in SUSE 10, a crontab @reboot entry is supposed to run, when the computer boots. However, I can't seem to get it to do anything. Is there something I'm missing? Is there some magic incantation that I have to say?
tnx jk
How does this particular line look like in /etc/crontab? Is crond running? Did you specify user root? You can test the entry with @reboot root echo "My @reboot entry is working" >> /var/log/messages \Steve
Steve Graegert wrote:
On 10/9/05, James Knott
wrote: James Knott wrote:
According to man(5) in SUSE 10, a crontab @reboot entry is supposed to run, when the computer boots. However, I can't seem to get it to do anything. Is there something I'm missing? Is there some magic incantation that I have to say?
tnx jk
How does this particular line look like in /etc/crontab? Is crond running? Did you specify user root? You can test the entry with
@reboot root echo "My @reboot entry is working" >> /var/log/messages
\Steve
Your example showed the problem. I forgot to include "root" in the command. tnx
On Sun October 9 2005 9:07 am, James Knott wrote:
Forgot to mention, I'm editing /etc/crontab directly with vi, as that's apparently the only way to edit that fil what happens when you type this command:
crontab -e -- Paul Cartwright Registered Linux user # 367800
Paul Cartwright wrote:
On Sun October 9 2005 9:07 am, James Knott wrote:
Forgot to mention, I'm editing /etc/crontab directly with vi, as that's apparently the only way to edit that fil what happens when you type this command:
crontab -e
That edits individual crontab files, for the user, including root. It does not edit /etc/crontab. This is mentioned in the online SUSE manual.
On Sun October 9 2005 10:11 am, James Knott wrote:
crontab -e
That edits individual crontab files, for the user, including root. It does not edit /etc/crontab. This is mentioned in the online SUSE manual. you are right, I'm used to modifying crontab files, not /etc/crontab.
-- Paul Cartwright Registered Linux user # 367800
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2005-10-09 at 09:36 -0400, Paul Cartwright wrote:
On Sun October 9 2005 9:07 am, James Knott wrote:
Forgot to mention, I'm editing /etc/crontab directly with vi, as that's apparently the only way to edit that fil what happens when you type this command:
crontab -e
That edits the file "/var/spool/cron/tabs/root" (or "user"). Instead, /etc/crontab has to be edited directly, with vi or whatever. - -- Cheers, Carlos Robinson -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFDSSUxtTMYHG2NR9URAhU0AKCJ2nc0Jjk1tBOQPevC0vkCqG1M6QCglCOQ YHeWRRF2WXQOWVmx6FiLHTk= =zKe/ -----END PGP SIGNATURE-----
On Sunday 09 October 2005 09:07 am, James Knott wrote:
James Knott wrote:
According to man(5) in SUSE 10, a crontab @reboot entry is supposed to run, when the computer boots. However, I can't seem to get it to do anything. Is there something I'm missing? Is there some magic incantation that I have to say?
tnx jk
Forgot to mention, I'm editing /etc/crontab directly with vi, as that's apparently the only way to edit that file.
Nope.... set the env variable: EDITOR=/<path to your fav editor>
Bruce Marshall wrote:
On Sunday 09 October 2005 09:07 am, James Knott wrote:
James Knott wrote:
According to man(5) in SUSE 10, a crontab @reboot entry is supposed to run, when the computer boots. However, I can't seem to get it to do anything. Is there something I'm missing? Is there some magic incantation that I have to say?
tnx jk Forgot to mention, I'm editing /etc/crontab directly with vi, as that's apparently the only way to edit that file.
Nope.... set the env variable: EDITOR=/<path to your fav editor>
What I was referring to, was not the choice of editor, but the fact that the command "crontab -e" does not edit /etc/crontab. It edits the crontab file for the user running the command. Each user, including root, can have their own crontab file.
participants (5)
-
Bruce Marshall
-
Carlos E. R.
-
James Knott
-
Paul Cartwright
-
Steve Graegert