Very Computer

Friends,

1.      Under AIX 4.1.5 how to restart or refresh cron daemon without
rebooting system? I even could not understood role of telinit q

2.      cron daemon NEVER exits (I tried kil -9 PID , taking rebirth ) I am
just keen to know to stop cron daemon (like stopsrc -s qdaemon).

Thank,

VK

--
The reason many people fail to recognise opportunity is because it comes
disguised as Hard Work. Cleverness carries the day, But Wisdom endureth.

It's easier to answer your 1st Q after the 2nd:

2.) cron is controlled by init: inittab tells init to *respawn* cron.
    So cron will be restarted by init everytime it terminates/is killed.
    If you really want to keep cron from running, you have to modify
    that entry in inittab *highly unrecommended!*

1.) If you kill cron (with or without -9) it *will* exit and be
    restarted. Compare the PID before and after.
    To refresh it use kill -1.

Are you facing problems with cron or are you just curious?

Regards,
Heiko

V K Agarwal schrieb:

Quote:>1.  Under AIX 4.1.5 how to restart or refresh cron daemon without
>rebooting system? I even could not understood role of telinit q

If what you are trying to accomplish is a refresh of cron after having
modified the cron table, you can do so in another way.

Use the 'crontab -e' command which will start the editor with
the current crontab, which you can then edit.
After quitting the editor (and saving your changes!), cron will
automatically be refreshed with the new table.

Regards

Peter

|>
|> >1.    Under AIX 4.1.5 how to restart or refresh cron daemon without
|> >rebooting system? I even could not understood role of telinit q
|>
|> If what you are trying to accomplish is a refresh of cron after having
|> modified the cron table, you can do so in another way.
|>
|> Use the 'crontab -e' command which will start the editor with
|> the current crontab, which you can then edit.
|> After quitting the editor (and saving your changes!), cron will
|> automatically be refreshed with the new table.
|>
|>
    A safer thing to do would be to copy the cron file back edit it and then
crontab it back since the "e" and "r" are so close together and we all make typos from
time to time ;)

ex,
for root

cp /var/spool/cron/crontabs/root /rootcron
vi /rootcron
# make your changes
crontab rootcron
crontab -l | pg #verify the changes are in there.

--
Phil Langerholc - DCS UNIX Systems Support
IBM Global Services - Corporate Logistics Team, Poughkeepsie, NY

The opinions expressed are my own and do not reflect those of IBM