HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Default for a cron scheduled process
Operating System - HP-UX
1825793
Members
2229
Online
109687
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- 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
12-03-2000 03:34 PM
12-03-2000 03:34 PM
I am having a problem with a cron scheduled job that fires off processes (C and FORTRAN) which creates directories and files. The permissions of the resulting files and directories do not have the permissions that I expect them to have. The processes do not set the permissions on each created file or directory, so how does a cron scheduled process determine the FMC mask it will use for a default? Any assistance is greatly appreciated.
TR.a
TR.a
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2000 05:25 PM
12-03-2000 05:25 PM
Solution
Tim:
I suspect that you normally establish your 'umask' in your '.profile'. Cron only supplies default environmental values for your HOME, LOGNAME, PATH and SHELL. You must either source your .profile or define the your variables "of interest" in the script that cron executes. In your case, it sounds like simply setting the 'umask' in the cron'ed script is the appropriate choice.
...JRF...
I suspect that you normally establish your 'umask' in your '.profile'. Cron only supplies default environmental values for your HOME, LOGNAME, PATH and SHELL. You must either source your .profile or define the your variables "of interest" in the script that cron executes. In your case, it sounds like simply setting the 'umask' in the cron'ed script is the appropriate choice.
...JRF...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-03-2000 05:47 PM
12-03-2000 05:47 PM
Re: Default for a cron scheduled process
If for some reason, you cannot or do not want to edit the scripts that cron fires off, you can source your .profile within the crontab entry with normal command stacking.
e.g.
00 03 * * 1-5 . .profile; my_fortran_program
e.g.
00 03 * * 1-5 . .profile; my_fortran_program
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP