Results 1 to 4 of 4

Thread: cron

  1. #1
    Join Date
    Jan 2005
    Posts
    2,175

    cron

    from my daily corn emails:

    --------------------- Cron Begin ------------------------

    **Unmatched Entries**
    BAD FILE MODE (/etc/cron.d/bfd)
    BAD FILE MODE (/etc/cron.d/prm)
    BAD FILE MODE (/etc/cron.d/spri)
    BAD FILE MODE (/etc/cron.d/smart)
    BAD FILE MODE (/etc/cron.d/smart1)
    BAD FILE MODE (/etc/cron.d/clamav)

    ---------------------- Cron End -------------------------

    what does that mean?

  2. #2
    Join Date
    Sep 2002
    Location
    Top Secret
    Posts
    11,686
    Most likely this is because they are world +x . Try removing the executable bit on them. Inside of SSH
    Code:
    chmod a-x filename
    cron files do not necessarily need to be +x
    WHMCS Guru - WHMCS addons, management, support and more.
    WHMCS Notifications Extended - Add slack, hipchat, SMS, pushover to WHMCS !!
    Always looking for Linux, WHMCS, Support Desk work. PM for details

  3. #3
    Join Date
    Jan 2005
    Posts
    2,175
    I changed permissions and now this shows up on the daily cron email:

    --------------------- Cron Begin ------------------------

    **Unmatched Entries**
    BAD FILE MODE (/etc/cron.d/bfd)
    BAD FILE MODE (/etc/cron.d/prm)
    BAD FILE MODE (/etc/cron.d/spri)
    BAD FILE MODE (/etc/cron.d/smart)
    BAD FILE MODE (/etc/cron.d/smart1)
    BAD FILE MODE (/etc/cron.d/clamav)
    BAD FILE MODE (/etc/cron.d/bfd)
    BAD FILE MODE (/etc/cron.d/prm)
    BAD FILE MODE (/etc/cron.d/spri)
    BAD FILE MODE (/etc/cron.d/smart)
    BAD FILE MODE (/etc/cron.d/smart1)
    BAD FILE MODE (/etc/cron.d/clamav)

    ---------------------- Cron End -------------------------
    2 instances of each file..

  4. #4
    Join Date
    Jun 2003
    Location
    World Wide Web
    Posts
    581
    "File mode" means the file access permissions, and this error should be fixed by correcting the permissions on the crons

    Try the following:
    chmod 0644 /etc/cron.d/*

    Also make sure the permission of the /etc/cron.d/ folder is 755, and that the ownership(should be root) on the files are correct as well.
    SupportExpertz.com - the name says it all!
    Managed Cloud Servers
    Server Management and Monitoring
    24x7 outsourced customer support

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •