Sponsored Content
Full Discussion: HardLinks and Softlinks
Top Forums Shell Programming and Scripting HardLinks and Softlinks Post 302556442 by pludi on Sunday 18th of September 2011 02:17:01 PM
Old 09-18-2011
A soft link is an directory entry that points, by name, to another directory entry, which may or may not exist. Since it's pointing by name the target can even reside on a different mount point.

Hard links, on the other hand, are directory entries that point to an inode used by another directory entry, and is still valid if the original entry is removed. Since all access information but the name is saved with the inode, both entries will always have the same access rights, timestamps, and user/group information. Also, due to sharing the same inodes, a hard link can't cross the boundary between mount points.
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

search for hardlinks based on filename via find command

I am using command substitution into a find command in a script where I have built a menu to do a bunch of tasks within my unix account. When I choose the options for to find a file/files that have the same inode of the entered filename, ie hardlinks, nothing shows up. When I choose the appropiate... (2 Replies)
Discussion started by: hunternjb
2 Replies

2. UNIX for Dummies Questions & Answers

How to list hardlinks?

Q1: Let's say I create a hard-link bar.c in /tmp to a file foo.c which resides in /var/tmp. Is there a easy way to find out which file /tmp/bar.c hardlinks to (and vice-versa - i.e which files have got hard-linked from /var/tmp/foo.c) when one does not (and wants to) know the location of the other... (0 Replies)
Discussion started by: mahatma
0 Replies

3. AIX

IHS 6.1 on AIX - problem with symlinks / symbolic links / softlinks

Hello, I got an IHS 6.1 installed and want to publish a directory with an index of files, directories and symlinks / symbolic links / soft links, last ones being created with the usual Unix command "ln -s .... ....". In httpd.conf I've tried following for that directory: Options Indexes... (1 Reply)
Discussion started by: zaxxon
1 Replies

4. UNIX for Dummies Questions & Answers

dump/restore of a fs with 100 of millions hardlinks

Hi :-) i have a dump of a backupdisk (~540GB / ext3). The Backups have some 100 millions of hardlinks (backups are created with storeBackup). The OS is linux. A restore of a directory ended after some days with the errormessage "no memory to extend symbol table" The restore of the complete... (0 Replies)
Discussion started by: turricum
0 Replies

5. UNIX for Dummies Questions & Answers

Create softlinks between 2 different hosts

Hi I want to create softlinks, my source files and folders are placed in one server(hostname: info-1) and i want to access those files from different host(hostname :info-2). file and folder names in info-1 host. file1 folder1 Thanks, Mallik. (1 Reply)
Discussion started by: tmalik79
1 Replies

6. Solaris

Will softlinks occupy space in Solaris10

I have a pen drive1 with UFS file system and it has 43G used. It has a hell lot of soft links to other files which are located in a second pen drive2. We partitioned the file system on sun sparc machine, such that / has around 150G space.Now when we are copying the files from pen drive 1 to / on... (3 Replies)
Discussion started by: crackperl
3 Replies
UNLINK(2)							System Calls Manual							 UNLINK(2)

NAME
unlink - remove directory entry SYNOPSIS
unlink(path) char *path; DESCRIPTION
Unlink removes the entry for the file path from its directory. If this entry was the last link to the file, and no process has the file open, then all resources associated with the file are reclaimed. If, however, the file was open in any process, the actual resource recla- mation is delayed until it is closed, even though the directory entry has disappeared. RETURN VALUE
Upon successful completion, a value of 0 is returned. Otherwise, a value of -1 is returned and errno is set to indicate the error. ERRORS
The unlink succeeds unless: [ENOTDIR] A component of the path prefix is not a directory. [EINVAL] The pathname contains a character with the high-order bit set. [ENAMETOOLONG] A component of a pathname exceeded 255 characters, or an entire path name exceeded 1023 characters. [ENOENT] The named file does not exist. [EACCES] Search permission is denied for a component of the path prefix. [EACCES] Write permission is denied on the directory containing the link to be removed. [ELOOP] Too many symbolic links were encountered in translating the pathname. [EPERM] The named file is a directory and the effective user ID of the process is not the super-user. [EPERM] The directory containing the file is marked sticky, and neither the containing directory nor the file to be removed are owned by the effective user ID. [EBUSY] The entry to be unlinked is the mount point for a mounted file system. [EIO] An I/O error occurred while deleting the directory entry or deallocating the inode. [EROFS] The named file resides on a read-only file system. [EFAULT] Path points outside the process's allocated address space. SEE ALSO
close(2), link(2), rmdir(2) 4th Berkeley Distribution May 22, 1985 UNLINK(2)
All times are GMT -4. The time now is 08:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy