Sponsored Content
Full Discussion: Code trouble
Top Forums Programming Code trouble Post 303011237 by Corona688 on Monday 15th of January 2018 12:55:47 PM
Old 01-15-2018
You probably didn't put enough options into pow. Please show the exact code you used.
 

10 More Discussions You Might Find Interesting

1. UNIX Desktop Questions & Answers

trouble

Hello, The system reboots in single user mode what command to use to bring the system up regularly?? I get INIT: cannot create /var/adm/utmpx Type control -d to proceede with a normal startup or give root passwd for system maintaince. either way i don't have a change and ... (1 Reply)
Discussion started by: awk
1 Replies

2. What is on Your Mind?

The trouble with...

Welcome to "The trouble with...." with your host, ZazzyBob. Todays offering - "The trouble with letting other people host your website" I use a certain web hosting service, who shall of course remain nameless here. They are running PHP 4.3.10 I decide to write a script to test their PHP... (6 Replies)
Discussion started by: zazzybob
6 Replies

3. UNIX for Dummies Questions & Answers

The trouble about SU ...

Hi all, having read lots of posts about SU I don't quiet understand this : I'm doing regular backups of my database (u betta do) and therefore use su - username -c "sqlscript special data_base" in a unixscript which is even using cron. (yep!) Now I need some other script, still with this... (4 Replies)
Discussion started by: nulnul7
4 Replies

4. Solaris

Trouble with tr

I'm not sure where to post this but it's happening on a SunOS 5.8 server so I'll try here. I've discovered some unexpected behavior when using tr. For example: echo a | tr Z echo b | tr a echo a | tr B echo a | tr B echo a | tr A (8 Replies)
Discussion started by: Mike@Work
8 Replies

5. UNIX for Dummies Questions & Answers

X trouble

Hi there, I'm new to unix-environments. I'm richard, and i'm mostly a web-developer, under php. I've done work in unix env before, but never had my own. Today, I've got debian 3.1 r4 from the official site, and i've attempted to install it twice. I installed it initially as "Desktop... (0 Replies)
Discussion started by: izua
0 Replies

6. UNIX for Dummies Questions & Answers

Little Trouble Understanding some code...

Couple of questions as I try to decipher someones code who left... What would something coded like this do? IFS=: grep FIELD1 /Path/Path2/Param.fle | read LBL1 LBL2 USRID EADR SUBJ SERVERNAME CFGTBL DIR ERR=0 Param.fle contents.. FIELD1:FEI::FIELD2:dATAFIELD BATCH:MAIN SERVER......etc.. (2 Replies)
Discussion started by: NycUnxer
2 Replies

7. Programming

Trouble with C

Hey, i am having a problem First, i know java well and i have used C++ on occasion so i thought i would be able to deal with a class where they program in C. unfortunately i have hit some speed bumps that i am having problems. Here is my problem: I have a structure cache_t in the sample... (0 Replies)
Discussion started by: zephoid
0 Replies

8. Shell Programming and Scripting

while condition with trouble

Hello! i have a llittle missunderstanding with a script and maybe you can explain where is the mistake. in the first place a have this script that is working just fine ... read -p "enter the name of the instance: " instance while ; .... but if i change the second condition with -z "`grep... (2 Replies)
Discussion started by: doro
2 Replies

9. Shell Programming and Scripting

Trouble executing piped shell commands in perl code

I am trying to execute a piped combination of shell commands inside a perl program. However, it is not working as desired. This is my program, i am trying to print only filenames from the output of ls -l $ cat list_test #!/usr/bin/perl -w use strict; my $count=0; my @list=`ls -l|awk... (4 Replies)
Discussion started by: sam05121988
4 Replies

10. Solaris

Trouble with backup

At work I am running a solaris 10 server with a ZFS filesystem. I am unfortunately not a solaris expert by any stretch of the imagination, and the relative difficulty in doing what I consider to be a super basic operation using solaris is driving me insane. It is my job to figure out some way... (2 Replies)
Discussion started by: dreiak
2 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 11:59 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy