09-09-2008
Looks like the error was due to a corrupt privileges table. After resorting the table everything seems to work now. It's just odd that it wouldn't work on cron.
Thanks to everyone for the suggestions.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
This is my first post!! I really hope this question hasn't been asked a thousand times before(I'll bet it has).
Anyway, here it is. I am new to the UNIX world by the way so forgive my ignorance. OK, whenever I write code on my windows machine and then try to port it over to UNIX I always get... (3 Replies)
Discussion started by: Jubba
3 Replies
2. UNIX for Dummies Questions & Answers
Hello Forum,
I am having an odd occurence. When i do a su in a terminal or console session, I am able get authenticated as superuser without using the full or correct root password. Anyone have any idea?
-AJ (4 Replies)
Discussion started by: jacobsa
4 Replies
3. UNIX for Dummies Questions & Answers
I am using smartFTP client on my windows machine to connect to a linux box of mine (different location) to download some large files 100+meg. The linux box is running vsftp.
After several minutes of downloading, the connection suddenly dies, and I cannot reconnect to the box via FTP using ANY... (7 Replies)
Discussion started by: Spetnik
7 Replies
4. AIX
Hi,
I have a strange problem. we're trying to connect an IBM pseries, to a Brocade switch, for SAN acess, using a badged emulex card, (IBM FC6239) WE can configure the device to see the fabric. The only problem we have is that the Brocade sees the HBA as storage, and not as a HBA.
We've zoned... (1 Reply)
Discussion started by: praxis22
1 Replies
5. UNIX for Dummies Questions & Answers
I discovered that where 'tr -s' works as expected on grepped input, it appears to completely fail on dig results.
I am not sure if this is because of some sort of non posix compliancy, or what.
Here is what I did:
The command below works as expected, squeezing all repeated spaces to a single... (3 Replies)
Discussion started by: bdmeyersc
3 Replies
6. Programming
I've been going through a java tutorial, and ran across some strangeness in this small example...
class SqrRoot {
public static void main(String args) {
double num,sroot,rerr,resquare;
for(num = 1.0; num < 100.0; num++) {
sroot = Math.sqrt(num);
... (1 Reply)
Discussion started by: Trones
1 Replies
7. Solaris
All,
I'm baffled by some sort behavior on SunOS 5.10 and looking for guidance.
Running the command:
sort -t'|' -k5,5 -k7,7 -k1,1 -k2,2 -k3,3 -k6,6 -k8,8 test
Against the file "test":
thirdA||||first||second|Data
thirdB||||first||second|
thirdC||||first||second|Data... (11 Replies)
Discussion started by: effigy
11 Replies
8. UNIX for Dummies Questions & Answers
I have to apologize for my ignorance so this question is probably stupid.
How does awk process a file? Does it read from top of input file to end of file going line by line?
Yoda helped me create an awk script that helps me parse the named.conf file and output it into a .csv file but when... (8 Replies)
Discussion started by: djzah
8 Replies
9. Shell Programming and Scripting
Hi all, I'm trying to use bash to create a basic parser for some text, because basic grep/sed/awk have all my needs covered.
So, I'm creating the chain of grep/sed I need and trying the execute that on the data I gather.
The problem is, it's not working as it does when hardcoded.
e.g.
... (3 Replies)
Discussion started by: beomagi
3 Replies
LEARN ABOUT XFREE86
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)