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 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)