search

ImagineAdmin / cronnix

Automatically exported from code.google.com/p/cronnix
0 stars 0 forks source link

selectRow:byExtendingSelection: in class MyTableView is deprecated #14

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago 
Scheduled run of a cron job not performing.
*/15 * * * *  cp file file
If I manually run  "Run Now" it works.
But no action is taken by cron using the scheduler

Saw this in the console

CronniX[66277]: *** WARNING: Method selectRow:byExtendingSelection: in class 
MyTableView is deprecated. It will be removed in a future release and should no 
longer be used.

Issue #2 
also when tried to open the user root

You can't open the application sucrontab because PowerPC applications are no 
longer supported.
The system returned an empty crontab for 'root'. This probably just means that 
there's no crontab for this user yet. Pressing OK will allow you to edit and 
install a new crontab and you will never see this alert sheet again. If, 
however, you are sure that 'root' does have a crontab, then you may have 
encountered an temporal anomaly. Contact the author (see the About box) and 
complain like there's no tomorrow.

What steps will reproduce the problem?
1. message 1 : a manual run of a cron entry after restarting cronix
2.
3. Message 2: Change user to root

What is the expected output? What do you see instead?
No output 

What version of the product are you using? On what operating system?
3.0.2   Lion 10.7.3

Please provide any additional information below.

Original issue reported on code.google.com by info...@ucnrs.org on 25 Apr 2012 at 11:59

GoogleCodeExporter commented 8 years ago 
Regarding your first issue, have you confirmed that you can successfully 
schedule tasks at all? Sometimes the cron daemon is not up and running. A quick 
test if cron is working can be made by dragging and dropping a program like 
TextEdit on CronniX' main window. This will schedule starting the program. 
(Make sure you save to actually write out the task.) Set the time a minute 
ahead wait for it to pop up.

If that works, the second typical pitfall is that cron has a different 
environment from your shell or the shell CronniX uses for the run now command. 
For example the cron environment has a very minimal path setting. Although "cp" 
should be in it, I've had the best success with cron when I wrote out the full 
path for all commands.

Regarding your second issue, this is a duplicate of #11. Please check that 
issue for more details.

Hope that helps,
Sven

Original comment by sven.a.s...@gmail.com on 30 Apr 2012 at 6:06

GoogleCodeExporter commented 8 years ago 
PS: The warning is not relevant to your problem.

Original comment by sven.a.s...@gmail.com on 30 Apr 2012 at 6:07