- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Permission to run cron jobs
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-17-2001 10:28 AM
тАО04-17-2001 10:28 AM
Permission to run cron jobs
/var/adm/cron/cron.allow only has read permissions, so would like to know if there's a different way than change permissions on the file and edit.
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-17-2001 10:39 AM
тАО04-17-2001 10:39 AM
Re: Permission to run cron jobs
Man the "crontab" manpage for more information.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-17-2001 10:42 AM
тАО04-17-2001 10:42 AM
Re: Permission to run cron jobs
The correct way to grant permissions to use 'cron' (or 'at') is to declare the user(name) in the ".allow" or ".deny" file. For instance, a valid /var/adm/cron/cron.allow file would have permissions of -r--r--r-- and would be owned by "bin:bin" and would contain lines looking like:
root
user1
user2
user3
This file would enable root, user1, user2 and user3 to schedule 'cron' tasks.
Thus, from the man pages for 'crontab':
You can execute crontab if your name appears in the file /var/adm/cron/cron.allow. If that file does not exist, you can use crontab if your name does not appear in the file /var/adm/cron/cron.deny. If only cron.deny exists and is empty, all users can use crontab. If neither file exists, only the root user can use crontab. The allow/deny files consist of one user name per line.
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-17-2001 10:44 AM
тАО04-17-2001 10:44 AM
Re: Permission to run cron jobs
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-17-2001 10:49 AM
тАО04-17-2001 10:49 AM
Re: Permission to run cron jobs
as it's r--r--r--, (and yes, owned by bin:bin), there's no way around but to change to be writable and add my user(s).
I understand the files (cron.deny, cron.allow), just thought there might be a different way (ie through SAM).
Thanks.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-17-2001 10:53 AM
тАО04-17-2001 10:53 AM
Re: Permission to run cron jobs
Rob
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-17-2001 10:55 AM
тАО04-17-2001 10:55 AM
Re: Permission to run cron jobs
You don't need to change ownership or permissions. Edit the appropriate file with 'vi' and use "wq!" [instead of merely "wq"] to override the readonly permission.
...JRF...