Sponsored Content
Full Discussion: crontab
Top Forums Shell Programming and Scripting crontab Post 19871 by yxiao on Wednesday 17th of April 2002 01:05:29 PM
Old 04-17-2002
Question Re

Thank you hugo. I did exectly the same way you show me. I got the following message:

apcore03(42): more /var/log/tcup_error.log
$ $ $ $ $ $ $ $ $ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > $ $ $ $ $ $ $ $ $ $ $ > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > $ $ $ $ $ $ $ $ $ $ $ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > $ $ $ $ $ $ $ $ $ $ $ > >
> > > > > > > > > > > > > > > > > > > > > > > > > > > $ $ $ $ $ $ $ $ $ $ $ > > > > > > > > > > > > > > > > > > > > > > > > > > > >
> $ $ $ $ $ $ $ $ $ $ $ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > $ $ $ $ $ $ $ $ $ $ $ > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > $ $ $ $ $ $ $ $ $ $ $ > > > > > > > > > > > > > > > > > > > > > > > > > > > > > $ $


apcore03(43): more /var/log/tcup.log
System is not configured properly, unable to proceed
System is not configured properly, unable to proceed
System is not configured properly, unable to proceed
System is not configured properly, unable to proceed
System is not configured properly, unable to proceed
System is not configured properly, unable to proceed
System is not configured properly, unable to proceed
System is not configured properly, unable to proceed



looks like something as it appeared before. Could you give me more help on that?

yun
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

crontab

Hi I have a shell script which works fine at the command line and does works in crontab also but does not send the output to mail as other scripts do by default. 10 1 * * * /export/home/test/report_script by default should send the output to mail but the script runs OK and the output... (1 Reply)
Discussion started by: run_time_error
1 Replies

2. UNIX for Dummies Questions & Answers

about crontab

dear all , does any one now how can i become sure that the crontab that i put was working successfully not by looking for thr result of the sheduled task but from a log for the crontab or something similar and i need to check that the cron i wrote is correct 00 15 * * 0,1,2,3,6... (2 Replies)
Discussion started by: habuzahra
2 Replies

3. UNIX for Dummies Questions & Answers

Crontab

How can I run "crontab" (parameters) every 6 hours on solaris machine? Thanks (1 Reply)
Discussion started by: gen4ik
1 Replies

4. Shell Programming and Scripting

help with crontab

i have a ksh script that creates messages in a temp directory and then sends them out using the sendmail command and i'm trying to set it up to run every night with crontab. So the basic gist of the script is #create temp dir and messages ... #loop through each message and send using sendmail... (3 Replies)
Discussion started by: bob122480
3 Replies

5. UNIX for Dummies Questions & Answers

crontab

hi all how to schedule the crontab file in unix? (2 Replies)
Discussion started by: ss4u
2 Replies

6. Shell Programming and Scripting

Using Crontab

Hi All, I've a shell script which calls a Sybase stored procedure to do some functionality. I want to schedule the running of this script by crontab. I'm using Solaris 5.8. When i executed the following command crontab -l i got the output as crontab: can't open your crontab file How... (10 Replies)
Discussion started by: sumesh.abraham
10 Replies

7. UNIX for Advanced & Expert Users

Crontab help

hi, I run a .sh file using crontab. I need to know the path of the file . Previously when I run the file alone , i used "pwd" but now when using crontab it gives the temp directory of the file. Is there any way I can find the absolute path of the file when i execute it ? Regards, Ranga (7 Replies)
Discussion started by: r_W213
7 Replies

8. UNIX for Advanced & Expert Users

Help regarding crontab

Dear All jobs are scheduled in crontab . To view this I use crontab -l . But suddenly today I am not able to see any jobs that is being scheduled in crontab. when I type crontab -l , I am seeing nothing.I am not logging through admin user(i dont have it).But I can schedule jobs through... (3 Replies)
Discussion started by: tkbharani
3 Replies

9. Shell Programming and Scripting

crontab

I have a crontab entry,but it is not working. Can anybody help me in this regard?? (2 Replies)
Discussion started by: Sourav_Paul
2 Replies

10. UNIX for Dummies Questions & Answers

at vs crontab

Hi, can someone explain the differences between using the at and crontab commands. When would you use one command over the other? TIA Dom (1 Reply)
Discussion started by: domburf69
1 Replies
qmail-log(5)							File Formats Manual						      qmail-log(5)

