12-07-2012
Wildcards are processed by the shell in UNIX.
When you issue "dir *" in DOS, the "*" will be passed as an argument to "dir", which would handle it. "ls" does not know how to handle "*", instead the shell, before passing the arguments, expands it itself by replacing the wildcard with all the filenames that fit. Only the so created line is passed to "ls" (or any other command).
This is why your error occurs: the shell tries to replace the "*" with all the filenames of 79k files and - naturally - the resulting line is too long to handle.
But "ls" will list all files anyway, so "*" is the default argument. You can simply leave it out, no?
I hope this helps.
bakunin
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,
I'm trying to list specific files and redirecting to a file
ls aqp* > temp.lst
but getting "/usr/bin/ls: 0403-027 the parameter list is too long." error. I just have 236 files in the directory.
I tried "ls | grep 'aqp*' > temp.lst" too, but nothing was redirected.
+ grep aqp*
+... (4 Replies)
Discussion started by: dateez
4 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,
I am getting the below error message When i am trying to delete the files from the directory.Could you please guide me?
rm *.aud
ksh: /usr/bin/rm: 0403-027 The parameter list is too long.
and
find /oracle/admin/testP/adump/*.aud -mtime +5 -exec rm {} \;
ksh: /usr/bin/find:... (3 Replies)
Discussion started by: nokiae63
3 Replies
LEARN ABOUT SUSE
mkmanifest
mkmanifest(1) General Commands Manual mkmanifest(1)
Name
mkmanifest - makes list of file names and their DOS 8+3 equivalent
Note of warning
This manpage has been automatically generated from mtools's texinfo documentation, and may not be entirely accurate or complete. See the
end of this man page for details.
Description
The mkmanifest command is used to create a shell script (packing list) to restore Unix filenames. Its syntax is:
mkmanifest [ files ]
Mkmanifest creates a shell script that aids in the restoration of Unix filenames that got clobbered by the MS-DOS filename restrictions.
MS-DOS filenames are restricted to 8 character names, 3 character extensions, upper case only, no device names, and no illegal characters.
The mkmanifest program is compatible with the methods used in pcomm, arc, and mtools to change perfectly good Unix filenames to fit the MS-
DOS restrictions. This command is only useful if the target system which will read the diskette cannot handle VFAT long names.
Example
You want to copy the following Unix files to a MS-DOS diskette (using the mcopy command).
very_long_name
2.many.dots
illegal:
good.c
prn.dev
Capital
ASCII converts the names to:
very_lon
2xmany.dot
illegalx
good.c
xprn.dev
capital
The command:
mkmanifest very_long_name 2.many.dots illegal: good.c prn.dev Capital >manifest
would produce the following:
mv very_lon very_long_name
mv 2xmany.dot 2.many.dots
mv illegalx illegal:
mv xprn.dev prn.dev
mv capital Capital
Notice that "good.c" did not require any conversion, so it did not appear in the output.
Suppose I've copied these files from the diskette to another Unix system, and I now want the files back to their original names. If the
file "manifest" (the output captured above) was sent along with those files, it could be used to convert the filenames.
Bugs
The short names generated by mkmanifest follow the old convention (from mtools-2.0.7) and not the one from Windows 95 and mtools-3.0.
See Also
Mtools' texinfo doc
Viewing the texi doc
This manpage has been automatically generated from mtools's texinfo documentation. However, this process is only approximative, and some
items, such as crossreferences, footnotes and indices are lost in this translation process. Indeed, these items have no appropriate repre-
sentation in the manpage format. Moreover, not all information has been translated into the manpage version. Thus I strongly advise you
to use the original texinfo doc. See the end of this manpage for instructions how to view the texinfo doc.
* To generate a printable copy from the texinfo doc, run the following commands:
./configure; make dvi; dvips mtools.dvi
* To generate a html copy, run:
./configure; make html
A premade html can be found at `http://www.gnu.org/software/mtools/manual/mtools.html'
* To generate an info copy (browsable using emacs' info mode), run:
./configure; make info
The texinfo doc looks most pretty when printed or as html. Indeed, in the info version certain examples are difficult to read due to the
quoting conventions used in info.
mtools-4.0.13 28Feb10 mkmanifest(1)