@Ravinder, only GNU find defaults to . as the start directory! Unix find gives error if no start directory is given - here unfortunately suppressed with 2>/dev/null
The following lists files and directories with mtime less than 7 days:
These 2 Users Gave Thanks to MadeInGermany For This Post:
Hi,
Having issues with the . parameter in the find command.
Issuing "find . -name \*.pl" gives me
find: cannot open .: No such device
I got it working by substituting . with *, so "find * -name \*.pl" gives the correct listing.
bin/test.pl
"which find" lists /bin/find.
Anybody... (7 Replies)
I have a script with a find command using xargs to copy the files found to another directory. The find command is finding the appropriate file, but it's not copying. I've checked permissions, and those are all O.K., so I'm not sure what I'm missing. Any help is greatly appreciated.
This is... (2 Replies)
Hi all,
find command not working for me in a perticular directory.The same command is working fine in any other directory.
Following is the command i issued:
find . -type f -print
my question is , is it possbile to disable a command only for a perticular directory ??...of course... (4 Replies)
put prtconf command,after show this error message:
bash-3.00# prtconf
/usr/sbin/prtconf: msize=msize + 12544^J12544: syntax error
pleae help me...........waiting for replay
by
mohan.s
Aix sysadmin
(deleted email, rule violation) (2 Replies)
Hi,
I am trying to list all the files created / modified today in a directory.
With reference to this thread,
https://www.unix.com/shell-programming-scripting/20324-capture-all-today-files.html
I have used the below command to list all the files modified today.
find . -daystart -type f... (8 Replies)
Hi ,
In /home/etc/files path ran the following command
find . -name 'ABC*' | wc -l
The output of the above command is 25 as expected
In path /home path ran the following command
find . -name '/home/etc/files/ABC*' | wc -l
The output of the abvoe command is 0 .
Why the above... (3 Replies)
Hello Friends,
I have a problem about a little script,
when i run the following two lines one by one on CLI then they work well:
/usr/bin/mkdir `perl -e 'use POSIX qw(strftime); print strftime "%Y-%m-%d",localtime(time() - 30*24*60*60);'`
find . -type f -name "fuseesb.log.*" -mtime 30... (5 Replies)
Hi All,
I am trying to select 30 days older files under current directory ,but not from subdirectory using below command.
find <Dir> -type f -mtime + 30
This command selecting all the files from current directory and also from sub directory .
I read some documention through internet ,... (1 Reply)
Hi
1st problem
--------------
i have this sed command in my unix script which replaces new line and carriage return in a line with the string "
"
the script works fine in Linux 3.0.101-0.5, but not in AIX 1 7 , the "s/\r/\
/g" replacement, replaces
all the character "r" in the file.... (3 Replies)
Can you please figure out what is the issue here
$ find . -maxdepth 1 -type f -size 0 -print
find: bad option -maxdepth
please find the OS details
$ uname -a
HP-UX g5u1216 B.11.31 U ia64 2614088426 unlimited-user license
Use code tags, thanks. (6 Replies)
Discussion started by: TomG
6 Replies
LEARN ABOUT HPUX
chroot
chroot(1M)chroot(1M)NAME
chroot - change root directory for a command
SYNOPSIS
newroot command
DESCRIPTION
The command executes command relative to the newroot. The meaning of any initial slashes in path names is changed for command and any of
its children to newroot. Furthermore, the initial working directory is newroot.
Note that command suffixes that affect input or output for the command use the original root, not the new root. For example, the command:
locates file relative to the original root, not the new one.
The command variable includes both the command name and any arguments.
The new root path name is always relative to the current root. Even if a is currently in effect, the newroot argument is relative to the
current root of the running process.
This command is restricted to users with appropriate privileges.
EXTERNAL INFLUENCES
International Code Set Support
Single- and multibyte character code sets are supported.
WARNINGS
command cannot be in a shell script.
Exercise extreme caution when referring to special files in the new root file system.
does not search the environment variable for the location of command, so the absolute path name of command must be given.
When using to establish a new environment, all absolute path name references to the file system are lost, rendering shared libraries inac-
cessible. If continued access to shared libraries is needed for correct operation, the shared libraries and the dynamic loader be copied
into the new root environment.
SEE ALSO chdir(2), chroot(2).
STANDARDS CONFORMANCE chroot(1M)