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

Similar Messages

  • Requesting System Maintenance Mode

    I just installed Solaris 10 on a SunFire v100 and patched the os. I added a second drive and mirrored it. Now I get this message 2 out of 3 times when I reboot the server.....
    LOM event: +36d+22h57m55s host reset
    Sun Fire V100 (UltraSPARC-IIe 548MHz), No Keyboard
    OpenBoot 4.0, 1024 MB memory installed, Serial #57166297.
    Ethernet address 0:3:ba:68:49:d9, Host ID: 836849d9.
    Executing last command: boot
    Boot device: rootdisk File and args:
    SunOS Release 5.10 Version Generic_118822-27 64-bit
    Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
    Use is subject to license terms.
    Hostname: gandalf
    Jan 31 17:41:02 svc.startd&#91;7&#93;: svc:/system/boot-archive:default: Method "/lib/sv<br />
    c/method/boot-archive" failed with exit status 1.
    Jan 31 17:41:02 svc.startd&#91;7&#93;: svc:/system/boot-archive:default: Method "/lib/sv<br />
    c/method/boot-archive" failed with exit status 1.
    Jan 31 17:41:02 svc.startd&#91;7&#93;: svc:/system/boot-archive:default: Method "/lib/sv<br />
    c/method/boot-archive" failed with exit status 1.
    &#91; system/boot-archive:default failed (see 'svcs -x' for details) &#93;
    Requesting System Maintenance Mode
    (See /lib/svc/share/README for more information.)
    Console login service(s) cannot run
    Root password for system maintenance (control-d to bypass):
    Any clue on what I should do?
    Thanks!
    Chris Edwards

    Hi,
    Can you please check the below note
    Solaris11 cannot boot and goes into maintenance ( svc:/system/early-manifest-import:default exited with status 1 ) (Doc ID 1526559.1)
    It has the solution workaround. Kindly let us know in case issue is not fixed
    Thanks,
    Krishna

  • Reschedule maintenance scripts?

    Is there a way to reschedule the maintenance scripts that run from 3:15 until 5:30?
    I would like to run them earlier so that I can shut down the computer before I go to bed, since I don't want to leave the machine on all night. I know you can do them manually, but I don't want to have to do that every day.
    Also, does anyone know if there would be some sort of problem if I rescheduled them? Can one continue working while they are running?
    Thanks
    eMac 1.25GHz, 512MB   Mac OS X (10.3.5)  

    Sorry for the dead link. I guess O'Reilly has issues with a direct link. Here's another site that explains how to edit crontab-
    Using the cron maintenance utility
    Though written for 10.1 the instructions are the same. Your system crontab file will look different. Scripts are run by periodic in Panther instead of directly running a specific script. Try experimenting with pico if you haven't used a command line text editor before. The OS is full explanations try the following commands in the Terminal application-
    man cron
    man periodic
    man periodic.conf
    man pico
    man 5 crontab
    man crontab
    Try NifflerX's suggestion if this seems to hard. Though using the Terminal way is good practice for changing system configuration files without the risk of gumming up your OS.

  • Getting error while opening layout in mobile system maintenance

    Hi Experts,
    I implemented note 904571 to prefilldata, with which all standard layouts loaded to mobile system maintenance. But problem here is if I try to open any one of the layout its giving following error
    "An unhandled exception has occured in your application. If you click continue, the application will ignore this error and attempt to ccontinue. If you click Quit, the application will be shut down immediately.
    Object variable or with variable not set."
    If I click on details of error, its giving following details
    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.
    Exception Text **************
    System.NullReferenceException: Object variable or With block variable not set.
       at Microsoft.VisualBasic.CompilerServices.LateBinding.LateGet(Object o, Type objType, String name, Object[] args, String[] paramnames, Boolean[] CopyBack)
       at MSY.Tlayoutdet1.ctrlctrlbtnOpen_onClicked() in C:\Ars_Translation50\Batch\app\MSY\src\Tlayoutdet1.vb:line 281
       at SAP.MT.FW.UI.ExposedFWElements.CoreCtrlButton.BtnClicked()
       at SAP.MT.FW.UI.ExposedFWElements.CoreCtrlButton.IPeerCtrlListener_btnClicked()
       at SAP.MT.FW.UI.PeerLayer.PeerCtrlButton.button_Click(Object sender, EventArgs e)
       at System.Windows.Forms.Control.OnClick(EventArgs e)
       at SAP.MT.FW.UI.NativeControl.NBaseControl.OnClick(EventArgs e)
       at SAP.MT.FW.UI.NativeControl.NButton.OnClick(EventArgs e)
       at SAP.MT.FW.UI.NativeControl.NButton.mButton_Click(Object sender, EventArgs e)
       at System.Windows.Forms.Control.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnClick(EventArgs e)
       at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
       at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ButtonBase.WndProc(Message& m)
       at System.Windows.Forms.Button.WndProc(Message& m)
       at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    Loaded Assemblies **************
    mscorlib
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.2407
        CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
    MobileClient
        Assembly Version: 5.0.0.0
        Win32 Version: 5.11.0.40
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MobileClient.exe
    UFCore
        Assembly Version: 5.0.0.0
        Win32 Version: 5.11.0.40
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFCore.DLL
    UFCoreExt
        Assembly Version: 5.0.0.0
        Win32 Version: 5.11.0.40
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFCoreExt.DLL
    System.Windows.Forms
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.2365
        CodeBase: file:///c:/windows/assembly/gac/system.windows.forms/1.0.5000.0__b77a5c561934e089/system.windows.forms.dll
    System
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.2407
        CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
    UFInternal
        Assembly Version: 5.0.0.0
        Win32 Version: 5.11.0.40
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFInternal.DLL
    UFCommon
        Assembly Version: 5.0.0.0
        Win32 Version: 5.11.0.40
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFCommon.DLL
    UFStorage
        Assembly Version: 5.0.0.0
        Win32 Version: 5.11.0.40
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFStorage.DLL
    Interop.Scripting
        Assembly Version: 1.0.0.0
        Win32 Version: 1.0.0.0
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Interop.Scripting.DLL
    Microsoft.VisualBasic
        Assembly Version: 7.0.5000.0
        Win32 Version: 7.10.6310.4
        CodeBase: file:///c:/windows/assembly/gac/microsoft.visualbasic/7.0.5000.0__b03f5f7f11d50a3a/microsoft.visualbasic.dll
    UFControlLibrary
        Assembly Version: 5.0.0.0
        Win32 Version: 5.11.0.40
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFControlLibrary.DLL
    Interop.UFGeneratorInterfaces
        Assembly Version: 1.0.0.0
        Win32 Version: 1.0.0.0
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Interop.UFGeneratorInterfaces.DLL
    System.Drawing
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.2327
        CodeBase: file:///c:/windows/assembly/gac/system.drawing/1.0.5000.0__b03f5f7f11d50a3a/system.drawing.dll
    MTIServices
        Assembly Version: 5.0.0.0
        Win32 Version: 5.11.0.40
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTIServices.DLL
    UFDialogs
        Assembly Version: 5.0.0.0
        Win32 Version: 5.11.0.40
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFDialogs.DLL
    UFIPlugins
        Assembly Version: 5.0.0.0
        Win32 Version: 5.11.0.40
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/UFIPlugins.DLL
    System.Xml
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.2371
        CodeBase: file:///c:/windows/assembly/gac/system.xml/1.0.5000.0__b77a5c561934e089/system.xml.dll
    Interop.ERRCOMPLib
        Assembly Version: 1.0.0.0
        Win32 Version: 1.0.0.0
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Interop.ERRCOMPLib.DLL
    MTBLLFWInterfaces
        Assembly Version: 1.0.0.0
        Win32 Version: 5.11.0.40
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTBLLFWInterfaces.DLL
    Accessibility
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.573
        CodeBase: file:///c:/windows/assembly/gac/accessibility/1.0.5000.0__b03f5f7f11d50a3a/accessibility.dll
    MSY
        Assembly Version: 0.0.0.0
        Win32 Version: 0.0.0.0
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/bin/MSY.dll
    MTBLLFW
        Assembly Version: 5.0.0.0
        Win32 Version: 5.11.0.40
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTBLLFW.DLL
    MTFWServices
        Assembly Version: 5.0.0.0
        Win32 Version: 5.11.0.40
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTFWServices.DLL
    MTServices
        Assembly Version: 5.0.0.0
        Win32 Version: 5.11.0.40
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTServices.DLL
    OnlineOffline
        Assembly Version: 1.0.2477.11060
        Win32 Version: 1.0.2477.11060
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/OnlineOffline.DLL
    vqq-mx7r
        Assembly Version: 0.0.0.0
        Win32 Version: 1.1.4322.2407
        CodeBase: file:///c:/windows/assembly/gac/system/1.0.5000.0__b77a5c561934e089/system.dll
    RegexAssembly40_0
        Assembly Version: 0.0.0.0
        Win32 Version: n/a
        CodeBase:
    MTBLLFWMetaInternal
        Assembly Version: 5.0.0.0
        Win32 Version: 5.11.0.40
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/MTBLLFWMetaInternal.DLL
    TLSender
        Assembly Version: 1.5.1.0
        Win32 Version: 5.11.0.40
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/TLSender.DLL
    Interop.CRYPTINGLib
        Assembly Version: 1.0.0.0
        Win32 Version: 1.0.0.0
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Interop.CRYPTINGLib.DLL
    Authentication
        Assembly Version: 5.5.0.0
        Win32 Version: 5.5.0.0
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Authentication.DLL
    System.Data
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.2365
        CodeBase: file:///c:/windows/assembly/gac/system.data/1.0.5000.0__b77a5c561934e089/system.data.dll
    System.EnterpriseServices
        Assembly Version: 1.0.5000.0
        Win32 Version: 1.1.4322.2326
        CodeBase: file:///c:/windows/assembly/gac/system.enterpriseservices/1.0.5000.0__b03f5f7f11d50a3a/system.enterpriseservices.dll
    sfabol
        Assembly Version: 0.0.0.0
        Win32 Version: 0.0.0.0
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/bol/apps/sfabol/vba/WBIT/sfabol/bin/sfabol.dll
    SSActiveTreeView.SSTree
        Assembly Version: 1.0.0.0
        Win32 Version: 1.0.0.0
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/Bin/SSActiveTreeView.SSTree.dll
    SSActiveTreeView
        Assembly Version: 1.0.0.0
        Win32 Version: 1.0.0.0
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/Bin/SSActiveTreeView.DLL
    AxSSActiveTreeView.AxSSTree_EventsRouter
        Assembly Version: 0.0.0.0
        Win32 Version: 0.0.0.0
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/Bin/AxSSActiveTreeView.AxSSTree_EventsRouter.dll
    Interop.UFBBInterfaces
        Assembly Version: 1.0.0.0
        Win32 Version: 1.0.0.0
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/Interop.UFBBInterfaces.DLL
    StdType
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.0.0
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/APP.Net/MSY/Bin/StdType.DLL
    Microsoft.VisualBasic.Compatibility
        Assembly Version: 7.0.5000.0
        Win32 Version: 7.10.3077
        CodeBase: file:///c:/windows/assembly/gac/microsoft.visualbasic.compatibility/7.0.5000.0__b03f5f7f11d50a3a/microsoft.visualbasic.compatibility.dll
    stdole
        Assembly Version: 7.0.3300.0
        Win32 Version: 7.00.9466
        CodeBase: file:///c:/windows/assembly/gac/stdole/7.0.3300.0__b03f5f7f11d50a3a/stdole.dll
    RFMobileReporting
        Assembly Version: 1.0.0.0
        Win32 Version: 5.11.0.40
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/RFMobileReporting.DLL
    AxInterop.SAPCalendar50
        Assembly Version: 1.1.0.0
        Win32 Version: 1.1.0.0
        CodeBase: file:///C:/Program%20Files/SAP/Mobile/Bin.NET/AxInterop.SAPCalendar50.DLL
    JIT Debugging **************
    To enable just in time (JIT) debugging, the config file for this
    application or machine (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.
    For example:
    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the machine
    rather than being handled by this dialog.
    Its urgent, Please help me out to rectify this error.
    Thanks & Regards,
    Venkata Ramana

    This seems like an error with standard SAP solution. I would suggest raising an OSS message and SAP should be able to help you out.
    Hope this helps.
    Regards,
    Kaushal

  • Programmed system maintenance

    I read that OSX has pre-programmed system maintenance and there is discussion on whether the computer should be turned off at night.
    Is there someplace I can check or reset my system maintenance?

    To check when your Periodic Maintenance Scripts, which I hope is what you want to know, open Terminal and type this exactly:
    ls -al /var/log/*.out
    Press Return
    and you should see three lines of info, one for each script: Daily, Weekly & Monthly. The date and time they were last run is in each line.
    To manually run the scripts open Terminal and type:
    sudo periodic daily weekly monthly
    Press return. You will be prompted for your Admin password and you need to type this into Terminal. Be warned, it might take a long time to run the scripts.
    For more info checkthe most excellent:
    The X Lab
    Hope this helps
    MacBook Pro 15"   Mac OS X (10.4.9)   1.83 GHz Intel Core Duo

  • How to find the system default scripts and prompts in UCCX 8.0

    Hello everyone,
    I have a bit of experience in UCCX 6.0 and just began to use UCCX 8.0. There's a question that where can I find the system default scripts and prompts in 8.0? In 6.0, I can find them in installing directory, but 8.0 is linux based so I can not do that in same way.
    Thanks.

    You can Login to CLI with either root access or remote user access and get default scripts by going to
    CD /opt/cisco/uccx/Scripts/system/default
    At this point you have to connect to ftp server and move these default script to yoru FTP server.
    I hope this helps

  • 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

  • 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

  • Can anyone help with a good system maintenance tool for ML

    Does any one have any suggestions for a good dependable all-in-one system maintenance tool for ML and is it straight forward and easy to use?
    Thanks in advance .....

    You really have no need for one. That said:
    Kappy's Personal Suggestions for OS X Maintenance
    For disk repairs use Disk Utility.  For situations DU cannot handle the best third-party utilities are: Disk Warrior;  DW only fixes problems with the disk directory, but most disk problems are caused by directory corruption; Disk Warrior 4.x is now Intel Mac compatible. Drive Genius provides additional tools not found in Disk Warrior.  Versions 1.5.1 and later are Intel Mac compatible.
    OS X performs certain maintenance functions that are scheduled to occur on a daily, weekly, or monthly period. The maintenance scripts run in the early AM only if the computer is turned on 24/7 (no sleep.)
    If you are using a pre-Leopard version of OS X, then an excellent solution is to download and install a shareware utility such as Macaroni, JAW PseudoAnacron, or Anacron that will automate the maintenance activity regardless of whether the computer is turned off or asleep.  Dependence upon third-party utilities to run the periodic maintenance scripts was significantly reduced since Tiger.  (These utilities have limited or no functionality with Snow Leopard, Lion, or Mountain Lion and should not be installed.)
    OS X automatically defragments files less than 20 MBs in size, so unless you have a disk full of very large files there's little need for defragmenting the hard drive. As for virus protection there are few if any such animals affecting OS X. You can protect the computer easily using the freeware Open Source virus protection software ClamXAV. Personally I would avoid most commercial anti-virus software because of their potential for causing problems. For more about malware see Macintosh Virus Guide.
    I would also recommend downloading a utility such as TinkerTool System, OnyX 2.4.3, or Cocktail 5.1.1 that you can use for periodic maintenance such as removing old log files and archives, clearing caches, etc.
    For emergency repairs install the freeware utility Applejack.  If you cannot start up in OS X, you may be able to start in single-user mode from which you can run Applejack to do a whole set of repair and maintenance routines from the command line.  Note that AppleJack 1.5 is required for Leopard. AppleJack 1.6 is compatible with Snow Leopard. (There is no confirmation that this version also works with Lion or later.)
    When you install any new system software or updates be sure to repair the hard drive and permissions beforehand. I also recommend booting into safe mode before doing system software updates.
    Get an external Firewire drive at least equal in size to the internal hard drive and make (and maintain) a bootable clone/backup. You can make a bootable clone using the Restore option of Disk Utility. You can also make and maintain clones with good backup software. My personal recommendations are (order is not significant):
      1. Carbon Copy Cloner.
      2. Data Backup
      3. Deja Vu
      4. SuperDuper!
      5. SyncTwoFolders
      6. Synk Pro
      7. Synk Standard
      8. Tri-Backup
    Visit The XLab FAQs and read the FAQs on maintenance, optimization, virus protection, and backup and restore.
    Always have a current backup before performing any system updates or upgrades.
    Additional suggestions will be found in
       1. Mac Maintenance Quick Assist,
       2. Mac OS X speed FAQ,
      3. Speeding up Macs,
      4. Macintosh OS X Routine Maintenance,
      5. Essential Mac Maintenance: Get set up,
      6. Essential Mac Maintenance: Rev up your routines,
      7. Maintaining OS X, 
      8. Five Mac maintenance myths,
      9. How to Speed up Macs, and
    10. Myths of required versus not required maintenance for Mac OS X.
    Referenced software can be found at CNet Downloads or MacUpdate.
    Be sure you have an adequate amount of RAM installed for the number of applications you run concurrently. Be sure you leave a minimum of 10% of the hard drive's capacity or 20 GBs, whichever is greater, as free space.

  • 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.

  • What is the best system maintenance software to use for a MBP??

    Hello everyone, I was formerly using Mac Tune-up for my Macbook Pro and it did an okay job but I am not sure what Mac software I should be using to keep my system clean while keeping it running at optimal performance. Turns-out I can no longer use Mac Tune-Up since I upgraded to Mavericks from Snow Leopard. Can anyone recommend to me the best system maintenance software to use for my MBP with Mavericks OS and where I can get it (a link or site URL)?  Thanks in advance!

    How to maintain a Mac
    1. Make two or more backups of all your files, keeping at least one off site at all times in case of disaster. One backup is not enough to be safe. Don’t back up your backups; all should be made directly from the original data. Don’t rely completely on any single backup method, such as Time Machine. If you get an indication that a backup has failed, don't ignore it.
    2. Keep your software up to date. In the App Store or Software Update preference pane (depending on the OS version), you can configure automatic notifications of updates to OS X and other Mac App Store products. Some third-party applications from other sources have a similar feature, if you don’t mind letting them phone home. Otherwise you have to check yourself on a regular basis.
    Keeping up to date is especially important for complex software that modifies the operating system, such as device drivers. Before installing any Apple update, you must check that all such modifications that you use are compatible. Incompatibility with third-party software is by far the most common cause of trouble with system updates.
    3. Don't install crapware, such as “themes,” "haxies," “add-ons,” “toolbars,” “enhancers," “optimizers,” “accelerators,” "boosters," “extenders,” “cleaners,” "doctors," "tune-ups," “defragmenters,” “firewalls,” "barriers," “guardians,” “defenders,” “protectors,” most “plugins,” commercial "virus scanners,” "disk tools," or "utilities." With very few exceptions, such stuff is useless or worse than useless. Above all, avoid any software that purports to change the look and feel of the user interface.
    It's not much of an exaggeration to say that the whole "utility" software industry for the Mac is a fraud on consumers. The most extreme examples are the "CleanMyMac" and “MacKeeper” scams, but there are many others.
    As a rule, the only software you should install is that which directly enables you to do the things you use a computer for, and doesn't change the way other software works.
    Safari extensions, and perhaps the equivalent for other web browsers, are a partial exception to the above rule. Most are safe, and they're easy to get rid of if they don't work. Some may cause the browser to crash or otherwise malfunction.  Some are malicious. Use with caution, and install only well-known extensions from relatively trustworthy sources, such as the Safari Extensions Gallery.
    Never install any third-party software unless you know how to uninstall it. Otherwise you may create problems that are very hard to solve. Do not rely on "utilities" such as "AppCleaner" and the like that purport to remove software.
    4. Don't install bad, conflicting, or unnecessary fonts. Whenever you install new fonts, use the validation feature of the built-in Font Book application to make sure the fonts aren't defective and don't conflict with each other or with others that you already have. See the built-in help and this support article for instructions. Deactivate or remove fonts that you don't really need to speed up application launching.
    5. Avoid malware. Malware is malicious software that circulates on the Internet. This kind of attack on OS X was once so rare that it was hardly a concern, but malware is now increasingly common, and increasingly dangerous.
    There is some built-in protection against downloading malware, but you can’t rely on it—the attackers are always at least one day ahead of the defense. You can’t rely on third-party protection either. What you can rely on is common-sense awareness—not paranoia, which only makes you more vulnerable.
    Never install software from an untrustworthy or unknown source. If in doubt, do some research. Any website that prompts you to install a “codec” or “plugin” that comes from the same site, or an unknown site, is untrustworthy. Software with a corporate brand, such as Adobe Flash Player, must come directly from the developer's website. No intermediary is acceptable, and don’t trust links unless you know how to parse them. Any file that is automatically downloaded from the web, without your having requested it, should go straight into the Trash. A web page that tells you that your computer has a “virus,” or that anything else is wrong with it, is a scam.
    In OS X 10.7.5 or later, downloaded applications and Installer packages that have not been digitally signed by a developer registered with Apple are blocked from loading by default. The block can be overridden, but think carefully before you do so.
    Because of recurring security issues in Java, it’s best to disable it in your web browsers, if it’s installed. Few websites have Java content nowadays, so you won’t be missing much. This action is mandatory if you’re running any version of OS X older than 10.6.8 with the latest Java update. Note: Java has nothing to do with JavaScript, despite the similar names. Don't install Java unless you're sure you need it. Most people don't.
    6. Don't fill up your disk/SSD. A common mistake is adding more and more large files to your home folder until you start to get warnings that you're out of space, which may be followed in short order by a startup failure. This is more prone to happen on the newer Macs that come with an internal SSD instead of the traditional hard drive. The drive can be very nearly full before you become aware of the problem.
    While it's not true that you should or must keep any particular percentage of space free, you should monitor your storage use and make sure you're not in immediate danger of using it up. According to Apple documentation, you need at least 9 GB of free space on the startup volume for normal operation.
    If storage space is running low, use a tool such as OmniDiskSweeper to explore the volume and find out what's taking up the most space. Move seldom-used large files to secondary storage.
    7. Relax, don’t do it. Besides the above, no routine maintenance is necessary or beneficial for the vast majority of users; specifically not “cleaning caches,” “zapping the PRAM,” "resetting the SMC," “rebuilding the directory,” "defragmenting the drive," “running periodic scripts,” “dumping logs,” "deleting temp files," “scanning for viruses,” "purging memory," "checking for bad blocks," "testing the hardware," or “repairing permissions.” Such measures are either completely pointless or are useful only for solving problems, not for prevention.
    To use a Mac effectively, you have to free yourself from the Windows mindset that every computer needs regular downtime maintenance such as "defragging" and "registry cleaning." Those concepts do not apply to the Mac platform. A well-made computing device is not something you should have to think about much. It should be an almost transparent medium through which you communicate, work, and play. If you want a machine that needs a lot of attention, use a PC.
    The very height of futility is running an expensive third-party application called “Disk Warrior” when nothing is wrong, or even when something is wrong and you have backups, which you must have. Disk Warrior is a data-salvage tool, not a maintenance tool, and you will never need it if your backups are adequate. Don’t waste money on it or anything like it.

  • Automated system maintenance timing

    iMac early 2008, 2GB RAM, 2.8GHz processor, HD 320 GB total, 225GB available, OS 10.6.8
    Whilst researching various causes for a Mac running slowly, I came across the statement that automated system maintenance procedures are scheduled by default to occur in "the early morning" hours, provided that the computer is running 24/7.  If I were to leave my computer on, it would go into sleep mode, as would I, during these early morning hours (assuming this to mean 1am etc.). Do the automated processes indeed occur in the 1am range and if so, will they happen if the computer is in sleep mode?

    Sorry that you feel that precision is not required in dealing with a modern
    operating system, and that the obsolete answer appears to fit your ideas
    on how to maintain a Mavericks system when compared to an older one.
    On more than one occasion, advice has been suggested without bearing.
    So be it with your interest in getting an answer that fits Mavericks 10.9
    since the factors that did change for this new system, are not addressed
    by the reply you sought to include as a correct response.
    And, I also gave you a bonus tip on a historically correct (to Mavericks)
    source of content that can be used with Mavericks for issues of a slow mac.
    Too bad I wasted some time and research, on your behalf. If I weren't
    working for free, I'd bill you double, and offer you to try a retail product.
    Your understanding of an answer has not been helpful to a resolution.
    However it does appear you did not read the link that supports my point:
    This is current to Mavericks, cited by Pondini as of now:
    On Snow Leopard 10.6.x and Later, if your Mac is powered-on but sleeping
    during those hours, the scripts will run shortly after it awakes.
    If you do not want current information on OS X 10.9.5, why ask and
    accept info that was OK prior to Lion 10.7.5 & think that's current??
    Is english your first language? I can try google translate if it helps...
    Good luck and happy computing!

  • 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.

  • 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.

Maybe you are looking for