Cron and PAM Issues: Difference between revisions
From Leo's Notes
This page was last edited on 1 September 2019, at 04:45.
m Text replacement - "Category:Linux " to "Category:Linux{{Navbox Linux}} " |
m Text replacement - "{{Navbox Linux}} {{Navbox Linux}}" to "{{Navbox Linux}}" |
||
| Line 17: | Line 17: | ||
[[Category:Linux]]{{Navbox Linux}} | [[Category:Linux]]{{Navbox Linux}} | ||
Revision as of 04:45, 1 September 2019
When you try editing cron, you get a message similar to:
root@ws1:/etc/pam.d# crontab -e Permission denied You (root) are not allowed to access to (crontab) because of pam configuration.
/var/log/secure shows messages similar to:
Jul 25 14:07:17 ws1 crontab: pam_access(crond:account): access denied for user `root' from `cron'
To fix this issue, ensure that cron can be accessed by the user. In the case above, 'root' to 'cron'. Do this by editing /etc/security/access.conf with the following line at the top of the file:
+ : root : cron crond
See Also
- Access.conf