NAME
qmail-log - the qmail activity record DESCRIPTION
qmail-send prints a series of lines describing its activities. Each possible line is described below. STATUS
status: local l/L remote r/R ... qmail-send is waiting for l local deliveries and r remote deliveries. The concurrency limits are L and R. status: exiting qmail-send is done. FATAL PROBLEMS
alert: cannot start: ... qmail-send is unable to prepare itself for delivering messages; it is giving up. This normally indicates a serious configuration error, but it can be caused by a temporary lack of resources. alert: oh no! lost ... One of the other daemons has died. qmail-send will exit as soon as possible. SERIOUS PROBLEMS
alert: unable to append to bounce message... qmail-send is unable to record a permanent failure, usually because the disk is full. This is a very serious problem; qmail-send cannot proceed without recording the results. It will try again in ten seconds. alert: out of memory... qmail-send tried to allocate more memory and failed. It will try again in ten seconds. alert: unable to opendir... qmail-send is having trouble reading a file list from disk, usually because the system's file descriptor table is full, but possibly because permissions are set incorrectly. It will try again in ten seconds. alert: unable to switch back... qmail-send was sent SIGHUP, and it is unable to reenter the queue directory. This is a very serious problem; qmail-send cannot pro- ceed outside the queue directory. It will try again in ten seconds. alert: unable to reread... qmail-send was sent SIGHUP, but it is unable to read the new controls. It will continue operating with the original controls. MESSAGES
new msg m qmail-send is going to preprocess a queued message. The message number, m, is its disk inode number. After a message is removed from the queue, its number can be reused immediately. info msg m: bytes b from <s> qp q uid u Message m contains b bytes; its envelope sender is s; it was queued by a user with user ID u. q is a long-term queue identifier, the process ID of the qmail-queue that queued the message. bounce msg m qp q Message m had some delivery failures. The long-term queue identifier of the bounce (or double-bounce) message is q. triple bounce: discarding ... Message m had some delivery failures, but it is already a double-bounce message, so it must be thrown away. Triple-bounce messages do not exist. end msg m qmail-send is about to remove message m from the queue. DELIVERIES
starting delivery d: msg m to ... qmail-send is telling qmail-lspawn or qmail-rspawn to deliver message m to one recipient. The delivery number, d, starts at 1 and increases by 1 for each new delivery. delivery d: success: ... Delivery d was successful. delivery d: failure: ... Delivery d failed permanently. The message will bounce. delivery d: deferral: ... Delivery d failed temporarily. This recipient will be retried later. delivery d: report mangled, will defer There is a serious bug in qmail-lspawn or qmail-rspawn. This recipient will be retried later. WARNINGS
internal error: delivery report out of range qmail-lspawn or qmail-rspawn has supplied a report on a nonexistent delivery. This is a serious bug. qmail-clean unable to clean up ... For some reason qmail-clean is unable to remove the indicated file. It will try again later. trouble fsyncing ... qmail-send was unable to write to disk the results of preprocessing a queued message. It will try again later. trouble in select There is an operating system bug. trouble injecting bounce message... qmail-send was unable to queue a bounce message, usually because the disk is full. It will try again later. trouble marking ... qmail-send was unable to record the result of a successful or permanently unsuccessful delivery. This means that the delivery will be tried again later. trouble opening ... qmail-send was unable to open the list of local or remote recipients for a message. It will try again later. trouble reading ... Either qmail-send is unable to read a recipient list, or it is unable to read the envelope of a queued message, or it is out of mem- ory. Whatever it was doing, it will try again later. trouble writing to ... qmail-send was unable to preprocess a queued message, usually because the disk is full. It will try again later. unable to create ... qmail-send was unable to preprocess a queued message, usually because the disk is out of inodes. It will try again later. unable to open ... qmail-send is unable to read the envelope of a queued message for preprocessing. It will try again later. unable to start qmail-queue... qmail-send is unable to queue a bounce message, usually because the machine is almost out of memory. It will try again later. This can also be caused by incorrect settings of $QMAILQUEUE or errors in a program or script which $QMAILQUEUE points to. unable to stat ... qmail-send is unable to obtain information about a file that should exist. It will try again later. unable to unlink ... qmail-send is unable to remove a file. It will try again later. unable to utime ... qmail-send is about to exit, and it is unable to record on disk the next scheduled delivery time for a message. The message will be retried as soon as qmail-send is restarted. unknown record type in ... There is a serious bug in either qmail-queue or qmail-send. SEE ALSO
qmail-send(8) qmail-log(5)
All times are GMT -4. The time now is 07:29 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy