Stoping & starting the cron daemon


 
Thread Tools Search this Thread
Operating Systems SCO Stoping & starting the cron daemon
# 1  
Old 04-30-2007
Stoping & starting the cron daemon

Hi

We are running SCO ver 5. Recently the cron daemon stopped running on its own. How do I find out why? How do I restart/stop it?

I typed cron but it didn't work. Will rebooting it do the trick or can I manually start and stop the cron daemon?

Please help.

Thanks & Regards.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. Fedora

cron daemon name

Hi All, Please tell me which daemon is responsible for start and stop the crontab. Please tell me the location where it resides in Linux platform. Sindu. (2 Replies)
Discussion started by: indira_s
2 Replies

2. UNIX for Dummies Questions & Answers

Cron Daemon and alert

I am not system admin on Unix or Linux server. I am Oracle DBA to work on these operating systems. On our Oracle Linux 5.8 box, it always pump up the alert message like this: Cron Daemon /bin/sh: /opt/oracle/product/middleware/agent11g/ccr/bin/emCCR: No such file or directory Please help... (2 Replies)
Discussion started by: duke0001
2 Replies

3. IP Networking

UDP Server/Daemon for receiving & acknowledging data

I'm looking for a couple high level pointers to writing a UDP server that will be acknowledging data at a rate of approximately twelve packets every second and will be running on and older but more or less dedicated Solaris 9 box. Acknowledging the data packets is relatively simple, after... (2 Replies)
Discussion started by: allbread
2 Replies

4. Solaris

Mail is not sent by cron daemon

Hello All, In SunOS 10, I have some cron jobs and it is running fine but the cron job outputs are not mailing to any acount of the system. In other OS, we have option like MAILTO variable or /dev/null to disable but in Sun I have no idea how it is disabled by default and how do I... (13 Replies)
Discussion started by: Tlogine
13 Replies

5. UNIX for Dummies Questions & Answers

how execute/visit a site using the cron daemon?

hi, i need to execute/visit a site to check if the site is up or not i have a server that have cron shedule that can execute a php file now how can i execute/visite a site using the same way as i execute a file? thanks a lot for your help :) (1 Reply)
Discussion started by: jasonx22
1 Replies

6. Shell Programming and Scripting

How to starting process as daemon using ssh command?

Hello, I need to run a command on remote Linux using the ssh command from my local machine. I am able to execute the command on remote machine using ssh but it's behaving strangely. The command is supposed to start a daemon process on remote linux box and the control should return back to me... (5 Replies)
Discussion started by: nitinshukla
5 Replies

7. SCO

Stoping & starting the cron

Hi We are running SCO ver 5. Recently the cron daemon stopped running on its own. How do I find out why? How do I restart/stop it? I typed cron but it didn't work. Will rebooting it do the trick or can I manually start and stop the cron daemon? Please help. Thanks & Regards. (9 Replies)
Discussion started by: othman
9 Replies

8. UNIX for Dummies Questions & Answers

Starting MySQL daemon

I'm running a FreedBSD server with mysql 4.1. When I start mysqld via the command: # /usr/local/bin/safe_mysqld --user=mysql it starts the mysql db (I know because the websites are running off of it) but does not return to a prompt, it will let me type but will not respond unless I restart... (15 Replies)
Discussion started by: unispace
15 Replies

9. UNIX for Dummies Questions & Answers

Cron daemon

I ve a problem with the cron daemon. i ve a process that sends many mail, and full my /var FS i don t want to write a script that would clean its mails i want to know if it would be possible to stop the cron daemon sending mails only for that specific process. Thanks !:D (3 Replies)
Discussion started by: karine
3 Replies

10. UNIX for Dummies Questions & Answers

Cron Daemon

Hey all, I'm running Mandrake 7.2 with several of the development/server tools loaded and operating. One problem I'm having is that I keep getting emails from the "Cron Daemon". They all say: touch: /var/log/news/nntpsend.log: Permission denied chmod: same as above /usr/bin/nntpsend: ... (2 Replies)
Discussion started by: ober5861
2 Replies
Login or Register to Ask a Question
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)