Yamaha Home Theater
Cocktail 3.7 not running weekly and monthly scripts under Mac OS X 10.4.3 and 10.4.4
For some users, Cocktail 3.7 fails to run the Mac OS X standard weekly and monthly maintenance scripts, despite being set to do so.
MacFixIt reader Gabriel Dorado writes:
"Cocktail 3.7 only runs the daily script and not the weekly or monthly ones even when they are selected at 'System/Scripts' and you click Run. Likewise when you run the Pilot with all tasks selected.
You can verify that the logs have not been run by launching the Terminal (located in Applications/Utilities) and entering the command:
- ls -al /var/log/*.out
where you will see the following if the scripts did not run:
- -rw-r--r-- 1 root wheel 22378 Jan 12 03:15 /var/log/daily.out
and the following if the scripts did run:
- -rw-r--r-- 1 root wheel 112831 Feb 1 10:38 /var/log/daily.out
- -rw-r--r-- 1 root wheel 938 Feb 1 20:01 /var/log/monthly.out
- -rw-r--r-- 1 root wheel 2800 Feb 1 20:07 /var/log/weekly.out
Until the bug is fixed, you can manually run the weekly and monthly scripts via the following Terminal commands (press return after each):
- sudo periodic monthly
- sudo periodic weekly
Feedback? Late-breakers@macfixit.com.
Resources
favour of Macaroni. It's functions can be controlled in a System Preferences
panel. Once set, it runs all Unix maintenance scripts faithfully on schedule
but waits for the computer to be active before doing so. It is totally
transparent and runs in the background. It also repairs permissions weekly
and will rid installations of any language-based resources (localization) that
you specify once a month. Version 2.0.6 is the most up-to-date, but will not
run on MacIntel machines yet.
Griff
There is a beta of 2.0.7 that will run on the new Intel machines.
mainly used for cache cleaning etc.
The problem here is: The "troubled guy" sends a bug report to Macfixit.com
instead of using built in bug reporting in Cocktail.
I have used that built in feature to alert Cocktail author. I am sure he will
provide a fix or insight into problem.
The problem is that people like you never discovered this issue.
Thanks to the "troubled guy" for reporting the issue. Thanks to actions like that
everybody may know and the issue can be explained and fixed quicker.
Grow up!
I have a good clue who sent that report and who are you sir.
You should grow up. Sending bogus feedback to versiontracker not enough
anymore?
You can view these logs by choosing Outputs from the Window menu.
you run cron scripts using Cocktail, the output is redirected to other log files
(located in /Library/Application Support/Cocktail/ - you can view these logs by
choosing Outputs from the Window menu) and the log files (.out) in var/log/ are
not modified.
No utility of which I'm aware writes to the /var/log/xxx.out logs when
running the cron scripts.
For confirmation that the crons have been run launch /Applications/Utilities/
Console/system.log and you should see the following text
Feb 4 23:51:31 Artie's-Computer syslogd: restart
Feb 4 23:51:31 Artie's-Computer syslogd: hostname changed, "localhost" to
"Artie's-Computer"
Feb 4 23:51:31 Artie's-Computer sudo: artie : TTY=unknown ; PWD=/ ;
USER=root ; COMMAND=/bin/sh /etc/weekly
Feb 4 23:51:32 Artie's-Computer kernel: resize: max chain len 16, new table
size 8192
Feb 4 23:51:57 Artie's-Computer kernel: resize: max chain len 18, new table
size 16384
Feb 4 23:52:09 Artie's-Computer syslogd: restart
Feb 4 23:52:09 Artie's-Computer sudo: artie : TTY=unknown ; PWD=/ ;
USER=root ; COMMAND=/bin/sh /etc/monthly
Feb 4 23:52:09 Artie's-Computer syslogd: restart
in which the first "restart" represents the daily script, etc.
Well Macaroni looks when did a script run by its (out file) time stamp. So when a
user has Macaroni, if he/she has Cocktail too and run all scripts and when
cocktail changes the "out" file stamp of the system, it would count as run.
I think , it could be achieved doing x.job >~/Application Support/Utility
So output will be redirected.
So, scripts run in fact, their .out files are staying away from system directories,
good...
No utility of which I'm aware writes to the /var/log/xxx.out logs when
running the cron scripts.
For confirmation that the crons have been run launch /Applications/Utilities/
Console/system.log and you should see the following text
Feb 4 23:51:31 Artie's-Computer syslogd: restart
Feb 4 23:51:31 Artie's-Computer syslogd: hostname changed, "localhost" to
"Artie's-Computer"
Feb 4 23:51:31 Artie's-Computer sudo: artie : TTY=unknown ; PWD=/ ;
USER=root ; COMMAND=/bin/sh /etc/weekly
Feb 4 23:51:32 Artie's-Computer kernel: resize: max chain len 16, new table
size 8192
Feb 4 23:51:57 Artie's-Computer kernel: resize: max chain len 18, new table
size 16384
Feb 4 23:52:09 Artie's-Computer syslogd: restart
Feb 4 23:52:09 Artie's-Computer sudo: artie : TTY=unknown ; PWD=/ ;
USER=root ; COMMAND=/bin/sh /etc/monthly
Feb 4 23:52:09 Artie's-Computer syslogd: restart
in which the first "restart" represents the daily script, etc.
- by Ilgaz February 6, 2006 7:52 AM PST
- As a cocktail user here I used the built in bug reporting of application to tell
- Like this Reply to this comment
-
(11 Comments)about this "bug".
Here is the response I got which explains in fact these scripts mentioned runs
too
(pasting below, posted to macfixit mail too)
"
Hello,
Thank you very much for your email. Cocktail is properly running all three
cron scripts. However, if
you run cron scripts using Cocktail, the output is redirected to other log files
(located in /Library/Application Support/Cocktail/ - you can view these logs
by
choosing Outputs from the Window menu) and the log files (.out) in var/log/
are
not modified.
Regards,
Kristofer Szymanski
Maintain
"