Execution of maintenance scripts in Lion

Hi there,
as of the latest update to OS X Lion, the maintenance scripts have ceased to perform automatically. Before, the scripts executed at their proper times (daily, weekly, monthly) and whenever the computer was running (no need to wait for specific time slots). I was able to verify the processes via Maintidget, a widget that monitors script activity and can also be used to execute them manually. As I said, presently there is no more automated script activity - I have to force their execution via Maintidget. Does anyone has an idea why this should be so?

the discussion of the timed maintenance is an old one and does no longer apply.
Sure it does. Those scripts are ancient carry-overs from the early days of Unix and have not been changed much since then.
Also, macjack has a good point. Verify what the widget is telling you. Paste the following command into the Terminal to find out when they last ran:
ls -al /var/log/*.out
The output on my machine is:
Hyperion:~ thomas$ ls -al /var/log/*.out
-rw-r--r-- 1 root wheel 355773 Feb 20 06:05 /var/log/daily.out
-rw-r--r-- 1 root wheel 1352 Feb 1 06:07 /var/log/monthly.out
-rw-r--r-- 1 root wheel 2697 Feb 18 09:31 /var/log/weekly.out

Similar Messages

Running Periodic Maintenance Scripts in Mountain Lion

Here's an oldie question that I think has been asked with every new version of Mac OS X. If a user shuts down his Mac in the evening and restarts in at 7AM the next morning, do the three periodic maintenance scripts ever run in Mountain Lion?
It's easy to run them manually in Terminal or even with with an Applescript that I wrote, but do they need to be run under the condition I posed above?
Thanks.

For those people stating that no one needs to run these scripts or that they're somehow dangerous, please reconsider before posting inaccurate things like that.
I haven't seen anyone stating that the scripts are dangerous. Clearly, they aren't. They are, however, unnecessary if the system is rebooted every day. The only exception is the periodic daily script 100.clean-logs, which deletes symbolic links in /Library/Logs/CrashReporter to crash and panic reports in /Library/Logs/DiagnosticReports older than 60 days. The reports themselves are deleted by a different process. Conceivably, if this script didn't run for a long enough time, the boot volume might fill up with broken symlinks to deleted crash reports. How long would that take?
Well, a symbolic link takes up 77 bytes of storage space. Storage devices, however, allocate space in minimum units of one sector, which is usually 512 bytes. Some of the newer 3 TB hard drives have a 4096-byte sector size. So let's make some worst-case assumptions. Your boot drive is 3 TB, and you have only 1% of that space free, which is 30 GB. You generate 100 crash reports a day -- those being only crashes of system processes, of course, not user processes, which are logged to a different place. So your volume is filling up with symbolic links at the rate of about 400 KB a day. At that rate, it would take only about 75 years to fill it up completely.
So you're quite correct. If your system is always shut down -- not in sleep -- between the hours of 3:15 and 5:30 AM every day, you should manually run 100.clean-logs at least once every 75 years. Let's say once every 25 years, to be on the safe side. Thanks for pointing that out.
Properly Maintain Macbook pro: Apple Support Communities

Mac OS X maintenance scripts and multiple user accounts

Hi everyone
Just wondering how the default maintenance scripts scheduled to run in the early morning works with multiple user accounts. Our Macs at home all have multiple user accounts (one for each of us) and I'm wondering whether the scripts work their magic across all accounts (assuming the computer itself is switched on AND not asleep).
Also, is the behaviour the same regardless of Mac OS X version? More specifically we're using snow leopard, lion, mountain lion, and maybe shortly mavericks.
Thanks!
Joe.

The maintenance scripts run by periodic perform system tasks. They do nothing in a user's account (unless you modify the scripts or create your own). They are primarily designed for long lived systems (servers). There isn't any magic nor would a normal mac users find any differences whether they ran or not.
In all the operating system versions that you mention, the scripts will run when the computer wakes, assuming that the computer was turned on before the prescribe times.

How can I make the execution of my script faster

Hi everyone
How can I make the execution of my script faster, because it takes a lot of time to execute? The following is my script:
DECLARE
CURSOR C1 IS
SELECT A.ITEM_CODE,A.STORE_CODE,ST_UNIT,SA_UNIT,CART_QTY,QUANTITY_ON_HAND
FROM PROJ.IM_LOCATION A
WHERE A.ITEM_CODE BETWEEN :ITEM_FRM AND :ITEM_TO
AND A.STORE_CODE = :FRM_STORE
ORDER BY
A.STORE_CODE ;
CURSOR C2 IS
SELECT A.ITEM_CODE,A.STORE_CODE,ST_UNIT,SA_UNIT,CART_QTY,QUANTITY_ON_HAND
FROM PROJ.IM_LOCATION A
WHERE A.ITEM_CODE BETWEEN :ITEM_FRM AND :ITEM_TO
AND A.STORE_CODE = :FRM_STORE
ORDER BY
A.STORE_CODE ;
big_syb_qty_issue number(12,3);
small_syb_qty_issue number(12,3);
big_issue number(12,3);
small_issue number(12,3);
item_syb_code varchar2(30);
big_syb_qty_rec number(12,3);
small_syb_qty_rec number(12,3);
BI_SUPP_REC number(12,3);
SM_SUPP_REC number(12,3);
big_syb_qty_ADJ number(12,3);
small_syb_qty_ADJ number(12,3);
big_ADJ number(12,3);
small_ADJ number(12,3);
big_syb_qty_rec_iner number(12,3);
small_syb_qty_rec_iner number(12,3);
BI_INTER number(12,3);
SM_INTER number(12,3);
cl_big_qty number(12,3);
cl_small_qty number(12,3);
cl_big_qty1 number(12,3);
cl_small_qty1 number(12,3);
BIG_QTY_OPEN number(12,3);
SMALL_QTY_OPEN number(12,3);
BEGIN
     IF ((:FRM_STORE IS NULL) OR (:ITEM_FRM IS NULL) OR (:ITEM_TO IS NULL) OR (:DATE_FRM IS NULL)) THEN
          SHOW_MESSAGE('You Should Enter the Parameters Values Correctly Please try again !!!! ');
          RAISE FORM_TRIGGER_FAILURE;
          GO_FIELD('DATE_FRM');
     END IF;
DELETE FROM STOCK_AT_DATE_REP2;
COMMIT;
cl_big_qty := 0;
cl_small_qty := 0;
-- MESSAGE('Please Wait The System Calculating The Transactions !!!');
SET_APPLICATION_PROPERTY(CURSOR_STYLE,'BUSY');
FOR R IN C1
LOOP
cl_big_qty := R.CART_QTY ;
cl_small_qty := R.QUANTITY_ON_HAND;
-- Transerfer Data 1
BEGIN
SELECT B.ITEM_CODE,SUM(NVL(CART_QTY,0)) ,SUM(NVL(ITEM_QUANTITY,0))
INTO item_syb_code,big_syb_qty_issue,small_syb_qty_issue
FROM IM_TRANS_ISSUE_HEADER A,IM_TRANS_ISSUE_DETAILS B
WHERE A.DOC_CODE = B.DOC_CODE
AND B.DEL_STORE = R.STORE_CODE
AND ITEM_CODE = R.ITEM_CODE
AND DOC_DATE > :DATE_TO
GROUP BY
B.ITEM_CODE;
-- SHOW_MESSAGE('ISSUED BIG'||' '||big_syb_qty_issue);
exception
when no_data_found then big_syb_qty_issue := 0;
small_syb_qty_issue := 0;
when others then MESSAGE(10,sqlerrm);
END ;
-- Goods Received Data From Supplier 1
BEGIN
SELECT B.ITEM_CODE,SUM(B.CART_QTY),SUM(ITEM_QUANTITY)
INTO item_syb_code,big_syb_qty_rec,small_syb_qty_rec
FROM IM_GOODS_RECIEVE_HEADER A,IM_GOODS_RECIEVE_DETAILS B
WHERE A.DOC_CODE = B.DOC_CODE
AND STORE_CODE = R.STORE_CODE
AND ITEM_CODE = R.ITEM_CODE
AND DOC_DATE > :DATE_TO
GROUP BY
B.ITEM_CODE;
-- SHOW_MESSAGE('RECEIVED FROM SUPPLIER BIG'||' '||big_syb_qty_rec);
exception
when no_data_found then big_syb_qty_rec := 0;
small_syb_qty_rec := 0;
when others then message(10,sqlerrm);
END ;
-- Adjustement Data 1
BEGIN
SELECT B.ITEM_CODE ,SUM(NVL(CART_QTY,0)) ADJUST_QTY,SUM(NVL(ITEM_QUANTITY,0))
INTO item_syb_code,big_syb_qty_ADJ,small_syb_qty_ADJ
FROM IM_ADJUST_HEADER A,IM_ADJUST_DETAILS B
WHERE A.DOC_CODE = B.DOC_CODE
AND B.STORE_CODE = R.STORE_CODE
AND ITEM_CODE = R.ITEM_CODE
AND A.DOC_DATE > :DATE_TO
GROUP BY
B.ITEM_CODE;
-- SHOW_MESSAGE('Adjust BIG'||' '||big_syb_qty_ADJ);
exception
when no_data_found then big_syb_qty_ADJ := 0;
small_syb_qty_ADJ := 0;
when others then message(10,sqlerrm);
END ;
-- Goods Received Data From Stores 1
BEGIN
SELECT B.ITEM_CODE,SUM(B.CART_QTY),SUM(ITEM_QUANTITY)
INTO item_syb_code,big_syb_qty_rec_iner,small_syb_qty_rec_iner
FROM IM_TRANS_REC_HEADER A,IM_TRANS_REC_DETAILS B
WHERE A.DOC_CODE = B.DOC_CODE
AND REC_STORE = R.STORE_CODE
AND ITEM_CODE = R.ITEM_CODE
AND DOC_DATE > :DATE_TO
GROUP BY
B.ITEM_CODE;
-- show_message('here');
-- SHOW_MESSAGE('Received From Stores BIG'||' '||big_syb_qty_rec_iner);
exception
when no_data_found then
big_syb_qty_rec_iner := 0;
small_syb_qty_rec_iner := 0;
when others then message(10,sqlerrm);
END ;
cl_big_qty := (NVL(cl_big_qty,0) + NVL(big_syb_qty_issue,0));
cl_big_qty := (NVL(cl_big_qty,0) - NVL(big_syb_qty_rec,0));
cl_big_qty := (NVL(cl_big_qty,0) - NVL(big_syb_qty_rec_iner,0));
big_syb_qty_ADJ := -1 * NVL(big_syb_qty_ADJ,0);
cl_big_qty := (NVL(cl_big_qty,0) + NVL(big_syb_qty_ADJ,0));
-- srw.message(2000,'cl_small_qty'||cl_small_qty);
cl_small_qty := (NVL(cl_small_qty,0) + NVL(small_syb_qty_issue,0));
cl_small_qty := (NVL(cl_small_qty,0) - NVL(small_syb_qty_rec,0));
cl_small_qty := (NVL(cl_small_qty,0) - NVL(small_syb_qty_rec_iner,0));
small_syb_qty_ADJ := -1 * NVL(small_syb_qty_ADJ,0);
cl_small_qty := (NVL(cl_small_qty,0) + NVL(small_syb_qty_ADJ,0));
-- srw.message(2000,'cl_small_qty'||cl_small_qty); srw.message(2000,'cl_small_qty'||cl_small_qty);
INSERT INTO STOCK_AT_DATE_REP2
VALUES(R.STORE_CODE,R.ITEM_CODE,cl_big_qty,cl_small_qty,R.ST_UNIT,R.SA_UNIT,:DATE_FRM,
:DATE_TO,0,0,0,0,0,0,0,0,cl_big_qty,cl_small_qty);
cl_big_qty := 0;
cl_small_qty := 0;
END LOOP;
COMMIT;
FOR R IN C2
LOOP
-- Transerfer Data 2
BEGIN
SELECT B.ITEM_CODE,SUM(NVL(CART_QTY,0)) ,SUM(NVL(ITEM_QUANTITY,0))
INTO item_syb_code,big_issue,small_issue
FROM IM_TRANS_ISSUE_HEADER A,IM_TRANS_ISSUE_DETAILS B
WHERE A.DOC_CODE = B.DOC_CODE
AND B.DEL_STORE = R.STORE_CODE
AND ITEM_CODE = R.ITEM_CODE
AND DOC_DATE BETWEEN :DATE_FRM AND :DATE_TO
GROUP BY
B.ITEM_CODE;
-- SHOW_MESSAGE('ISSUED BIG'||' '||big_syb_qty_issue);
exception
when no_data_found then
big_issue := 0;
small_issue := 0;
when others then MESSAGE(10,sqlerrm);
END ;
-- Goods Received Data From Supplier 2
BEGIN
SELECT B.ITEM_CODE,SUM(NVL(B.CART_QTY,0)),SUM(NVL(ITEM_QUANTITY,0))
INTO item_syb_code,BI_SUPP_REC,SM_SUPP_REC
FROM IM_GOODS_RECIEVE_HEADER A,IM_GOODS_RECIEVE_DETAILS B
WHERE A.DOC_CODE = B.DOC_CODE
AND STORE_CODE = R.STORE_CODE
AND ITEM_CODE = R.ITEM_CODE
AND DOC_DATE BETWEEN :DATE_FRM AND :DATE_TO
GROUP BY
B.ITEM_CODE;
-- SHOW_MESSAGE('1- SM_SUPP_REC '||' '||SM_SUPP_REC );
-- SHOW_MESSAGE('RECEIVED FROM SUPPLIER BIG'||' '||big_syb_qty_rec);
exception
when no_data_found then
BI_SUPP_REC := 0;
SM_SUPP_REC := 0;
when others then message(10,sqlerrm);
END ;
-- Adjustement Data 2
BEGIN
SELECT B.ITEM_CODE ,SUM(NVL(CART_QTY,0)) ADJUST_QTY,SUM(NVL(ITEM_QUANTITY,0))
INTO item_syb_code,big_ADJ,small_ADJ
FROM IM_ADJUST_HEADER A,IM_ADJUST_DETAILS B
WHERE A.DOC_CODE = B.DOC_CODE
AND B.STORE_CODE = R.STORE_CODE
AND ITEM_CODE = R.ITEM_CODE
AND A.DOC_DATE BETWEEN :DATE_FRM AND :DATE_TO
GROUP BY
B.ITEM_CODE;
-- SHOW_MESSAGE('Adjust BIG'||' '||big_syb_qty_ADJ);
exception
when no_data_found then
big_ADJ := 0;
small_ADJ := 0;
when others then message(10,sqlerrm);
END ;
-- Goods Received Data From Stores 2
BEGIN
SELECT B.ITEM_CODE,SUM(NVL(B.CART_QTY,0)),SUM(NVL(ITEM_QUANTITY,0))
INTO item_syb_code,BI_INTER,SM_INTER
FROM IM_TRANS_REC_HEADER A,IM_TRANS_REC_DETAILS B
WHERE A.DOC_CODE = B.DOC_CODE
AND REC_STORE = R.STORE_CODE
AND ITEM_CODE = R.ITEM_CODE
AND DOC_DATE BETWEEN :DATE_FRM AND :DATE_TO
GROUP BY
B.ITEM_CODE;
-- show_message('here');
-- SHOW_MESSAGE('Received From Stores BIG'||' '||big_syb_qty_rec_iner);
exception
when no_data_found then
BI_INTER := 0;
SM_INTER := 0;
when others then message(10,sqlerrm);
END ;
BEGIN
     BIG_QTY_OPEN := 0;
SMALL_QTY_OPEN := 0;
BEGIN
SELECT NVL(S_BIG_QTY_OPEN,0) ,NVL(S_SMALL_QTY_OPEN,0)
INTO
BIG_QTY_OPEN,SMALL_QTY_OPEN
FROM STOCK_AT_DATE_REP2
WHERE S_STORE_CODE = R.STORE_CODE
AND S_ITEM_CODE = R.ITEM_CODE;
END;
BIG_QTY_OPEN := ((BIG_QTY_OPEN) + NVL(big_issue,0));
BIG_QTY_OPEN := ((BIG_QTY_OPEN) - NVL(BI_SUPP_REC,0));
big_adj := -1 * NVL(big_adj,0);
BIG_QTY_OPEN := ((BIG_QTY_OPEN) + NVL(big_adj,0));
BIG_QTY_OPEN := ((BIG_QTY_OPEN) - NVL(BI_INTER,0));
SMALL_QTY_OPEN := ((SMALL_QTY_OPEN) + NVL(SMALL_issue,0));
SMALL_QTY_OPEN := ((SMALL_QTY_OPEN) - NVL(SM_SUPP_REC ,0));
SMALL_adj := -1 * NVL(SMALL_adj,0);
SMALL_QTY_OPEN := ((SMALL_QTY_OPEN) + NVL(SMALL_adj,0));
SMALL_QTY_OPEN := ((SMALL_QTY_OPEN) - NVL(SM_INTER,0));
END;
BEGIN
UPDATE STOCK_AT_DATE_REP2
SET BIG_SUP_REC = BI_SUPP_REC,
SMALL_SUP_REC = SM_SUPP_REC,
BIG_ISSUE_TRAN = big_issue,
SMALL_ISSUE_TRAN = SMALL_issue,
BIG_ADJUST = big_adj,
SMALL_ADJUST = SMALL_adj,
BIG_INTER_REC = BI_INTER,
SMALL_INTER_REC = SM_INTER,
S_BIG_QTY_OPEN = BIG_QTY_OPEN,
S_SMALL_QTY_OPEN = SMALL_QTY_OPEN
WHERE S_STORE_CODE = R.STORE_CODE
AND S_ITEM_CODE = R.ITEM_CODE;
exception
when no_data_found then
NULL;
when others then
message(10,sqlerrm);
END;
END LOOP;
COMMIT;
SET_APPLICATION_PROPERTY(CURSOR_STYLE,'default');
SYNCHRONIZE;
-- SHOW_MESSAGE('The Data Have Been Calculated !!!');
END;
declare
     pl_id ParamList;
APPLICATION_ID VARCHAR2(20):='PRD';
          COMMAND_LINE VARCHAR2(100) :='STOCK_LEDGER';
BEGIN
pl_id := Get_Parameter_List('tmpdata');
IF NOT Id_Null(pl_id) THEN
Destroy_Parameter_List( pl_id );
END IF;
pl_id := Create_Parameter_List('tmpdata');
Add_Parameter(pl_id,'DATE_FRM',TEXT_PARAMETER,:DATE_FRM);
Add_Parameter(pl_id,'DATE_TO',TEXT_PARAMETER,:DATE_TO);
Add_Parameter(pl_id,'ITEM_FRM',TEXT_PARAMETER,:ITEM_FRM);
Add_Parameter(pl_id,'ITEM_TO',TEXT_PARAMETER,:ITEM_TO);
Add_Parameter(pl_id,'FRM_STORE',TEXT_PARAMETER,:FRM_STORE);
IF :REPORT_TYPE = 1 THEN
Run_Product(REPORTS,'C:\INV\RDF\STOCK_LEDGER.rdf',SYNCHRONOUS,RUNTIME,
FILESYSTEM, pl_id,NULL);
ELSIF :REPORT_TYPE = 2 THEN
Run_Product(REPORTS,'C:\INV\RDF\STOCK_LEDGER_2.rdf',SYNCHRONOUS,RUNTIME,
FILESYSTEM, pl_id,NULL);
END IF;
END;
Waiting for your valuable answer
Best Regards
Jamil Alshaibani

Make a matte in Photoshop.
From the Photoshop menu bar: File > New > Film & Video Presets. Choose one that suits your FCP project pixel dimensions. Make the background black. Place a white rectangle with rounded corners on top (the white will determine how much of your picture is visible). Flatten Image. Save as TIFF. Import into FCP.
Move your video clips up to V2. Place the imported TIFF on V1. Highlight all clips on V2.
Go to Modify > Composite Mode > Travel Matte Luma. Done.
If you want soft edges, no need for a matte. Double click your clip to place it in the Viewer. Open up the Motion tab > Crop > Edge Feather. Nice and quick. Copy and Paste attributes for the other clips.

Tracking the order of execution of sql scripts in SQL*Plus

In our production environment we sometimes have to run some .sql scripts in a particular order. Since the order of execution is important , i have created another .sql file caller caller.sql(shown at the bottom) which will call all the scripts in the right order.
i thought of putting a exec DBMS_LOCK.SLEEP (5); after the end of every execution of the script so that i can see the
'Ending script1'message .
The spooling within the caller script(execute_stack.log) has become meaningless because each script has a spool <filename.log> and spool off within it. These spool logs (for every script) is important for tracking purposes as each script belongs to a different development team and i have to send them the spooled log file after the execution.
I don't want to see the entire scripts running by in my screen. Since these scripts have their own spooling, i can later check the logs if the scripts where executed properly.
So i need two things.
1.I just need to see the following and nothing else in the screen.
Ending script1
Ending script2
Ending script3
.2. I need to log the order of execution. ie. the execute_stack.log should look like the above.Since there is a spool off within each script, this wouldn't be possible.Right?
Ending script1
Ending script2
Ending script3
.The caller.sql script which calls all the scripts in the right order
alter session set nls_date_format = 'DD-MON-YYYY hh24:MI:SS';
set serveroutput on
set echo on;
set feedback on;
spool execute_stack.log
@script1.sql
exec dbms_output.put_line ('Ending script1');
dbms_output.put_line(chr(10)||chr(10)||'.'||chr(10)||'.'||chr(10));
exec DBMS_LOCK.SLEEP (5);
@script2.sql
exec dbms_output.put_line ('Ending script2');
dbms_output.put_line(chr(10)||chr(10)||'.'||chr(10)||'.'||chr(10));
exec DBMS_LOCK.SLEEP (5);
@script3.sql
exec dbms_output.put_line ('Ending script3');
dbms_output.put_line(chr(10)||chr(10)||'.'||chr(10)||'.'||chr(10));
exec DBMS_LOCK.SLEEP (5);
@script4.sql
dbms_output.put_line(chr(10)||chr(10)||'.'||chr(10)||'.'||chr(10));
exec dbms_output.put_line ('Ending script3');
commit;
spool off;Is this a professional way of tracking the execution of .sql scripts?

Pete_Sg1 wrote:
Is this a professional way of tracking the execution of .sql scripts?No. There is very little professional about using .sql scripts on a production system - when stored procedures are safer, more robust, easier managed and controlled and secure.. and where a log table can be used to properly log the runtimes (and other stats) of each processing step.
Let's just take a look at the number of moving parts you need to schedule and run a .sql script. A cron job needs to be configured with the proper environment setting. It needs to run a shell script. That shell script needs to load SQL*Plus. SQL*Plus needs to connect to the database (starting a dedicated server process most likely). SQL*Plus then needs to read a .sql file, parse these commands and either execute these locally (SQL*Plus commands) or remotely (PL/SQL and SQL commands).
How can this be considered professional when the very same can be achieved with a
- stored procedure
- using DBMS_JOB to schedule the procedure for execution
There are so many things that can go wrong with the first method. And so few things that could go wrong with the last one. No contest as to which method is not only better, but also professional.
PS. See that you use Windows to run these scripts. It is even worse as it introduces another hardware and software layer making the scenario even more insecure & unsafe with more moving parts that can go wrong or simply fail.

CJS-00030 Assertion failed: Execution of SQL script reports an unexpected error.System Copy

Experts,
I am performing Homogeneous System copy using backup/restore method.I have taken QA system backup ie dump files and trying to build on Sandbox system for testing purpose.Everything went fine and was able to load the dump but stuck at one of the point and throwing me error
ERROR [cinstallercallbackimpl.cpp:228]
CJS-00030 Assertion failed: Execution of SQL script reports an unexpected error.
When I checked the sapinst_dev log I found the below error but not able to fix it and not aware to proceed further
1> use SID
1> EXEC sp_changedbowner sapsa
Msg 17362, Level 16, State 1:
Server 'SID', Procedure 'sp_changedbowner', Line 181:
The proposed new db owner already is a user in the database or owns the database.
(return status = 1)
I am sure these may be small changes that have to be made by changing the db owner and Im not exactly sure how to perform it.
Note:I am Using the Windows environment with Sybase ase database and SWPM tool to perform.
Appreciate your suggestions
Thanks

I fixed the issue ..by changing the owner sapsa.Bingo !!!!

Running Maintenance Scripts for Mac OS 10.5.8 HELP!

I am trying to run the maintenance scripts on my laptop for the first time. I go to Terminal type in "sudo periodic daily weekly monthly" and hit return. A warning message pops up the some data may be lost.... and the the Password prompt comes up. I back up consistently so I just want to run the scripts since it has never been done. However, when I try to type in my password, NOTHING types. I hit return and tried again, but nothing. Can someone please help me figure out what is wrong and if there is any other maintenance I need to do to the system?
Thanks in advance for any help.

You don't need to use any utility, or perform any procedure, to make sure OS X's built-in maintenance tasks have run under OS X 10.5 and later.
OS X 10.5 will run its cron jobs automatically (actually, they are no longer handled by the UNIX facility "cron", they are now handled by a similar facility called "launchd". if that means anything to you) whether you have left your computer on all night or not. You no longer need a utility to run missed maintenance as of OS X 10.5. It will run automatically at the next available opportunity. Actually, this was the case as of OS X 10.4, but a bug kept the maintenance routines from running more than once per restart under OS X 10.4. This was fixed in OS X 10.5
http://discussions.apple.com/message.jspa?messageID=6552347
http://arstechnica.com/reviews/os/macosx-10.4.ars/5
http://developer.apple.com/macosx/launchd.html

Maintenance scripts

Hi everyone,
I have two questions that I need help with, both related to the running of maintenance scripts. I downloaded and installed "anacron" the other day. When I check terminal, I notice that the daily maintenance script runs between midnight and 1am each day. I'm pretty sure that the default time for Tiger is somewhere between 3 and 4 am, a time which is assumed to not have much user activity. If the maintenance scripts are now being run around midnight or 1am, times when I am likely to be using the computer, will I notice a system slowdown? I've heard that supplemental maintenance scripts programs, (like Onyx, anacron, macjanitor, etc) are not necessary.
I would uninstall the program, but I've tried searching for the files that the readme says to delete, and I am unable to find them (using the Finder and EasyFind). I am not sure if the program has now replaced Tiger maintenance, and if I delete anacron then the Tiger scripts won't run anymore. Can someone provide me with a way to safely uninstall the program and ensure that the scripts will still run? Thank you.

Hi Louis
I have been running Anacron for several years with no problems. You will not know when it is running most of the time unless you hear your hardrive clicking. Since my computer sleeps through the scheduled times it normally would run, it will run the scrips at times after the time period exceeds the time limit set since last run. Daily scripts every 24 hrs., etc. Anacron will check every hour to test the time limit to see if it needs to run and will run the scripts when needed. Therefore, if your computer was sleeping or off less than 24 hrs. of the time the daily script was set to run or since the last time it was run and you wake it or turn it on 3 days later, the daily script will run approximately 15 minutes past the next hour.
As I said, it has never given me a problem and you won't ever have to worry about the log files getting bloated.
These scripts don't really need to be run that often and some people prefer to use manuel programs such as ONYX to run them on occasion. That's probably more of a personal preference. I choose not to want to think about it and let Anacron do it's thing. If I ever think it may be causing problems, I won't hesitate to remove it. But so far on 3 computers, no problems.
But if you feel the need to uninstall it follow this:
To uninstall Anacron, go to Hard Drive/Library/LaunchDaemons/anacron.plist. Move the file "anacron.plist" to the desktop and restart the computer. Then you can trash anacron.plist file.
Or, search in the Finder or with spotlight for Anacron. You will see the "anacron.plist" file. Delete it and restart the computer. Then you will be able to empty the trash.
I can't really say how much this and permission repair has really helped, but I can tell you that for 3 years I have virtually no problems with my computers and have never had to reinstall the operating system on any of them other than updating or moving to the newer OSX.

Has someone written a Script for Lion to capture Macbook details?

Has someone written a Script for Lion to capture Macbook details?
I would need a basic script for starts - the one that captures
Mac's memory utilization
Are there any libraries in this regard and whether normal bash scripting
is used for capturing such details?

I don't see any so far, but load the Dictionaty...

Maintenance Scripts?? MacJanitor?

On my G4 iBook running 10.3 I found and used an app called Macjanitor.
Here is the blurb from their site.
Freeware utility to run the system's daily, weekly, and monthly maintenance scripts.
These scripts are normally run between 3am and 5am, and will not be run if you shut off your Mac at night. This can allow log files to grow very large, and prevent system databases from getting backed up.
With MacJanitor, you can run these scripts 'by hand' periodically without having to use the Terminal to keep your Mac OS X machine in top racing form.
Excellent for laptop users and others who shut off or put their Macs to sleep at night.
Supposedly normal set maintenance scripts in OS X are set to run around 3-5am (not sure where you see this) but they will only run if the system is on (of course) and Not asleep. Well I can guarantee my system is alseep as that time !!
I also stumbled across someone commenting on how useless MacJanitor was because they use something called Aancron http://members.cox.net/18james/anacron-tiger.html
Blurb from their site
Anacron runs the periodic daily, weekly and monthly tasks on your Mac even if the machine (a laptop, for example) spends much of its time asleep or switched-off. Anacron silently checks when you reboot and every sixty minutes while the computer is running to see if the various periodic scripts are overdue, and runs them if necessary. The advantage of Anacron over many other solutions to this issue is that it runs as a proper Unix background process, requires no user intervention, and uses the regular periodic scripts, including local additions or modifications.
Sounds like a better solution, but I curious to what others due for running these maintenance scripts?
Has anyone used either of these 2 programs under 10.4?
Opinions and experiences please.

Yes, I use OnyX because it runs them at times I have scheduled it to do so. 10.4.0 or later runs them automatically, if the computer is on and idle at 1AM, which isn't normal for many people so running them with an app can be good if you leave your machine running for days or weeks at a time. That said if you shut down your machine down every night there is no need to because the tasks will be run at boot each morning.

OSB maintenance scripts

Where can I find more information about OSB's maintenance scripts? Specifically, what is responsible for rotation and cleanup of old files under /usr/local/oracle/backup/admin/history/host/ on the OSB server?
I have files under /usr/local/oracle/backup/admin/history/host/<hostname>/<date>.<hostname>.0.saved that are from more than 7 months ago. Under OSB's policies, we have the "Log retain time" and "Transcript retain time" set to 14 days (default is 7 days), and the "Job retain time" set to 21 days (default is 30 days). Do any of those retention policy settings impact the cleanup of the above mentioned files? It seems they do not, as the files located there that are 7+ months old are quite past that retention and have not been cleaned up.
Are the files under /usr/local/oracle/backup/admin/history/host/ maintained by OSB internally, or are those files and directories something that I as the system admin should be cleaning via a cronjob?
OSB version 10.4.0.2.0

That Mac sets up I-net connection not only in the night.
The logs of router controlling the lan where the Mac is physically present show for some day
a setup of nearly 8 I-net connections between 9 and 18 o'clock.
Again it must have been the Mac because the WiFi access point was shut down in that time
and the only other client with Ethernet connection was also shut down at that time.

Root crontab no system maintenance scripts

Server: HP DL380, Redhat 4 update 6 (download from linux.oracle.com)
Today I checked crontab and noticed that there are no system maintenance scripts running under root, to e.g. rotate log files, etc. Is this normal, any suggestions please?
Best regards

Check the directories below. Linux cron has directories for hourly, daily, weekly and monthly root scripts where you can drop scripts that you want to run periodically. This is handy if you do not want to maintain a root crontab file.
ll /etc |grep cron
-rw-r--r-- 1 root root 329 Sep 28 2004 anacrontab
drwxr-xr-x 2 root root 4096 Mar 27 15:37 cron.d
drwxr-xr-x 2 root root 4096 Apr 7 16:08 cron.daily
-rw-r--r-- 1 root root 0 May 12 2007 cron.deny
drwxr-xr-x 2 root root 4096 Sep 20 2004 cron.hourly
drwxr-xr-x 2 root root 4096 May 12 2007 cron.monthly
-rw-r--r-- 1 root root 255 Sep 20 2004 crontab
drwxr-xr-x 2 root root 4096 Nov 28 2007 cron.weekly

Do I need maintenance scripts ?

I am using Macaroni which runs Unix maintenance script every time I start the computer. At night the cpmputer is shut off. Do I really need to run these scripts with Snow Leopard ?

I know people have weighed in on this before.
sudo periodic all
that is all and no I don't leave mine on, or run them daily, in fact hardly at all. But I do other things to keep the system in top shape.
as long as the utility is certified compatible, you are fine. I think Onyx, SL Cache Cleaner and others can also automatically schedule cron to run next time, I just don't do anything automatic.
Every time you start? or once a day? some scripts are only weekly and monthly anyway.

Cron, cronX and maintenance scripts

In my old iBook I used cronX (I think that's the name) to set the unix maintenance scripts to run when the computer is likely to be awake. I don't know that those things bought me anything, but can't hurt, right?
My problem - I'd like to get a current version for the new MacBook (wow! - way cool!) but neither Google nor VersionTracker have a listing for any version of cronX. I recall it came from somewhere in Europe so perhaps that's why? Also have heard of MacJanitor and maybe a couple of other apps that will do a similar function.
Can anyone point me to a source for cronX or similar?
Thanks!
MacBook 13" 2.0GHz Mac OS X (10.4.6)

Oops - got lucky searching for something else!
It's cronniX from http://h5197.serverkompetenz.net:9080/abstracture_public/projects-en/cronnix/
MacBook 13" 2.0GHz Mac OS X (10.4.6)

Cron & missed maintenance scripts

Hiya.
I'm assuming the cron-driven daily/weekly/monthly maintenance scripts are not run if the computer is sleeping.
What (if any) is the easiest way to get caught up on those if missed for a while?
Thanks in advance...

Hi--
They're actually not run by cron any more, but by launchd. So, if the computer is sleeping, but not actually off, they will eventually run. On my PowerBoook, the daily runs about once a week, the weekly every couple of months, and the monthly not often at all.
If you want to run them by hand, you can easily run them in the Terminal (press the "enter" key after each line):
<pre class="command">sudo periodic daily
sudo periodic weekly
sudo periodic monthly</pre>
I think you can run them all like this, too:
<pre class="command">sudo periodic daily weekly monthly</pre>
but I've never run them that way. I either let them run on their own, or run them one at a time.
charlie

Execution of maintenance scripts in Lion

Similar Messages

Maybe you are looking for