• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Cronjob Hell 8.1.0

D

deeltje

Guest
Maybe not the brightest thread ever, so i hope you all can forgive me for that.

I've upgrade my Debian PLESK server from 8.0.1 to 8.1.0, as you all wil know; statistics ain't working anymore (they've deleted it out of the cronjobs), i know how to manually update the stats (opt/psa/admin/sbin/statistics) but i like to know how to build a proper cronjob for it.

I've checked my scheduled tasks in PLESK and found a massive overload of pure nonsense cronjob-directories?:

alias/backup/bin/bind/daemon/Debian-exim/drweb/games/gnats/identd/irc/list/lp/mail/man/mysql/news/nobody/popuser/postgres/proxy/psaadm/psaftp/qmaild/qmaill/qmailp/qmailq/qmailr/qmails/root/sshd/sync/sys/uucp/www-date

I thought the only one that was used, was the 'root'... as you have to be root to do imported cronjobs in the first place.

I used to have 1 list of cronjobs which did exactly what it said it should do. Now i have a huge amount of directories and most of them are empty!

Is there anyone that can tell me which directories can be deleted to clean up the place and what cronjobs are needed to run a clean PLESK, cause i've really lost it this time...
 
Back
Top