process nice level command line vs cron

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Command works at command line but not from cron

Oracle Linux 6. Trying to set up a simple monitoring of memory usage. This command does exactly what I want at the command line: echo $(date +%Y-%m-%d" "%H:%M:%S) $(grep PageTables /proc/meminfo) >> /home/oracle/meminfo.logBut when I put it in my crontab: * * * * * echo $(date +%Y-%m-%d"...

2. Shell Programming and Scripting

Issue in running a command line utility in CRON

Hi Everyone! I am facing an issue in running a command line utility from the CRON. This utility displays IPC statistics on UNIX message queues: The "queue name" and the "count" of messages in the queue. When running this utility from prompt, it will provide an output on the screen, like the...

3. Shell Programming and Scripting

Script runs in command-line fine but times out in CRON?

Hi, I have a script that seems to run to completion when in the command-line, but when it is run using the cron, it seems to time out. They both start and run fine, but on the CRON it stops prematurely. The script hits an API every few seconds and grabs data. Does anyone have any idea on...

4. Shell Programming and Scripting

s3cmd works on command line not on cron

Ubuntu 9.10 is my linux distro Based on forums they say that the problem is with environment . here is my case: login as user, then sudo -s using this command: s3cmd put file s3://bucket >>worked! now here is the simple script intended for testing: #! /bin/bash env >/tmp/cronjob.log...

5. UNIX for Dummies Questions & Answers

How to change the log level for cron?

Hello, I'm wondering how to change the log level to level 2 for cron without manually have to restart it with every boot. I didn't thing this would be hard to find, but searching has cause me to come up empty. System is Ubuntu Karmic/9.10 With thanks, Narnie

6. UNIX for Dummies Questions & Answers

Script through cron and command line

I have a script which runs fine through command line, but doesn't run through cron. There are some variables which are set by the .profile file which are used by the script. Is it that cront does not pick these variables. $/export/home/rahul/bin/createfile.sh >>...

7. UNIX for Dummies Questions & Answers

script works on command line, not in cron job

Hey there, I'm a total newbie unix guy here and just picking this stuff up. Have a very small script I put together that works fine from the command line but not once I put it in a cron job. Searched and found this thread and am wondering it it has something to do with setting variables, though the...

8. Programming

nice command and nice() system call

Hi I want to implement the nice command in the shell that I am building. I came to know that there is a corresponding nice() system call for the same. But since I will be forking different processes to run different commands typed on the command prompt, is there any way I can make a command...

9. UNIX for Advanced & Expert Users

Nice the process on user level

Hi there, I was wandering, if it is possible to nice set of process on user level. Say, I have user1,user2 if user1 spawns 12 process and user2 spwans 15 process, Is there a way can I change the priority of any process started by user1 to 5 and viz-a-viz user2 to 20 Thanks in advance

10. HP-UX

urgent help required on changing process priority using nice

Hi folks, Hope you can help me. I have a process that is currently running at nice 20 and need it to run faster (-10?). How do I change the process using nice? I have the process number and thought it would be along the lines of; nice -10 process_id but it doesn't seem to like that.

LEARN ABOUT OSF1

queuedefs

queuedefs(4)						     Kernel Interfaces Manual						      queuedefs(4)

NAME

       queuedefs - Queue description file for at, batch, and cron commands

DESCRIPTION

       The  queuedefs  file describes the characteristics of the queues managed by cron or specifies other characteristics for cron.  Each noncom-
       ment line in this file describes either one queue or a cron characteristic.  Each uncommented line should be in one of the  following  for-
       mats.

	    q.[njobj][nicen][nwaitw] max_jobs=mjobs log=lcode

       The  fields  in these lines are as follows: The name of the queue.  Defined queues are as follows: The default queue for jobs started by at
       The default queue for jobs started by batch The default queue for jobs run from a crontab file

	      Queues d to z are also available for local use.  The maximum number of jobs that can be run simultaneously in  the  queue;  if  more
	      than  njob jobs are ready to run, only the first njob jobs will be run.  The others will be initiated as currently running jobs ter-
	      minate.  The nice(1) value to give to all jobs in the queue that are not run with a user ID of superuser.  The number of seconds	to
	      wait  before rescheduling a job that was deferred because more than njob jobs were running in that queue, or because the system-wide
	      limit of jobs executing (max_jobs) has been reached.  The maximum number of active jobs from all queues that  may  run  at  any  one
	      time.  The default is 25 jobs.  Logging level of messages sent to a log file.  The default is 4.	Defined levels are as follows:

	      level-code   level

		  0	   None

		  1	   Low

		  2	   Medium

		  3	   High

		  4	   Full

       Lines beginning with # are comments, and are ignored.

EXAMPLES

       The  following  file specifies that the b queue, for batch jobs, can have up to 50 jobs running simultaneously; that those jobs will be run
       with a nice value of 20.  If a job cannot be run because too many other jobs are running, cron will wait 60 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.  If a job cannot be run
       because too many other jobs are running cron will wait 60 seconds before trying again to run it.  b.50j20n60w

       The following file specifies that a total of 25 active jobs will be allowed by cron over all the queues at any one time, and cron will  log
       all messages to the log file.  The last two lines are comments that are ignored.  max_jobs=25 log=4 # This is a comment # And so is this

FILES

       Main cron directory The default location for the queue description file.

RELATED INFORMATION

       Commands: at(1), cron(8), crontab(1), nice(1)
       delim off

																      queuedefs(4)

UNIX for Advanced & Expert Users