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
LEARN ABOUT ULTRIX
symlink
symlink(2) System Calls Manual symlink(2)
Name
symlink - make symbolic link to a file
Syntax
symlink(name1, name2)
char *name1, *name2;
Description
A symbolic link name2 is created to name1 (name2 is the name of the file created, name1 is the string used in creating the symbolic link).
Either name can be an arbitrary path name. The files need not be on the same file system.
Return Values
Upon successful completion, a zero (0) value is returned. If an error occurs, the error code is stored in errno, and a -1 value is
returned.
Diagnostics
The symbolic link is made, unless one or more of the following are true:
[ENOTDIR] A component of the name2 prefix is not a directory.
[EEXIST] The name2 already exists.
[EACCES] A component of the name2 path prefix denies search permission.
[EROFS] The file name2 would reside on a read-only file system.
[EFAULT] The name1 or name2 points outside the process's allocated address space.
[ELOOP] Too many symbolic links were encountered in translating the pathname.
[ENAMETOOLONG] A component of either pathname exceeded MAXNAMELEN characters, or the entire length of either pathname exceeded MAXPATHNAME
characters.
[ENOENT] The named file does not exist.
[EIO] An I/O error occurred while making the directory entry for name2, or allocating the inode for name2, or writing out the link
contents of name2.
[ENOSPC] The directory in which the entry for the new symbolic link is being placed cannot be extended, because there is no space
left on the file system containing the directory.
[ENOSPC] The new symbolic link cannot be created, because there is no space left on the file system that will contain the symbolic
link.
[ENOSPC] There are no free inodes on the file system on which the symbolic link is being created.
[EDQUOT] The directory in which the entry for the new symbolic link is being placed cannot be extended because the user's quota of
disk blocks on the file system containing the directory has been exhausted.
[EDQUOT] The new symbolic link cannot be created because the user's quota of disk blocks on the file system that will contain the
symbolic link has been exhausted.
[EDQUOT] The user's quota of inodes on the file system on which the user's symbolic link is being created has been exhausted.
[EIO] An I/O error occurred while making the directory entry or allocating the inode.
[ETIMEDOUT] A connect request or remote file operation failed, because the connected party did not properly respond after a period of
time that is dependent on the communications protocol.
See Also
ln(1), link(2), readlink(2), stat(2), unlink(2)
symlink(2)