The "find" is probably not hung. It will take time to search from root down. The error messages "find: cannot open" are because you are not logged in as "root" and do not have permission look at some directories. This is harmless because you could not have created a file in one of those directories. If you really don't know where you created the file, the find from root will find it eventually.
I need help in forming a script to copy files from one location which has a sub directory structure to another location with similar sub directory structure,
say location 1,
/home/rick/tmp_files/1-12/00-25/
here 1-12 are the number of sub directories under tmp_files and 00-25 are sub... (1 Reply)
Hi all
I need to copy the entire contents of one file into an existing file at a specific location. I know the exact line number where I need to put it. It appears I would use either sed or awk to do this, but I have been unsuccessful so far:
File A
line 1
line 2
line 3
line 4
... (6 Replies)
Create a script that copies files from one specified directory to another specified directory, in the order they were created in the original directory between specified times. Copy the files at a specified interval. (2 Replies)
Hi,
I am logging to a linux server through a user "user1" in /home directory.
There is a script in a directory in 'root' for which all permissions are available including the directory. This script when executed creates a file in the directory.
When the script is added to crontab, on... (1 Reply)
I have file file1.txt in location 'loc1'. Now i want a copy of this file in location 'loc2' with a new file called test.txt.
Please help me how to do this in shell script. (1 Reply)
Hi
This is my third past and very impressed with previous post replies
Hoping the same for below query
How to find a existing file location and directory location in solaris box (1 Reply)
A) I would like to achive following actions using shell script. can someone help me with writing the shell script
1) Go to some dir ( say /xyz/logs ) and then perform find operation in this dir and list of subdir using
find . -name "*" -print | xargs grep -li 1367A49001CP0162 >... (1 Reply)
Hello.
I want to to backup some "default:" values from a file do some other job and after restore that "default:" values back.
The problem is that the source and destination file has a lot of default: strings in it but with different values...
So..
Here is an example:
A part of my source... (6 Replies)
This question could be specific to the site subdivx.com In the past, I've been able to download a file following location using cURL but there is something about subdivx.com that's different and can't figure out how to get it to work.
I tried the following directly in the terminal with no... (5 Replies)
Discussion started by: MoonD
5 Replies
LEARN ABOUT OSF1
lndir
lndir(1X)lndir(1X)NAME
lndir - create a shadow directory of symbolic links to another directory tree
SYNOPSIS
lndir fromdir [todir]
DESCRIPTION
lndir makes a shadow copy todir of a directory tree fromdir, except that the shadow is not populated with real files but instead with sym-
bolic links pointing at the real files in the fromdir directory tree. This is usually useful for maintaining source code for different
machine architectures. You create a shadow directory containing links to the real source which you will have usually NFS mounted from a
machine of a different architecture, and then recompile it. The object files will be in the shadow directory, while the source files in
the shadow directory are just symlinks to the real files.
This has the advantage that if you update the source, you need not propagate the change to the other architectures by hand, since all
source in shadow directories are symlinks to the real thing: just cd to the shadow directory and recompile.
The todir argument is optional and defaults to the current directory. The fromdir argument may be relative (e.g., ../src) and is relative
to todir (not the current directory).
Note that RCS, SCCS, and CVS.adm directories are not shadowed.
Note also that if you add files, you must run lndir again. Deleting files is difficult because the symlinks will point to places that no
longer exist.
BUGS
The patch routine needs to be able to change the files. You should never run patch from a shadow directory.
Use a command like the following to clear out all files before you can relink (if the fromdir has been moved, for instance):
find todir -type l -print | xargs rm
The following command will find all files that are not directories:
find . ! -type d -print
lndir(1X)