cerowain

Of interest, this is the first day I saw an error from cron.daily occur and my system spontaneously rebooted last night. Coincidence? maybe. Just of interest.

Recently my system has started producing errors from cron, warning: Potentially dangerous mode on unraid-api: 0666 error: Ignoring unraid-api because it is writable by group or others. error: found error in file unraid-api, skipping warning: Potentially dangerous mode on unraid-api.patch: 0666 error: Ignoring unraid-api.patch because it is writable by group or others. error: found error in file unraid-api.patch, skipping Looking in logrotate.d I can see that the permissions are set to world writable on unraid-api and unraid-api.patch ls -l /etc/logrotate.d/unraid-api* -rw-rw-rw- 1 root root 165 Feb 10 09:31 /etc/logrotate.d/unraid-api -rw-rw-rw- 1 root root 408 Feb 10 09:31 /etc/logrotate.d/unraid-api.patch If I correct the permissions of the files it still produces errors because unraid.api.patch is a patch file, not a logrotate config file. Removing the app, manually cleaning up and reinstalling does not make any difference. For now I have removed the patch file and fixed the permissions on '/etc/logrotate.d/unraid-api' and my system is running fine, at least as far as I can tell.