10-07-2012
First thing I'd say, is it the tar creation or the ftp that fails to run under cron?
Where are you expecting the cron job to get the ftp login credentials from?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I am trying to run a series of perl scripts at different times using crontab under solaris. The scripts that i am using require some specific environment variables to be specified for database functionality, but i would also like it that i can specify a few global variables for output locations.
... (8 Replies)
Discussion started by: Smitty McSmith
8 Replies
2. Solaris
Is it possible to use environment variables within cron jobs. I am using a cron job to run a c program at regular intervals. The C program uses a library and i have set the library path in the LD_LIBRARY_PATH environment variable. But when i ran the job i got the error library not found!! Any... (1 Reply)
Discussion started by: atheek
1 Replies
3. UNIX for Dummies Questions & Answers
Hello,
I am using Solaris 10.0 and defining PATH on command line by the following way:
#export PATH=/usr/sfw/bin....
...but after restart, Solaris forgets what I defined and I need to re-define the same PATH environment.
I want to to get defined my PATH environment during booting... (10 Replies)
Discussion started by: XNOR
10 Replies
4. Shell Programming and Scripting
Hi,
In Cron file i'm using username and password hard-coded and now i wann to use environmental veraiables in cron file.
But Could you please guide me how to use these environmental variables in cron file ?
Thanks,
Shyamu.A (4 Replies)
Discussion started by: shyamu544
4 Replies
5. Solaris
where do you set environment variables for cron jobs?
I have a feeling it would ignore ~/.bashrc ?
thanks. (2 Replies)
Discussion started by: orange47
2 Replies
6. Shell Programming and Scripting
Hi everyone,
I wrote a script that is supposed to be run by cron on a daily basis. It works just fine if I run it manually, but due to a lack of environment variables (which are available during my user session but not when cron runs the script) it keeps failing to run successfully.
Here's the... (2 Replies)
Discussion started by: gacanepa
2 Replies
7. Solaris
Hi Friends,
Good day!
This is my first post in this forum :)
In my company we have a requirement for back up application specific files and directories .We have around 40+ application which needs to be backed up .All these applications are running on Solaris 10 enviornment.
Is... (8 Replies)
Discussion started by: Abilash_KP
8 Replies
8. Solaris
Hi
I need to know what is the unique identifier for solaris OS even in a virtualized environment?
Will "Using Universally Unique Identifiers" help?
virtinfo -u
Domain UUID: 9db53f14-f27c-69f9-a71c-8926e9ae6eed
If Not, then let me know?
Would appreciate if similar UNIQUE id (of... (3 Replies)
Discussion started by: skyineyes
3 Replies
9. Solaris
Hi Experts,
Please help me on this.
I've a print environment using NIS in Solaris 10.
Recently we have new JDE environment which using Solaris 11 OS, and found that we can't use NIS anymore. So only the option is using CUPS.
How do we integrate this print environment for both Solaris 10... (9 Replies)
Discussion started by: srigias
9 Replies
10. Shell Programming and Scripting
Hi everybody ,
when I run a script from the command line it works but returns a failure if I run it from crontab.
Basically I wanted to send a file to hdfs,
I thought it was related to the fact that crontab do not know the path to hdfs so I put the full path but it still does not work: here... (1 Reply)
Discussion started by: beautymind
1 Replies
LEARN ABOUT X11R4
queuedefs
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)