Sponsored Content
Full Discussion: unable to list the files
Top Forums UNIX for Dummies Questions & Answers unable to list the files Post 302273496 by risshanth on Monday 5th of January 2009 12:34:20 AM
Old 01-05-2009
unable to list the files

Hi,

$ ls -ltr *.log

Error :
argument list too long: ls

How to rectify this ?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Unable to get initial list of users

I cannot access the Accounts Manager facility when using SCO (F2 Screen) or scoadmin from the Command prompt. when using System Administration screen the Error "Unable to get initial list of users" is given. (0 Replies)
Discussion started by: Waitstejo
0 Replies

2. UNIX for Dummies Questions & Answers

I'm unable to run Keyed List commands(in ubuntu's terminal and Evolane Tcl Engine)

I'm trying to run these commands (keylset,keylget) but i keep getting a error message "invalid command name "keylset"". I've tried running it on both ubuntu's terminal and also Evolane Tcl Engine. Any idea what could be the problem? (1 Reply)
Discussion started by: abe171
1 Replies

3. Shell Programming and Scripting

unable to put cc list in mailx

Hi, I am using mailx command to send mail. But unable to use -c option to send mails by cc list. eg. ..mailx -s "subject" -c "CCLIST" "TOLIST" Its showing " illegal option -- c" I am using HP UX. Can anybody help me out. Thanks in advance..! (3 Replies)
Discussion started by: Kattoor
3 Replies

4. Shell Programming and Scripting

Take a list if strings from a file and search them in a list of files and report them

I have a file 1.txt with the below contents. -----cat 1.txt----- 1234 5678 1256 1234 1247 ------------------- I have 3 more files in a folder -----ls -lrt------- A1.txt A2.txt A3.txt ------------------- The contents of those three files are similar format with different data values... (8 Replies)
Discussion started by: realspirituals
8 Replies

5. Red Hat

Unable to copy files due to many files in directory

I have directory that has some billion file inside , i tried copy some files for specific date but it's always did not respond for long time and did not give any result.. i tried everything with find command and also with xargs.. even this command find . -mtime -2 -print | xargs ls -d did not... (2 Replies)
Discussion started by: before4
2 Replies

6. Shell Programming and Scripting

Unable to list files in ascending order

Hi ! I am just trying to list my files in ascending order so that in some other software, I just want merge with some modification, when I list its coming like this new-10.txt new-11.txt new-12.txt new-13.txt new-14.txt new-15.txt new-16.txt new-17.txt new-18.txt new-19.txt... (2 Replies)
Discussion started by: nex_asp
2 Replies

7. Shell Programming and Scripting

Unable to list particular file in dir.

Hi i am trying to list all the file starting with CSA.CHENAISCP* i am using below command to do that ls -lrt | grep CSA.CHENAISCP*however i am getting below error. 0403-027 The parameter list is too long.please suggest me some alternative way. scriptor (3 Replies)
Discussion started by: scriptor
3 Replies

8. UNIX for Dummies Questions & Answers

Unable to list folder contents

I'm unable to list the contents of a directory once I move into it. I have full permissions on this directory (called "Scripts" in the below example). The scenario is shown below in detail: Command 'ls' works fine to begin with: 1: pmn@linuxhost /home/pmn > cd /opt/smt/proiv 2:... (4 Replies)
Discussion started by: pmn
4 Replies

9. Solaris

Unable to list files in a directory

Hi have a system running solaris with a mount point running 58% capacity used, but unfortunately when I type ls -lrtin a specific directory, it returns: ls: Not enough space. I suspect there are millions of files in this directory. So what I did is to create a script like this: touch -mt... (13 Replies)
Discussion started by: fretagi
13 Replies

10. Shell Programming and Scripting

Unable to ssh and list files in local directory from remote.

#!/bin/bash script_work_dir="/home/websys/TEST_dpi_42_file_trnsfer_engine/PORT22/script_work_area" script_config_dir="/home/websys/TEST_dpi_42_file_trnsfer_engine/PORT22/script_config" dpi_sourceServerList=$script_config_dir"/dpi_sourceServerList" dpi_srvr_42="rtm@1.1.1.1"... (8 Replies)
Discussion started by: sadique.manzar
8 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 12:45 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy