05-17-2011
Find command gave unexpected results
Hi,
I recently executed a find command that caused unexpected permission changes and we had to do a full system restore. Can someone please explain what this command would do?
find /staging/admin/scr * -exec chmod 755 '{}' +
It caused file permissions inside / to be modified strangely.
Can someone let me know why?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
This is probably simple so forgive me...
I just want to find all files in a folder created within the last 10 minutes...
This is easy:
# find /home/folder -cmin -10
If the find command locates any files created in the last ten minutes I want it to send an email alert.
I just want to... (3 Replies)
Discussion started by: gardellap
3 Replies
2. Shell Programming and Scripting
Hi
Purpose is to have a utility command to find and edit files .
I tried a function like the following in my .profile file
function vifind(){
find . -name $1 -print -exec vi {} \;
}
Is this correct? is there a better way to do it?
I see this behaving a bit strange in case of AIX, and... (6 Replies)
Discussion started by: grep_whoami
6 Replies
3. UNIX for Dummies Questions & Answers
Hello,
When I run this script, here's what I get:
Searching ...
found 1111
2222
3333
.....
7777
.....
8888
9999 in 95_test
Search completed.
I expected only to see what number was found in the file, not including the ones not found.
Thanks for your help!
#!/bin/sh (1 Reply)
Discussion started by: SSims
1 Replies
4. Shell Programming and Scripting
I have two sripts running in bash. The first one uncompresses log files and moves them to a working directory using uncompress -c and > output to new directory. It then creates one control record to assure our search returns a record. It then calls or executes the second script, which is a grep for... (6 Replies)
Discussion started by: altamaha
6 Replies
5. Shell Programming and Scripting
Following script gives different results when triggered from Cron compared to when triggered from command line.
It is not able to assign values to some variables when triggered from cron.
Can any one help? Its a very simple script
Script -
#! /bin/ksh
sFile=$1
sEnv=$2
sWaitFile=$3... (1 Reply)
Discussion started by: sumeet
1 Replies
6. Shell Programming and Scripting
Hi,
In an effort to collect all my .java-files and place them in a LaTeXfile (using the listings environment of latex), i tried to use ex.
So what i have now is:
find . -name "*\.java" > latex
ex latex <<HERE
%s/\(.*\)/\\lstinputlisting{\1}
wq
HERE
So i try to escape the '\' with... (1 Reply)
Discussion started by: HannesBBR
1 Replies
7. Shell Programming and Scripting
Hi
I am comparing two files with comm -13 < (sort acc11.txt) < (sort acc12.txt) > output.txt
purpose: Get non matching records which are in acc12 but not in acc11...
TI am getting WRONG output.
Is there any constraints with record length with comm? The above files are the two consective ... (2 Replies)
Discussion started by: vedanta
2 Replies
8. Shell Programming and Scripting
Hi
I'm having hard time here with below script. If i run script manually i see expected results but, if i keep this script in cron job i'm getting unexpected results. Unexpected results means even though condition is true,cronjob returning output of else condition.
This script and cronjob... (2 Replies)
Discussion started by: buzzme
2 Replies
9. Shell Programming and Scripting
Hello,
Hitting a wall on this one. When at the command prompt it works fine:
# find /home/testuser -name 'PAINT*canvasON.txt'
/home/testuser/PAINT_canvasON.txt
# pwd
/home/testuser
# ls -l PAINT*canvasON.txt
-rw-r--r-- 1 root user 23 Feb 07 02:58 PAINT_canvasON.txt... (2 Replies)
Discussion started by: seekryts15
2 Replies
10. Shell Programming and Scripting
I want to remove any files that are older than 2 days from a directory. It deletes those files. Then it comes back with a message it is a directory. What am I doing wrong here?
+ find /mydir -mtime +2 -exec rm -f '{}' ';'
rm: /mydir is a directory (2 Replies)
Discussion started by: jtamminen
2 Replies
AMIN(1) General Commands Manual AMIN(1)
NAME
amin - notify writers that you are busy
SYNOPSIS
amin [-ynesp] command [args...]
DESCRIPTION
Amin is used when you don't want to be written while running a command. It runs the command given normally. If your message permissions
(see mesg(1)) are off, it does nothing much else. If your messages are on, people writing you with write(1) will be warned that you are
running that command and will be given the opportunity to change their minds about writing you.
The -n option may be used to turn your messages entirely off for the duration of the execution of command. People writing you will get
"Permission denied". The -y option turns your message permissions on for the duration of the execution of the command. The -e may be used
after either -n or -y to indicate that the logins listed in the .yeswrite or the .nowrite files respectively are exceptions to the message
permissions set. The default is -s which leaves your message permissions in their original state. In any case, after the command is com-
plete, your permissions will be restored to the original state.
The -p flag causes all telegrams sent to you while the command is running to be saved. They are displayed as soon as the command is com-
plete. If used with the -n flag, writes are refused, but telegrams are still saved.
If you have designated yourself as a helper, you will still be marked on the finger(1) output as a helper while you are running amin but
people doing ``write help'' will not be connected to you, even if you have the helper flag set to ``Y''.
AUTHOR
Jan Wolter
FILES
/etc/wrttmp to find message permissions
/etc/utmp to find user
SEE ALSO
mesg(1), finger(1), write(1), huh(1).
7th Edition July 1, 1991 AMIN(1)