01-14-2015
It all depends on how may files are in the current directory. The * on the command line is expanded to names them all before the command is actually run. If there are lots, then it becomes huge and exceeds the allowed command length resulting in the error you see.
Robin
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
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
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
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
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. Shell Programming and Scripting
This is one of shell things I guess. I have a directory in a production server that contains about 20,000 files. It gets cleaned up every week and is kept in check that it does not get out of hand.
Here is my problem.
When I perform a ls -ltr, I get the listing. However should I parameterize... (4 Replies)
Discussion started by: jerardfjay
4 Replies
6. UNIX for Dummies Questions & Answers
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
7. Shell Programming and Scripting
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
8. UNIX for Dummies Questions & Answers
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
9. Shell Programming and Scripting
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
10. AIX
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
LEARN ABOUT MINIX
resolvepath
resolvepath(2) System Calls resolvepath(2)
NAME
resolvepath - resolve all symbolic links of a path name
SYNOPSIS
#include <unistd.h>
int resolvepath(const char *path, char *buf, size_t bufsiz);
DESCRIPTION
The resolvepath() function fully resolves all symbolic links in the path name path into a resulting path name free of symbolic links and
places the resulting path name in the buffer buf which has size bufsiz. The resulting path name names the same file or directory as the
original path name. All ``.'' components are eliminated and every non-leading ``..'' component is eliminated together with its preceding
directory component. If leading ``..'' components reach to the root directory, they are replaced by ``/''. If the number of bytes in the
resulting path name is less than bufsiz, the contents of the remainder of buf are unspecified.
RETURN VALUES
Upon successful completion, resolvepath() returns the count of bytes placed in the buffer. Otherwise, it returns -1, leaves the buffer
unchanged, and sets errno to indicate the error.
ERRORS
The resolvepath() function will fail if:
EACCES Search permission is denied for a component of the path prefix of path or for a path prefix component resulting
from the resolution of a symbolic link.
EFAULT The path or buf argument points to an illegal address.
EIO An I/O error occurred while reading from the file system.
ENOENT The path argument is an empty string or a component of path or a path name component produced by resolving a sym-
bolic link does not name an existing file.
ELOOP Too many symbolic links were encountered in resolving path.
ENAMETOOLONG The length of path exceeds PATH_MAX, or a path name component is longer than NAME_MAX. Path name resolution of a
symbolic link produced an intermediate result whose length exceeds PATH_MAX or a component whose length exceeds
NAME_MAX.
ENOTDIR A component of the path prefix of path or of a path prefix component resulting from the resolution of a symbolic
link is not a directory.
USAGE
No more than PATH_MAX bytes will be placed in the buffer. Applications should not assume that the returned contents of the buffer are null-
terminated.
SEE ALSO
readlink(2), realpath(3C)
SunOS 5.10 12 May 1997 resolvepath(2)