05-04-2005
dynamic update of docs
hi,
i have some files which r link to the directory
and to refer these files there is a html link on my web page
At the moment there are only 2 active links. I created a soft link to the original source at very first time, the owner of these documents can change the content and update anytime after that . As long as they don't change the file name, the updated info will reflect immediately on the web.
my problem is : i would like to create a dymamic update from original source without creating the soft link at the first time, which means everytime the document owner check in their files in the following directory, it immediately created an active link on the web. Eventually all the cell names that I already created on the html table will be active when the owner checkin their .doc files in the directory structure below.
plz help
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I recently coded a typical ftp script looking like
ftp -n $hostname <<
user $user $pass
<commands..>
quit
!
I know the code fails when you try to indent it like:
ftp $hostname <<
user $user $pass
<commands..>
quit
!
Just for the sake of neat code, is there a... (4 Replies)
Discussion started by: yongho
4 Replies
2. AIX
hi gurus,
i am new to the AIX 5.3, if some one can provide the document related to the full command list with help, and other system admin related docs, it would be very helpful for me.
With Best Regards
Deepak (1 Reply)
Discussion started by: deepaksachdeva
1 Replies
3. HP-UX
hi everyone
I m plannin to study the HP-UX
can anyone supply me with some docs or ebooks or any links for free download.
thanks in advance (4 Replies)
Discussion started by: livemyway
4 Replies
4. Shell Programming and Scripting
currently it has the following:
bdumpN=`ll /home/apps/oracle/admin/DBprod/bdump/DBprod_j* | grep "$Cdate" | wc -l`
If I pass the DBname, I would not have to hardcode it in the script...
I can capture the database name by adding the following:
DBname=$1
The problem is, I have been unable... (2 Replies)
Discussion started by: mr_manny
2 Replies
5. Shell Programming and Scripting
Hello Guys,
I'm new to Shell scripting, and i need someone to help me with this issue:
I'm trying to do a dynamic update query on Sysbase database table using shell script.
Lets say, the Update query is "update Table set id=X" , where X is dynamic value for the loop index.
If the loop is... (10 Replies)
Discussion started by: Alaeddin
10 Replies
6. Shell Programming and Scripting
Hi ,
Im not into much of a perl and now I have work on some perl scripts which
use commands like Config::Tiny, Use Data:Dumper etc.
Can any one provide insight into these commands or any documents are also more than welcomed.
Thanks, (2 Replies)
Discussion started by: rimser9
2 Replies
7. UNIX for Advanced & Expert Users
I have a file that reads File (X.txt)
Contents of record 1:
rdrDESTINATION_ADDRESS (String) "91 971502573813"
rdrDESTINATION_IMSI (String) "000000000000000"
rdrORIGINATING_ADDRESS (String) "d0 movies"
rdrORIGINATING_IMSI (String) "000000000000000"
rdrTRAFFIC_EVENT_TIME... (0 Replies)
Discussion started by: magedfawzy
0 Replies
8. Solaris
Did you ever wonder what Oracle did with the Sun Documentation? It's still out there but it's not that easy to find even with their new wiz-bang "My Oracle Support" page. I found this site today with links directly to the documentation.
I hope everyone find this useful:
Where'd the Docs Go?... (2 Replies)
Discussion started by: bluescreen
2 Replies
9. Shell Programming and Scripting
Hi All,
I am newbie here and request your assistance.
I have a service running on public ip, but since I have a dynamic IP it keeps on changing and every time I need to manually get the new ip and add to the config file and restart the service. This has become bit time consuming.
Hence, I... (4 Replies)
Discussion started by: Shaan_Shaan
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