07-17-2009
Paramater list too long while chmod
Hi i am transferring the files(around 10000) from the Windows sever to the UNIX server in that i run a command chmod 777 filename.txt
but it is taking a longer time as it gives chmod for each and every file.
So i thouught of giving the permission from the UNIX itself and i tried running
chmod 777 filename.txt and it is throwing an error Parameter list is too long.
So i tried it with find . -name "filename*.txt" -exec chmod 777 {} \;
still i get the error parameter list is too long!
Any other options to avoid this error wud be highly appreciated!
Thanks in advance!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I do ls -l ABC*, I get arg list too long message. This will not happen if ABC* has small no of files I believe 4000 files is limit. Any way of avoiding this.
I even tried like this
for i in `ls -l ABC*`
do
echo $i
done
Same problem.
Any solution would be great.
I am on HP-UX... (5 Replies)
Discussion started by: vingupta
5 Replies
2. Shell Programming and Scripting
I'm creating a shell script, part of which has a cp command.So far i've got:
cp --recursive --reply=yes /development/myProgram/* /somewhere/else
I need to add something that says to not copy certain files, in this case all directories named "CVS" and files named ".project" and... (2 Replies)
Discussion started by: allelopath
2 Replies
3. UNIX for Dummies Questions & Answers
echo dirname/filename* | xargs ls -t
As a substitute doesn't give the results desired when I exceed the buffer size. I still want the files listed in chronological order, unfortunately xargs releases the names piecemeal...does anyone have any ideas? :( (4 Replies)
Discussion started by: CSU_Ram
4 Replies
4. 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
5. UNIX for Dummies Questions & Answers
If I am root user, and trying to chown everything in a directory and it's subdirectories (e.g. httpdocs and everything inside that directory, including it's sub directories), how would I do that? I tried it with -r but it didnt seem to work...can someone help with the correct syntax?
Also, if I... (3 Replies)
Discussion started by: Eman619
3 Replies
6. UNIX and Linux Applications
i think it is the same in both... Iam i right? (1 Reply)
Discussion started by: sumaiya
1 Replies
7. Shell Programming and Scripting
Dear Experts,
I have a list of 10K files in a directory. I am not able to execute any commands lile ls -lrt, awk, sed, mv, etc........
I wanna execute below command and get the output. How can I achieve it?? Pls help.
root# awk -F'|' '$1 == 1' file_20120710* | wc -l
/bin/awk: Argument list... (2 Replies)
Discussion started by: Naga06
2 Replies
8. Shell Programming and Scripting
Hi,
I have a list of files in a text file. I want to change the mode of every one of those files, but am having difficulty in doing so.
#!/bin/bash
files=/home/david/files.txt
for $item in $files {
chmod 640 $item
}
.. doesn't cut it.
Can anyone help?
Thanks. (7 Replies)
Discussion started by: davidm123SED
7 Replies
9. UNIX for Dummies Questions & Answers
Hello All,
I am trying to find a file name with .sh exention from a list of .dat files inside a directory.
find /app/folder1/* -name '*.dat'| xargs grep '.sh'
ksh: /usr/local/bin/find: arg list too long
Please help me finding the command.
Thanks (3 Replies)
Discussion started by: tkhan9
3 Replies
10. Shell Programming and Scripting
Hi Team,
Here's the situation.
I have approximately 300000 to 500000 jpg files in /appl/abcd/work_dir
mv /appl/abcd/work_dir /appl/abcd/process_dir
The above move command will work if the jpg files count is close to 50000 (not sure). If the count is less this mv command holds good. But if... (14 Replies)
Discussion started by: kmanivan82
14 Replies
CHMOD(1) General Commands Manual CHMOD(1)
NAME
chmod - change mode
SYNOPSIS
chmod [ -Rf ] mode file ...
DESCRIPTION
The mode of each named file is changed according to mode, which may be absolute or symbolic. An absolute mode is an octal number con-
structed from the OR of the following modes:
4000 set user ID on execution
2000 set group ID on execution
1000 sticky bit, see chmod(2)
0400 read by owner
0200 write by owner
0100 execute (search in directory) by owner
0070 read, write, execute (search) by group
0007 read, write, execute (search) by others
A symbolic mode has the form:
[who] op permission [op permission] ...
The who part is a combination of the letters u (for user's permissions), g (group) and o (other). The letter a stands for all, or ugo. If
who is omitted, the default is a but the setting of the file creation mask (see umask(2)) is taken into account.
Op can be + to add permission to the file's mode, - to take away permission and = to assign permission absolutely (all other bits will be
reset).
Permission is any combination of the letters r (read), w (write), x (execute), X (set execute only if file is a directory or some other
execute bit is set), s (set owner or group id) and t (save text - sticky). Letters u, g, or o indicate that permission is to be taken from
the current mode. Omitting permission is only useful with = to take away all permissions.
When the -R option is given, chmod recursively descends its directory arguments setting the mode for each file as described above. When
symbolic links are encountered, their mode is not changed and they are not traversed.
If the -f option is given, chmod will not complain if it fails to change the mode on a file.
EXAMPLES
The first example denies write permission to others, the second makes a file executable by all if it is executable by anyone:
chmod o-w file
chmod +X file
Multiple symbolic modes separated by commas may be given. Operations are performed in the order specified. The letter s is only useful
with u or g.
Only the owner of a file (or the super-user) may change its mode.
SEE ALSO
ls(1), chmod(2), stat(2), umask(2), chown(8)
7th Edition May 22, 1986 CHMOD(1)