Different redirection behavior in BASH/Linux when run under cron vice login ??? Post: 302529475

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Very Strange Behavior for redirection

I have searched far and wide for an explanation for some odd behavior for output redirection and haven't come up with anything. A co-worker was working on old scripts which have run for years and embedded in their code were output redirects which worked for the script during execution and then...

2. Shell Programming and Scripting

General Q: how to run/schedule a php script from cron jobs maybe via bash from shell?

Status quo is, within a web application, which is coded completely in php (not by me, I dont know php), I have to fill out several fields, and execute it manually by clicking the "go" button in my browser, several times a day. Thats because: The script itself pulls data (textfiles) from a...

3. Shell Programming and Scripting

Behavior of Bad Script in Cron Job

Hi A Ksh script is deployed in a server and executed through cronjob. If one of the line in the middle of the script fails . Are the remaining lines executed ?

4. Linux

how to run cron tab job on linux

Dear All many hosting companies do have provision of cron tab settings In case a web hosting company do not have such facility can I run cron tab job

5. Shell Programming and Scripting

how do I run bash script using cron job

How do I run bash script using a cron job? I have tried to just write the path of the script, but that didn't work.

6. Red Hat

bash Linux login file

Hello all new to linux here... Please help,... when using Pico how can I open and edit the bash Linux login file (stored in your Linux root directory). I would like to add the new commands for items listed below. a) display contents of a directory => mycd b) display date and time =>...

7. Shell Programming and Scripting

Insane redirection behavior

Hi guys, I know computers don't misbehave. But I'm puzzled by what's happening right know in a script : I simplified the example to point out what seems weird to me. Don't try to find any sense to this stupid script. There are 10 rows in /tmp/tmp.txt i=0 tmpfile=/tmp/tmp.txt while...

8. Solaris

Run automated bash commands from sh login shell

I use plink.exe to automate remote commands that return data to Windows machines. This works well on newer servers running Red Hat since the commands were developed for bash and the designated user's login shell is bash. I need to also support older servers which are running Solaris 10 but the...

9. Shell Programming and Scripting

Different behavior between bash shell and bash script for cmd

So I'm trying to pass certain json elements as env vars and use them later on in a script. Sample json: JSON='{ "Element1": "file-123456", "Element2": "Name, of, company written in, a very weird way", "Element3": "path/to/some/file.txt", }' (part of the) script: for s...

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)