Sponsored Content
Full Discussion: parameter list too long
Top Forums Shell Programming and Scripting parameter list too long Post 72482 by jerardfjay on Friday 20th of May 2005 02:21:36 PM
Old 05-20-2005
Quote:
Originally Posted by jim mcnamara
try
Code:
ls -ltr | grep '.Z'

Which is basically a hack.
Jim,

That works fine, Thanks. But I was trying to find out why passing a parameter to the ls command with a wildcard returns the error message that the paramter list being too long. Is this a shortfall with shell or is it a shortfall of 'ls'. Either way what should be done to overcome this error for the ls command? Smilie Jerardfjay
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Parameter List to Long

I am trying to do a find file command on a directory and delete files older then 30 days and I am getting an error saying that the parameter list that I am passing to the rm command is to long. Here is my command: find ~mydir/* -type f -mtime +$30 | xargs -i -exec rm -rf {} \; ksh:... (3 Replies)
Discussion started by: lesstjm
3 Replies

2. UNIX for Dummies Questions & Answers

Grep 0403-027 The parameter list is too long.

Hi there I get this error message when I try to do a basic grep. Does anyone have any ideas what is wrong. Thanks 0403-027 The parameter list is too long. (1 Reply)
Discussion started by: japada
1 Replies

3. Shell Programming and Scripting

rdist help 'parameter list too long'

I am trying to use the rdis command to keep a DR server in sync with our production server. My problem is that one of my directories has over 8 thousand files in it (and growing buy 300 per month) and when I execute it, it complains about 'parameter list too long'. All of the files in the... (5 Replies)
Discussion started by: hedrict
5 Replies

4. HP-UX

parameter list too long

Hi When i say ls * (HP-UX 11.11)in a particular directory it says sh: /usr/bin/ls: The parameter list is too long. Can somebody help me how to resolve this problem. (2 Replies)
Discussion started by: satyanarayang
2 Replies

5. UNIX for Dummies Questions & Answers

0403-027 The parameter list is too long.

hi when i ran the following command rm *_F i got this error 0403-027 The parameter list is too long. It shd remove 5000(around) files pls help me on this. why its throwing this error how to rectify this error (5 Replies)
Discussion started by: romiljain
5 Replies

6. Shell Programming and Scripting

Tar: Parameter list is too long

Hi all, I have a lot of files in my audit log directory which i am trying to tar. However, i hit the below error: ksh: /usr/bin/tar: 0403-027 The parameter list is too long. Is there any work around to resolve this problem? I need to tar all the files up. Thanks. (5 Replies)
Discussion started by: ahSher
5 Replies

7. UNIX for Dummies Questions & Answers

UNIX: 0403-027 The parameter list is too long

Hello All, We have a batch job that clean old records. This run a script to back up file then delete. Unfortunately, this job been failing lately. This is the error we received. "/usr/bin/compress: 0403-027 The parameter list is too long." I am not sure if the job failed since its... (2 Replies)
Discussion started by: juieshenkei
2 Replies

8. Shell Programming and Scripting

usr/bin/ls: 0403-027 The parameter list is too long

I ran this script in AIX 5L environment and getting an error usr/bin/ls: 0403-027 The parameter list is too long Our administrator had increased the maxium allowable size of the ARG/ENV list but it still doesn't work. I have tested the command in red below in the unix prompt and it works just... (13 Replies)
Discussion started by: hanie123
13 Replies

9. AIX

0403-027 The parameter list is too long on AIX 5.3

Hi we are using AIX 5.3 64bit I have near about 79000 log file having naming convention like "IFTMBCSun Aug 14 07:45:00 PAKST 2011". This naming convention was created by a script error, now we need to rename these log file by removing extar spaces and (:) colon for that we wrote below script ... (4 Replies)
Discussion started by: lodhi1978
4 Replies

10. UNIX for Dummies Questions & Answers

Getting parameter list is too long in grep command

Hi i am getting below message while using grep command "The parameter list is too long" grep -i 919716499889 * ksh: /usr/bin/grep: 0403-027 The parameter list is too long. please let me know what changes i can do in this command (5 Replies)
Discussion started by: scriptor
5 Replies
edinplace(1)							Mail Avenger 0.8.3						      edinplace(1)

NAME
edinplace - edit a file in place SYNOPSIS
edinplace [--error=code] [[--file=file] command [arg ...]] DESCRIPTION
edinplace runs command with its input from file (or standard input by default), and then replaces the contents of file with the output of command. To the extent possible, edinplace attempts to exit with the same status as command. If edinplace is run on standard input (no --file option), it must inherit a file descriptor 0 that is open for both reading and writing. When processing standard input, if edinplace does not encounter a fatal error, it rewinds its standard input to offset 0 before exiting. Thus, a script can first run edinplace command, then run another filter command such as grep, and the resulting output will be the output of grep on command's output. If no command is specified, edinplace just rewinds its standard input to file offset 0. In this case, it is an error to supply the --file option. Of course, rewinding only works when standard input is a real file (as opposed to a pipe or device). There are two options: --error=code (-x code) Ordinarily, edinplace attempts to exit with the same status as command. However, if edinplace encounters some fatal error (such as being unable to execute command), it will exit with status code. The default value is 1. The range of valid exit codes is 1-255, inclusive. --file=file (-f file) Specifies that file should be edited. Otherwise, edinplace will edit its standard input (which must be opened for both reading and writing). --skipfrom Skip the first line of the file if it starts "From ". If edinplace is run without a command, positions the file offset at the start of the second line of the file. If edinplace is run with a command, then the first line of the file is neither fed to the command, nor overwritten. This option is useful for running edinplace over mail files, which sometimes start with a "From " line specifying the envelope sender of the message. Since "From " is not part of the message header, just a Unix convention, some programs are confused by the presence of that line. Note that if you specify a command, then edinplace resets the file offset to 0 upon exiting, even if the --skipfrom option was present. EXAMPLES
The following command prepends the string "ORIGINAL: " to the beginning of each line in text file message: edinplace -f message sed -e 's/^/ORIGINAL: /' The following command runs the spamassassin mail filter program on a mail message stored in file message, replacing the contents of message with spamassassin's annotated output, and exiting with code 100 if spamassassin thinks the message is spam. If edinplace encounters any fatal errors, it will exit with code 111. edinplace -x 111 -f message spamassassin -e 100 (spamassassin reads a mail message on standard input and outputs an annotated copy of the message including information about whether or not the message is likely to be spam and why. The -e option to spamassassin specifies what exit status spamassassin should use if the message appears to be spam; edinplace will use the same exit code as the program it has run.) To run spamassassin on incoming mail before accepting the mail from the remote client, place the following line in an appropriate Mail Avenger rcpt file as the last command executed: bodytest edinplace -x 111 spamassassin -e 100 SEE ALSO
avenger(1) The Mail Avenger home page: <http://www.mailavenger.org/>. BUGS
edinplace does not make a copy of the file being edited, but rather overwrites the file as it is being processed. At any point where command has produced more output than it has consumed input from the file, edinplace buffers the difference in memory. Thus, a command that outputs large amounts of data before reading the input file can run edinplace out of memory. (A program that outputs data as it reads even a very large file should be fine, however.) If command crashes or malfunctions for any reason, you will likely lose the input file, since edinplace will view this as a program that simply outputs the empty file. AUTHOR
David Mazieres Mail Avenger 0.8.3 2012-04-05 edinplace(1)
All times are GMT -4. The time now is 07:22 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy