08-28-2002
First, I think it good that we have a link to the open group. We stayed pretty much on the high road and that's good for everyone, including us.
Second, I agree with jj25 that we should modify the open group post to include mention of the version 3 link. I just visited that link. I did not know that the standard was available via the web. I'll bet that a lot of other people didn't know that either. That was a very useful link. Thanks, jj25.
7 More Discussions You Might Find Interesting
1. Solaris
Hi there
I have a backup script that runs every night and for some reason ive been getting in in the morning and the process has died, Is there any way I can tell when it died? if not .....would anybody recommend some scripting that i could do that would be able to tell me this information
... (3 Replies)
Discussion started by: hcclnoodles
3 Replies
2. UNIX for Dummies Questions & Answers
I am using SunOS 5.7
I have installed Python 2.5 via make install
Without going into details, I'd like to uninstall it and replace it with an earlier version. Maybe as far back as 2.2.3. Unfortuantely, make uninstall gives me Don't know how to make target 'uninstall'. This is thematically... (2 Replies)
Discussion started by: Dbecker
2 Replies
3. Shell Programming and Scripting
two things.
why doesn't the 'die' message get displayed - "Error: release log directory creation failed..."?
why does the script name and line number get displayed despite the inclusion of a '\n'. apparently adding a newline prevents this from happening.
if (! -d "$logdir") {
use... (4 Replies)
Discussion started by: mjays
4 Replies
4. Shell Programming and Scripting
I have a perl program that I want to read from a file passed as an argument or from a pipe. If their is no pipe or arguments, I want it to output a help message. I am stuck on how to prevent perl from reading from the keyboard if it isn't fed any file names or data from a pipe. The only things I... (4 Replies)
Discussion started by: ilikecows
4 Replies
5. Post Here to Contact Site Administrators and Moderators
First of all, I want to thank everyone who runs this forum for the fine job they've done. While I myself have not yet had any need for help, I have enjoyed and learned while helping others.
Due diligence disclaimer: I searched for a discussion on this issue, using "tynt" and "copy paste", but... (11 Replies)
Discussion started by: alister
11 Replies
6. Shell Programming and Scripting
Hi,
I will ftp aroung 80 files after connecting to an FTP Server. But after 2 minutes of connection, it is timed out and connection is dying. Server had a 2 minute connection timeout if connection is idle. But my question, Isn't tranfering files not considered as an activity. Is the connection... (7 Replies)
Discussion started by: vasuarjula
7 Replies
7. What is on Your Mind?
Update: UserCP Screeching Frog 0.7641 - Changed Live Chat to Live Updates
In this version of the UserCP, I have changed "Live Chat" to "Live Updates" by disabling the ability to post in the "live chat" area and changed the name to "Live Updates"
The reason for this change is that experienced... (6 Replies)
Discussion started by: Neo
6 Replies
link(1) General Commands Manual link(1)
NAME
link, unlink - Creates an additional directory entry for an existing file
SYNOPSIS
link file1 file2
unlink file
STANDARDS
Interfaces documented on this reference page conform to industry standards as follows:
link: XCU5.0
unlink: XCU5.0
Refer to the standards(5) reference page for more information about industry standards and associated tags.
DESCRIPTION
The link command performs the link() system call to create an additional directory entry for an existing file, file1. In effect, the
underlying file then has two names, file1 and file2 (either of these arguments can be a pathname). The old and new entries share equal
access rights to the underlying file.
The unlink command performs the unlink() system call to remove a link to file created by link. The unlink command removes the directory
entry specified by the file parameter and, if the entry is a hard link, decrements the link count of the file referenced by the link.
You should be familiar with the link() and unlink() system calls before you use these commands.
The link and unlink commands do not issue error messages when the associated system call is unsuccessful.
NOTES
The link and unlink commands cannot be used to link and unlink directories.
EXIT STATUS
The link and unlink commands both exit with the following: The link() or unlink() system call succeeded. Too few or too many arguments
specified. The link() or unlink() system call failed.
SEE ALSO
Commands: fsck(8), ln(1)
Functions: link(2), unlink(2)
link(1)