Sponsored Content
Operating Systems Solaris Created cron.allow file and now email fails Post 302088748 by citrowske on Thursday 14th of September 2006 09:15:44 AM
Old 09-14-2006
Created cron.allow file and now email fails

Getting ready for Sarbanes Oxley and I was told that I need to create a cron.allow file for the box so that only specified users can create cron jobs. That was easy enough, and I put in all the accounts that had scheduled cron jobs such as:
root
lp
My oracle account
A couple of programmer accounts.

I set that up yesterday but I noticed today that all of the schedule jobs ran, but the jobs that sent e-mail for status reporting failed. Is cron somehow related to email. Do I need to set up some type of system user in the cron.allow for e-mail to work?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

email when cron fails

I have a cronjob scheduled to run everyday. How can I obtain an email if and only if the cronjob fails? I am using Sun Solaris (ksh). :rolleyes: (7 Replies)
Discussion started by: inpavan
7 Replies

2. Forum Support Area for Unregistered Users & Account Problems

now 4 users created, still no email

I'm sorry for being an annoyance. I did read in another post that anyone who gives a proper email address will receive a confirmation. Well, I have created 4 accounts to no avail. Who knows, maybe I did mistype my email in one of them (twice since we have to reconfirm and with the same typo),... (3 Replies)
Discussion started by: seaghan
3 Replies

3. Shell Programming and Scripting

cron entry fails.

Hello, I have added the following entry in my cron file: * * * * * . /home/texprd/.profile>/dev/null 2>&1; echo "test" >> /home/texprd/test.log 2>&1 The cron fails ie the added command fails to append "test" in the test.log file. However if I run the command manually from the shell... (3 Replies)
Discussion started by: mahive
3 Replies

4. Shell Programming and Scripting

isql output file not created while running it through cron

#!/bin/ksh file="/pkgs/roots/scripts/ISQL_op.txt" isql -H 11.11.11.111:1111 -U myUser -P myPwd -o $file << eof go select * from Table1 go eof my cron entry 00 08 03 11 * /pkgs/roots/scripts/testc.ksh file permission of the script is correct, i have used absolute path everywhere. ... (2 Replies)
Discussion started by: vikram3.r
2 Replies

5. Shell Programming and Scripting

Send a file through email using cron as an attachment

Hi All, I want to send a file as an attachment through cron job.Is this possible using cronjob nd if it i, can you please let me know how to do this? Thanks (2 Replies)
Discussion started by: NARESH1302
2 Replies

6. UNIX for Advanced & Expert Users

Cron job fails every now and then.

I added a shell script to cron that executes every 5-15 minutes. It's used to monitor multiple environments, so it has to ssh to each machine to check the status of that machine. Sometimes, I may have more than one instance of this script running at the same time. So, here's my problem. I've... (2 Replies)
Discussion started by: mrwatkin
2 Replies

7. UNIX for Dummies Questions & Answers

cron job for the created shell script

Hi am newbie for unix shell.. how to create a cron job for my already created shell script.:confused: Thanks! (1 Reply)
Discussion started by: vidhyaS
1 Replies

8. BSD

X -configure fails on NetBSD: Number of created screens does not ...

Hello, my system is NetBSD 6.1.5 on AMD64. 'X -configure' prints following message: "Number of created screens does not match number of detected devices" Only motherboard's on-board graphic is using. xorg.conf.new Section "ServerLayout" Identifier "X.org Configured" ... (7 Replies)
Discussion started by: temp-usr
7 Replies

9. Shell Programming and Scripting

How to send a file in UNIX through email which is created only 15 minutes before the current time?

I wanted to send an email to the client whenever there is failed record created in a /feed/HR-76/failed folder after processing of feed file. I can find out with the help of below script that what is the new file created but that file didn't make just 15 minutes before. ... (1 Reply)
Discussion started by: puneetkhullar
1 Replies

10. UNIX for Advanced & Expert Users

Email notifications when new directory is created.

Hi Team, Can you please help me on this, I want to receive an email notification whenever new directory is created under the path /home/data. Am using bash shell. We are not sure about the directory name. When ever any new directory is created, scrip should monitor for new directory and... (1 Reply)
Discussion started by: Dhivyaprabha
1 Replies
queuedefs(4)							   File Formats 						      queuedefs(4)

NAME
queuedefs - queue description file for at, batch, and cron SYNOPSIS
/etc/cron.d/queuedefs DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue. The format of the lines are as follows: q.[njobj][nicen][nwaitw] The fields in this line are: q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see at(1)); c is the default queue for jobs run from a crontab(1) file. njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100. nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2. nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's queue, or because the system-wide limit of jobs executing has been reached. The default value is 60. Lines beginning with # are comments, and are ignored. EXAMPLES
Example 1: A sample file. # # a.4j1n b.2j2n90w This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron. SEE ALSO
at(1), crontab(1), nice(1), cron(1M) SunOS 5.10 1 Mar 1994 queuedefs(4)
All times are GMT -4. The time now is 02:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy