06-05-2013
I don't know details about Tomcat, but it seems it does an lstat() then checks the attributes and aborts if not a "plain file".
Try a hard link instead - it is much harder to detect a hard-link!
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi all,
I am trying to ftp and get some symbolic link file as it is instead of getting whatever it is pointing at. Is it do-able?
Thx in advance. (11 Replies)
Discussion started by: andrec
11 Replies
2. UNIX for Dummies Questions & Answers
hello folks
how y'all doin
well i have some questions about symbolic link and hard link
hope some one answer me
i open terminal and join as root
and i wrote ln -s blah blah
then i wrote ls
i see red file called blah blah
but didn't understand what is this can some one explain and... (2 Replies)
Discussion started by: detective linux
2 Replies
3. UNIX for Dummies Questions & Answers
Hi,
I am trying to find all files in a directory that have .dat and .int extensions and removing them.
rm -f `find ${MY_DIR} -type f -name '*.dat' -o -name '*.int'`
This works fine if $MY_DIR is a regular directory.
However when $MY_DIR is a symbolic link then this command fails.
How... (1 Reply)
Discussion started by: neeto
1 Replies
4. Solaris
Hi all,
I want to create a symlink on a link file, i mean, there is a file which is actually a symlink of some version. Now i want to create one more symlink on that link file.
EX: there is a file:
uat -> version
prod -> version
Now i want to create one more link on these 'uat' and... (1 Reply)
Discussion started by: raghu.iv85
1 Replies
5. Shell Programming and Scripting
I have a script within my home folder and want to be able to execute it without using the sh command.
I know that if it was in ~/bin and executable I could do it just by typing the file name, but would rather keep it in the current file structure
I tried creating a soft link in ~/bin,... (5 Replies)
Discussion started by: Jaloopa
5 Replies
6. Shell Programming and Scripting
Hi,
I have created an empty file and a symbolic link to a file. But when I issue the following commands, I am getting the output 2.
stat -c "%s" linkfile
du -hb linkfile
Why this is happening? (4 Replies)
Discussion started by: royalibrahim
4 Replies
7. Shell Programming and Scripting
Hi Forums,
I got a little problem, I made a few modifications to the code of the launch script of a testing server(minecraft) and now updating is broken aswell as the automatic directory creation.
These Lines somehow create an endless symlink that refers to itself and I don't know how to fix... (0 Replies)
Discussion started by: Xaymar
0 Replies
8. Programming
Hello All,
I've encountered a strange behaviour from g++ that doesn't make sense to me. Maybe you can shed some light on it:
I have a bunch of source files and want to compile them and link them with a static library liba.a located in /usr/local/lib64 into an executable
Approach 1 works... (0 Replies)
Discussion started by: magelord
0 Replies
9. UNIX for Dummies Questions & Answers
Hi everybody,
I read about treads realted to this issue but they did not resovle issue given below.
Please help me resolve issue given below
I have html file under /srv/www/htdocs/actual_folder
ls actual_folder/
test.html
and following link works... (0 Replies)
Discussion started by: newbielgn
0 Replies
10. UNIX for Dummies Questions & Answers
Hi, trying to understand more about symblic link, when I compiled a program called "match" in one folder ~/downloadsoftware/I want this program to be accessible like a system command by putting a symbolic link in /usr/bin/ Not by setting the $PATH method in .bashrc at this time.
What I did is:... (4 Replies)
Discussion started by: yifangt
4 Replies
LN(1) BSD General Commands Manual LN(1)
NAME
link, ln -- make links
SYNOPSIS
ln [-Ffhinsv] source_file [target_file]
ln [-Ffhinsv] source_file ... target_dir
link source_file target_file
DESCRIPTION
The ln utility creates a new directory entry (linked file) which has the same modes as the original file. It is useful for maintaining mul-
tiple copies of a file in many places at once without using up storage for the ``copies''; instead, a link ``points'' to the original copy.
There are two types of links; hard links and symbolic links. How a link ``points'' to a file is one of the differences between a hard and
symbolic link.
The options are as follows:
-F If the target file already exists and is a directory, then remove it so that the link may occur. The -F option should be used with
either -f or -i options. If none is specified, -f is implied. The -F option is a no-op unless -s option is specified.
-h If the target_file or target_dir is a symbolic link, do not follow it. This is most useful with the -f option, to replace a symlink
which may point to a directory.
-f If the target file already exists, then unlink it so that the link may occur. (The -f option overrides any previous -i options.)
-i Cause ln to write a prompt to standard error if the target file exists. If the response from the standard input begins with the char-
acter 'y' or 'Y', then unlink the target file so that the link may occur. Otherwise, do not attempt the link. (The -i option over-
rides any previous -f options.)
-n Same as -h, for compatibility with other ln implementations.
-s Create a symbolic link.
-v Cause ln to be verbose, showing files as they are processed.
By default, ln makes hard links. A hard link to a file is indistinguishable from the original directory entry; any changes to a file are
effectively independent of the name used to reference the file. Hard links may not normally refer to directories and may not span file sys-
tems.
A symbolic link contains the name of the file to which it is linked. The referenced file is used when an open(2) operation is performed on
the link. A stat(2) on a symbolic link will return the linked-to file; an lstat(2) must be done to obtain information about the link. The
readlink(2) call may be used to read the contents of a symbolic link. Symbolic links may span file systems and may refer to directories.
Given one or two arguments, ln creates a link to an existing file source_file. If target_file is given, the link has that name; target_file
may also be a directory in which to place the link; otherwise it is placed in the current directory. If only the directory is specified, the
link will be made to the last component of source_file.
Given more than two arguments, ln makes links in target_dir to all the named source files. The links made will have the same name as the
files being linked to.
When the utility is called as link, exactly two arguments must be supplied, neither of which may specify a directory. No options may be sup-
plied in this simple mode of operation, which performs a link(2) operation using the two passed arguments.
COMPATIBILITY
The -h, -i, -n and -v options are non-standard and their use in scripts is not recommended. They are provided solely for compatibility with
other ln implementations.
The -F option is FreeBSD extention and should not be used in portable scripts.
SEE ALSO
link(2), lstat(2), readlink(2), stat(2), symlink(2), symlink(7)
STANDARDS
The ln utility conforms to IEEE Std 1003.2-1992 (``POSIX.2'').
The simplified link command conforms to Version 2 of the Single UNIX Specification (``SUSv2'').
HISTORY
An ln command appeared in Version 1 AT&T UNIX.
BSD
February 14, 2006 BSD