Sponsored Content
Top Forums Shell Programming and Scripting Unprintable filenames and automating a chmod Post 302164350 by jpport123 on Monday 4th of February 2008 02:00:45 PM
Old 02-04-2008
Unprintable filenames and automating a chmod

I have a fair amount of files in multiple directoroes that need to have an attribute modified, so a script is in order. Initially it seemed like creating a script with a find and then pipe it to xargs chmod would do the trick. Enter into the equation non-printable filenames... ugh... Has anyone in the forum dealt with this with any luck?

Thanks
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

automating password ?

Hi all, I want to write a script which logs into a database (DB2). To do this i need to have a password. This will be done lots and lots of times, so i need to modify the script to automate the response to the password request. How do i this, because at present i do the following: db2 connect... (3 Replies)
Discussion started by: Liamo
3 Replies

2. UNIX for Advanced & Expert Users

Automating Autosys

Can multiple Autosys jobs be changed with the same parameter at the same time? what scripting do I need? (0 Replies)
Discussion started by: LilyClaro
0 Replies

3. UNIX for Dummies Questions & Answers

CHMOD DOS Filenames

This is a little embarassing to ask this question, anywho... I want to chmod some directories on our public drive but I having difficulties with those created in windows eg p:\usr\public\Bill Gates When I enter chmod 777 Bill Gates I get an error, obviously because of the space in the... (1 Reply)
Discussion started by: moondogi
1 Replies

4. UNIX and Linux Applications

What is the difference between chmod in solaris and chmod in Linux?

i think it is the same in both... Iam i right? (1 Reply)
Discussion started by: sumaiya
1 Replies

5. Shell Programming and Scripting

Automating scsudo

Solaris... I need to automate running of scsudo from another script. However, I've determined that scsudo reads the password from /dev/tty rather than STDIN when the Password prompt appears. I don't have 'expect' or equivalents available - can I automate sending the correct password when... (1 Reply)
Discussion started by: JerryHone
1 Replies

6. Shell Programming and Scripting

Automating The process

Hi Guru's, I am trying to write a scripts that will automate my image provisoining process. Scenario: I have Linux Image Hosted on cloud which needs to be provisoned before it can be used. Currently we log onto the image through the putty on windows and connect to linux instance. I... (3 Replies)
Discussion started by: taqvia
3 Replies

7. UNIX for Dummies Questions & Answers

Automating a process

Could any one tell me , how to start a thread here, i just searching for so long. sorry to post in irrelavent here ---------- Post updated at 08:19 AM ---------- Previous update was at 08:00 AM ---------- Hi, I got a requirement to automate the process. We have SLA files, there are... (1 Reply)
Discussion started by: afahmed
1 Replies

8. Shell Programming and Scripting

Automating

Hi All, I have a shell script that is integrated with a fault management system. It periodically monitors the system and raises an alarm. This script has different functions and it accepts input from us on the console. Is there any way to invoke it using a shell script ? Please advise. ... (2 Replies)
Discussion started by: praviper
2 Replies

9. UNIX for Dummies Questions & Answers

Automating the FTP get

Hi , I want to pull files from ftp monthly once . The files in ftp has a something like 292_fileto_pull and next month it will be 293_fileto_pull for each month the number keeps increasing. i thought in my script if i can use date and increment the number by it mget *_292_fileto_pull i... (2 Replies)
Discussion started by: vikatakavi
2 Replies

10. Shell Programming and Scripting

How to remove unprintable characters?

Hi Gurus, when I run following command to split one line file to multiple lines, it stopped because of hitting un-printable special charactor. awk -v L="$2" '{for (i=1; i<=length($0); i+=L) print substr($0, i, L)}' "$1" > "$1"_split I use cat -A, I can see one un-printable charactor M-^T. how... (1 Reply)
Discussion started by: ken6503
1 Replies
CHASE(1)							Chase user's manual							  CHASE(1)

NAME
chase - chase symbolic links SYNOPSIS
chase [ --verbose | --from-file | -f | --null | -0 | --loop-warn-threshold COUNT | -w COUNT | --loop-fail-threshold COUNT | -l COUNT | --disable-loop-detection | -D ] [file...] chase -v | --version chase -h | --help DESCRIPTION
Chase is a small utility that tracks down the name of the actual file that is truly accessed, when one hits a symbolic link. It chases the link, so to speak. In normal operation, you give chase a name of an existing file. The program will then show you (or, more accurately, print to the standard output stream) the name of the real file that the original file referred to. It does not matter if you give the program the name of a reg- ular file; chase will just give you the same name back. You can give the utility the option --verbose, in order to have it be more verbose in its operation. You can also give the program a list of files from which it will read the file names to be chased (see the option --from-file). I'll give you a good example of a case where chase is useful. In a Debian GNU/Linux system, software installation is handled by the pro- gram dpkg(8). There is a way to query dpkg(8), which package a file belongs to. Unfortunately, this does not not grok all symlinks. This is a problem, since the Debian system uses symbolic links extensively for handling several flavours of a program (say, XEmacs and GNU Emacs and the versions 19 and 20 of both). Now with chase, one can determine the real file easily and then using this result as an argument to dpkg(8). Observe: ajk@ugh:~$ dpkg -S `which xemacs20` dpkg: /usr/bin/xemacs20 not found. ajk@ugh:~$ dpkg -S `which xemacs20 | xargs chase` xemacs20-nomule: /usr/bin/xemacs-20.4-nomule ajk@ugh:~$ When given multiple file names as arguments, chase will chase every one of them in order. OPTIONS
The following options are recognized by chase: --verbose Chat about what is being done. -f, --from-file Treat the file names on the command line as sources for names to be chased. If this option is present, chase will read in each of the files given on the command line (both a sole dash "-" and the absence of file names will be taken as meaning the standard input stream). Each line in the files is taken as a verbatim file name that will be chased like it had been given on the command line of a run without this option. There is no means for quoting the newline character; therefore only file names that do not contain new- lines can be specified via the files. This restriction is lifted by the -0 option, though. However, literal spaces are preserved and are not interpreted as special. -0, --null This option implies the option -f, which reads file names from a file. The -0 option modifies the behavior -f so that instead of treating lines in the file as file names, the file names are expected to be separated by null characters. This allows for specify- ing file names with newlines in them with -f. -w WCOUNT, --loop-warn-threshold=WCOUNT -l LCOUNT, --loop-fail-threshold=LCOUNT Set the threshold for warning about a possible symlink loop (WCOUNT) and for failing because of one (LCOUNT). There are default values, which you can find out by invoking chase with the argument --help. Using zero as WCOUNT or LCOUNT disables the check. -D, --disable-loop-detection Normally chase keeps a record of all symlinks it has visited when chasing the current file. It uses this record to reliably detect symlink loops. However, checking the record slows the process a little (more for long chains of symlinks) and the record requires a small amount of memory (more for long chains of symlinks), so it may be desirable in some cases to inhibit this check. This option disables this loop detection and the associated recording of visited symlinks. When this option is in effect (assuming no bugs in the related code) chase runs in constant space and linear time relative to the length of the symlink chains encountered. -h, --help Output a usage summary and exit successfully. -v, --version Show version information and exit successfully. DIAGNOSTICS
The exit status is 0 if and only if all files given in the command lines exist and none of them are dangling symlinks. The following messages are emitted by chase when it suspects or detects a symlink loop: quite many symlink hops, hope we're not looping... This means that the chain of symlinks is longer than a given threshold. This may mean that the chain is infinite (and thus contains a loop somewhere). The threshold can be specified by using the --loop-warn-threshold command line option. too many symlink hops, giving up... This means that the chain of symlinks is longer than a given threshold. This usually means that the chain is infinite (and thus contains a loop somewhere). The threshold can be specified by using the --loop-fail-threshold command line option. If you see this message, it means that chase has given up on that file. symlink loop detected, giving up... The symlink chain is looping and therefore there is no result for the chase. Chase has given up on that file. Additionally, Chase emits several error messages under problematic conditions. They all come from the system libraries, so the program has no control over the actual wording of the messages. They all follow the format "program name: file name: error message", where file name is the name of the offending file or directory. BUGS
Chase may have bugs. If you find them, please report them to <rotty@debian.org> or preferably via the Debian bugtracking system. AUTHOR
Chase has been written by Antti-Juhani Kaijanaho <gaia@iki.fi> and is currently maintained by Andreas Rottmann <rotty@debian.org>. SEE ALSO
find(1), ln(1), namei(1), readlink(1), readlink(2), symlinks(1) Chase 0.5 2000-01-02 CHASE(1)
All times are GMT -4. The time now is 03:18 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy