Sponsored Content
Top Forums UNIX for Dummies Questions & Answers How do properties effect script? Post 302077318 by blowtorch on Wednesday 21st of June 2006 06:23:11 AM
Old 06-21-2006
To be honest, I was surprised to find that the -f and -i options work together. But on checking the man page (on HP and Sun), I found the following:
On HP-UX:
HTML Code:
rm recognizes the following options:

           -f   Force each file or directory to be removed without prompting
                for confirmation, regardless of the permissions of the
                entry.  This option also suppresses diagnostic messages
                regarding nonexistent operands.

                This option does not suppress any diagnostic messages other
                than those regarding nonexistent operands.  To suppress all
                error message and interactive prompts, the -f option should
                be used while redirecting standard error output to
                /dev/null.

                This option ignores any previous occurrence of the -i
                option.

 Hewlett-Packard Company            - 1 -   HP-UX Release 11i: November 2000

 rm(1)                                                                 rm(1)

           -i   Write a prompt to standard error requesting confirmation
                before removing each entry.
On Solaris:
HTML Code:
    -f    Removes all files (whether write-protected or not)  in
           a  directory  without  prompting the user. In a write-
           protected directory, however, files are never  removed
           (whatever  their permissions are), but no messages are
           displayed. If the removal of a write-protected  direc-
           tory  is  attempted,  this option will not suppress an
           error message.

     -i    Interactive. With this option, rm prompts for  confir-
           mation  before removing any files. It overrides the -f
           option and remains in  effect  even  if  the  standard
           input is not a terminal.
So if you run "rm -fi" on HP, it is interactive, but "rm -if" is forced as specified in the man page. But on Solaris, if "-i" is specified, then the "-f" is ignored regardless of where it occurs.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

recursive effect!!

I run the following command in some of my folders... and ended up with a huge mess!! find . -type f -exec perl -e 's/blabla/zzzxxxx/gi' -p -i.bak {} \; I had to kill the process and later when I checked with one of my folders.. ls vaditerm.dt.bak vaditerm.dt.bak.bak... (2 Replies)
Discussion started by: sskb
2 Replies

2. UNIX for Advanced & Expert Users

Effect of Preemptive Kernel

hi there, i am porting kernel 2.2 driver program to kernel 2.6. for some extent i am successfull but some times the system gets hanged. what might be the problem? i am not able to get any help from log messages as nothing is being printed at that moment. hey does this kernel preemptiveness and... (2 Replies)
Discussion started by: sriram.ec
2 Replies

3. Solaris

will this script in crontab effect SUN 9??

Hi all, I work in Sun Solaris 9. I am plan to put the following script(remove90dysOldrfiles.sh) in CRONTAB for removing huge huge number of files those are older than 90 days from different directory. In the Crontab i will set the time for everymidnight it will search 90days older file and... (2 Replies)
Discussion started by: thepurple
2 Replies

4. Virtualization and Cloud Computing

The Network Effect - Part 1

2008-10-31T22:46:14+01:00 http://geekandpoke.typepad.com/.a/6a00d8341d3df553ef010535ce543e970c-800wi Nicholas Carr (and here) has some problems with Tim O'Reilly's theory about the cloud and the network effect. http://feeds.feedburner.com/~f/GeekAndPoke?i=OFn0M... (0 Replies)
Discussion started by: Linux Bot
0 Replies

5. Shell Programming and Scripting

Nullify the effect of Trap command in later part of the script

Hi All, i have an issue regarding trap command. i have specified trap function in the beginning of the script to catch some signals but in the later part of the script i want to remove the effect of this. Can anybody help me out of this. for e.g. pressing Ctrl+C for the first time should... (2 Replies)
Discussion started by: vikas_kesarwani
2 Replies

6. Shell Programming and Scripting

Reading the Properties File From Shell script

Hi, I am new to the shell script please I need help for following question. I have properties file name called "com.test.properties" I have No of key values in this properties. com.person.name = xyz com.person.age = 55 com.person.address = hello I want read this properties but i... (1 Reply)
Discussion started by: venukjs
1 Replies

7. UNIX for Dummies Questions & Answers

What crontab is in effect after reboot

A basic cron question and I hope I explain it enough. If a person creates a file to use with cron and issues the followin command: crontab I understand this will set the cron entries to whatever is in . However, if we now edit the crontab with: crontab -e and save, how does cron... (3 Replies)
Discussion started by: niswonp
3 Replies

8. Shell Programming and Scripting

script to parse the properties file

Hi Friends, I have a requirement to parse a properties file having a key=value pairs. i need to count the number of key value pairs in the properties file and iterate through each key-value pair. I have written the script to read the number of lines from the property file, but cannot... (2 Replies)
Discussion started by: prashdeep
2 Replies

9. Shell Programming and Scripting

Alias has no effect in script

It doesn't have effect in script but it works on the terminal root@server:/opt/kvm/usecases/logs# alias echo='echo -e' root@server:/opt/kvm/usecases/logs# echo "xxxx\n" xxxx root@server:/opt/kvm/usecases/logs# cat xx.sh #!/bin/bash alias echo='echo -n' echo "sssf \n" ... (3 Replies)
Discussion started by: yanglei_fage
3 Replies

10. Shell Programming and Scripting

awk set $1 to itself, effect on $0

jotne posted an interesting thread an hour or two ago, and ended up with the following: awk '{$1=$1} /^+$/' file I had a question about the effect of $1=$1 assignment, and thought it better to start a new thread, because it's really a different topic. $ cat test.sh set -v echo " abcd" | awk... (3 Replies)
Discussion started by: hanson44
3 Replies
rm(1)								   User Commands							     rm(1)

NAME
rm, rmdir - remove directory entries SYNOPSIS
/usr/bin/rm [-f] [-i] file... /usr/bin/rm -rR [-f] [-i] dirname... [file...] /usr/xpg4/bin/rm [-fiRr] file... /usr/bin/rmdir [-ps] dirname... DESCRIPTION
/usr/bin/rm /usr/xpg4/bin/rm The rm utility removes the directory entry specified by each file argument. If a file has no write permission and the standard input is a terminal, the full set of permissions (in octal) for the file are printed followed by a question mark. This is a prompt for confirmation. If the answer begins with y (for yes), the file is deleted, otherwise the file remains. If file is a symbolic link, the link will be removed, but the file or directory to which it refers will not be deleted. Users do not need write permission to remove a symbolic link, provided they have write permissions in the directory. If multiple files are specified and removal of a file fails for any reason, rm will write a diagnostic message to standard error, do noth- ing more to the current file, and go on to any remaining files. If the standard input is not a terminal, the utility will operate as if the -f option is in effect. /usr/bin/rmdir The rmdir utility will remove the directory entry specified by each dirname operand, which must refer to an empty directory. Directories will be processed in the order specified. If a directory and a subdirectory of that directory are specified in a single invoca- tion of rmdir, the subdirectory must be specified before the parent directory so that the parent directory will be empty when rmdir tries to remove it. OPTIONS
The following options are supported for /usr/bin/rm and /usr/xpg4/bin/rm: -r Recursively removes directories and subdirectories in the argument list. The directory will be emptied of files and removed. The user is normally prompted for removal of any write-protected files which the directory contains. The write-protected files are removed without prompting, however, if the -f option is used, or if the standard input is not a terminal and the -i option is not used. Symbolic links that are encountered with this option will not be traversed. If the removal of a non-empty, write-protected directory is attempted, the utility will always fail (even if the -f option is used), resulting in an error message. -R Same as -r option. /usr/bin/rm The following options are supported for /usr/bin/rm only: -f Removes all files (whether write-protected or not) in a directory without prompting the user. In a write-protected directory, how- ever, files are never removed (whatever their permissions are), but no messages are displayed. If the removal of a write-protected directory is attempted, this option will not suppress an error message. -i Interactive. With this option, rm prompts for confirmation before removing any files. It overrides the -f option and remains in effect even if the standard input is not a terminal. /usr/xpg4/bin/rm The following options are supported for /usr/xpg4/bin/rm only: -f Does not prompt for confirmation. Does not write diagnostic messages or modify the exit status in the case of non-existent oper- ands. Any previous occurrences of the -i option will be ignored. -i Prompts for confirmation. Any occurrences of the -f option will be ignored. /usr/bin/rmdir The following options are supported for /usr/bin/rmdir only: -p Allows users to remove the directory dirname and its parent directories which become empty. A message is printed to standard error if all or part of the path could not be removed. -s Suppresses the message printed on the standard error when -p is in effect. OPERANDS
The following operands are supported: file A path name of a directory entry to be removed. dirname A path name of an empty directory to be removed. USAGE
See largefile(5) for the description of the behavior of rm and rmdir when encountering files greater than or equal to 2 Gbyte ( 2 **31 bytes). EXAMPLES
The following examples are valid for the commands shown. /usr/bin/rm /usr/xpg4/bin/rm Example 1: Removing directories The following command: example% rm a.out core removes the directory entries a.out and core. Example 2: Removing a directory without prompting The following command: example% rm -rf junk removes the directory junk and all its contents, without prompting. /usr/bin/rmdir Example 3: Removing empty directories If a directory a in the current directory is empty, except that it contains a directory b, and a/b is empty except that it contains a directory c, the following command will remove all three directories: example% rmdir -p a/b/c ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of rm and rmdir: LANG, LC_ALL, LC_COLLATE, LC_CTYPE, LC_MESSAGES, and NLSPATH. EXIT STATUS
The following exit values are returned: 0 If the -f option was not specified, all the named directory entries were removed; otherwise, all the existing named directory entries were removed. >0 An error occurred. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: /usr/bin/rm /usr/bin/rmdir +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+ |CSI |enabled | +-----------------------------+-----------------------------+ /usr/xpg4/bin/rm +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWxcu4 | +-----------------------------+-----------------------------+ |CSI |enabled | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ SEE ALSO
rmdir(2), unlink(2), attributes(5), environ(5), largefile(5), standards(5) DIAGNOSTICS
All messages are generally self-explanatory. It is forbidden to remove the files "." and ".." in order to avoid the consequences of inadvertently doing something like the following: example% rm -r .* It is forbidden to remove the file "/" in order to avoid the consequences of inadvertently doing something like: example% rm -rf $x/$y or example% rm -rf /$y when $x and $y expand to empty strings. NOTES
A - permits the user to mark explicitly the end of any command line options, allowing rm to recognize file arguments that begin with a -. As an aid to BSD migration, rm will accept -- as a synonym for -. This migration aid may disappear in a future release. If a -- and a - both appear on the same command line, the second will be interpreted as a file. SunOS 5.10 26 Jan 2001 rm(1)
All times are GMT -4. The time now is 09:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy