Sponsored Content
Full Discussion: sys cron not running
Top Forums UNIX for Advanced & Expert Users sys cron not running Post 302565783 by vivek.goel.piet on Tuesday 18th of October 2011 06:16:07 PM
Old 10-18-2011
sys cron not running

Hi all,
I have a solris 10 machine and i am facing some strange issues.
My sys user cron is not executing.
Can any one help on this issue?
Code:
root@antsdp1b>svcs -a|grep -i cron
online          1:08:55 svc:/system/cron:default
root@antsdp1b>

the cron process is also running. but whatever i schedule in the sys user cron, it is not executing. However the same thing was working earlier.

Regards
Vivek
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

not running in cron

I have written a shell script and when i run it from shell prompt it runs fine but in the cron it only runs partially. That means cron is working fine. there is a command which i am using in the script which doesn't run at all. That comman uses different user privileges like ptadmin i am not... (4 Replies)
Discussion started by: ajnabi
4 Replies

2. Shell Programming and Scripting

running cron jobs

Hi, I'm new to cron and I would like to know if this cron entry looks right. Every monday to friday, at 9:15 AM execute the script called done_att.sh Every monday to friday, at 3:15 PM execute the script called start_att.sh 15 09 * * /u54/jobs/done_att.sh 45 15 * *... (1 Reply)
Discussion started by: ted
1 Replies

3. Solaris

[need help] about after running sys-unconfig and config network for v890

hi expert, i had do sys-unconfig for my v890 sparc and had config for eri0 network interface and hostname but after the server bring up i got this error messages : NIS domainname is www.USSDGmdn-4.com starting rpc services: rpcbind keyserv done. Setting netmask of eri0 to 255.255.255.0... (5 Replies)
Discussion started by: bucci
5 Replies

4. Shell Programming and Scripting

Cron not running .. please help

i have a simple script that ftp a file out, manually running it works fine. #!/bin/sh ftp 152.226.69.48 << cmd bin get applicant_vw.txt quit cmd but when I cron it, 14 9 * * * /opt/home/XXX/XXX/dailyjob.sh > /opt/home/XXX/XXX/cronlog.txt seems that it was executed because i can... (2 Replies)
Discussion started by: beisaikong
2 Replies

5. UNIX for Advanced & Expert Users

Cron not running

Hello All, I have installed a few crons on a machine. But for some reason the crons just don't run. I have checked the permissions on the files and also restarted the cron daemon. But it doesn't seem ti help. Can anyone suggest any other things I can do to get it running again? Regards,... (6 Replies)
Discussion started by: garric
6 Replies

6. UNIX for Advanced & Expert Users

SYS CRONJOB just not running...

I'm trying to run "SAR -i 60" under #/var/spool/cron/crontabs/SYS 0,10,20,30,40,50 0-6 sh -c "/usr/lib/sa/sa1 60 10 &" 55 23 * 0-6 /usr/lib/sa/sa2 -i 900 -A machine is not running above cron job under "sys" at all. This suppose to run every minutes and all time in 24 hours. When day... (6 Replies)
Discussion started by: deal732
6 Replies

7. Solaris

Cron job running even after cron is removed

Hi , I have removed a cron for particular user , but cron job seems to be running even after the cron entry is removed. The purpose of the cron was to sendmail to user ( it uses mailx utility ) I have restarted cron and sendmail service still user is getting mail alerts from the cron job. And... (4 Replies)
Discussion started by: chidori
4 Replies

8. Shell Programming and Scripting

Script not running in cron

Hi All, I have a script which is running fine while triggered manually, However if I placed in crontab it throwing an error. #!/usr/bin/ksh set -vx lc=1 st_date=$(`date "+%Y%m%d"`) LOGFILE=/home/transfer.log.$st_date file="/home/OM_WF.log.$st_date" Manual run - lc=1 + lc=1... (4 Replies)
Discussion started by: nag_sathi
4 Replies

9. Windows & DOS: Issues & Discussions

Sys headers - running Linux C code on windows

Hi All, I wanted to run a small socket application written in C on windows. The code was written for GNU/linux..the compiler on windows CodeBlocks complains about the sys headers. is there an equivalent for windows ? (4 Replies)
Discussion started by: coolatt
4 Replies

10. Programming

Interactive Python 3.5+ sys.stdout.write() AND sys.stderr.write() bug?

(Apologies for any typos.) OSX 10.12.3 AND Windows 10. This is for the serious Python experts on at least 3.5.x and above... In script format sys.stdout.write() AND sys.stderr.write() seems to work correctly. Have I found a serious bug in the interactive sys.stdout.write() AND... (2 Replies)
Discussion started by: wisecracker
2 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 09:31 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy