GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- cron output question
Operating System - HP-UX
1855348
Members
6931
Online
104109
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp
Knowledge Base
Discussions
Forums
Discussions
back
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
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
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
06-04-2002 11:38 PM
06-04-2002 11:38 PM
cron output question
Hello,
Here is a part of my cron
00,15,30,45 * * * * /users/killproc
The script is ok
But when it's start the standard output go to root's mail .(lot of messages !!)
Start of script:
# Killproc
. /users/explara/env/exploit.env #env exploit
. /users/explara/env/cmxAP.env # env cimix
#
FOUT=/users/explara/log/killproc.log
exec 1>$FOUT 2>&1
#
...
Thanks.
Here is a part of my cron
00,15,30,45 * * * * /users/killproc
The script is ok
But when it's start the standard output go to root's mail .(lot of messages !!)
Start of script:
# Killproc
. /users/explara/env/exploit.env #env exploit
. /users/explara/env/cmxAP.env # env cimix
#
FOUT=/users/explara/log/killproc.log
exec 1>$FOUT 2>&1
#
...
Thanks.
Bonjour
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-04-2002 11:47 PM
06-04-2002 11:47 PM
Re: cron output question
Hi Malosse,
the standard output of cron is the mail account of the user, who started the job. If you don't want this, you have to redirect your output, for example into a logfile:
00,15 * * * * /usr/killproc > /path_to_logfile/logfile 2>/path_to_errorfile/errorlogfile
Allways stay on the bright side of life!
Peter
the standard output of cron is the mail account of the user, who started the job. If you don't want this, you have to redirect your output, for example into a logfile:
00,15 * * * * /usr/killproc > /path_to_logfile/logfile 2>/path_to_errorfile/errorlogfile
Allways stay on the bright side of life!
Peter
I'm learning here as well as helping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-04-2002 11:48 PM
06-04-2002 11:48 PM
Re: cron output question
You must to redirect the output of the script in crontab.
Otherwise, the standard output and error output is e-mailed to user.
Otherwise, the standard output and error output is e-mailed to user.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-04-2002 11:52 PM
06-04-2002 11:52 PM
Re: cron output question
Hi,
If you don't want the output, redirect the STDOUT and STDERR to /dev/null in your cron job:
00,15,30,45 * * * * /users/killproc >/dev/null 2>&1
Hope this helps. Regards.
Steven Sim Kok Leong
If you don't want the output, redirect the STDOUT and STDERR to /dev/null in your cron job:
00,15,30,45 * * * * /users/killproc >/dev/null 2>&1
Hope this helps. Regards.
Steven Sim Kok Leong
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
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP