The OpenNET Project / Index page

[ новости /+++ | форум | wiki | теги | ]

Интерактивная система просмотра системных руководств (man-ов)

 ТемаНаборКатегория 
 
 [Cписок руководств | Печать]

link (2)
  • link (1) ( Solaris man: Команды и прикладные программы пользовательского уровня )
  • link (1) ( FreeBSD man: Команды и прикладные программы пользовательского уровня )
  • link (1) ( Русские man: Команды и прикладные программы пользовательского уровня )
  • link (1) ( Linux man: Команды и прикладные программы пользовательского уровня )
  • link (1) ( POSIX man: Команды и прикладные программы пользовательского уровня )
  • link (2) ( Solaris man: Системные вызовы )
  • >> link (2) ( FreeBSD man: Системные вызовы )
  • link (2) ( Русские man: Системные вызовы )
  • link (2) ( Linux man: Системные вызовы )
  • link (3) ( Solaris man: Библиотечные вызовы )
  • link (3) ( POSIX man: Библиотечные вызовы )
  • link (5) ( FreeBSD man: Форматы файлов )
  • Ключ link обнаружен в базе ключевых слов.

  • BSD mandoc
     

    NAME

    
    
    link
    
     - make a hard file link
    
     
    

    LIBRARY

    Lb libc
    
     
    

    SYNOPSIS

       #include <unistd.h>
    int link (const char *name1 const char *name2);
     

    DESCRIPTION

    The link ();
    system call atomically creates the specified directory entry (hard link) Fa name2 with the attributes of the underlying object pointed at by Fa name1 . If the link is successful: the link count of the underlying object is incremented; Fa name1 and Fa name2 share equal access and rights to the underlying object.

    If Fa name1 is removed, the file Fa name2 is not deleted and the link count of the underlying object is decremented.

    The object pointed at by the Fa name1 argument must exist for the hard link to succeed and both Fa name1 and Fa name2 must be in the same file system. The Fa name1 argument may not be a directory.  

    RETURN VALUES

    Rv -std link  

    ERRORS

    The link ();
    system call will fail and no link will be created if:

    Bq Er ENOTDIR
    A component of either path prefix is not a directory.
    Bq Er ENAMETOOLONG
    A component of either pathname exceeded 255 characters, or entire length of either path name exceeded 1023 characters.
    Bq Er ENOENT
    A component of either path prefix does not exist.
    Bq Er EOPNOTSUPP
    The file system containing the file named by Fa name1 does not support links.
    Bq Er EMLINK
    The link count of the file named by Fa name1 would exceed 32767.
    Bq Er EACCES
    A component of either path prefix denies search permission.
    Bq Er EACCES
    The requested link requires writing in a directory with a mode that denies write permission.
    Bq Er ELOOP
    Too many symbolic links were encountered in translating one of the pathnames.
    Bq Er ENOENT
    The file named by Fa name1 does not exist.
    Bq Er EEXIST
    The link named by Fa name2 does exist.
    Bq Er EPERM
    The file named by Fa name1 is a directory.
    Bq Er EPERM
    The file named by Fa name1 has its immutable or append-only flag set, see the chflags(2) manual page for more information.
    Bq Er EPERM
    The parent directory of the file named by Fa name2 has its immutable flag set.
    Bq Er EXDEV
    The link named by Fa name2 and the file named by Fa name1 are on different file systems.
    Bq Er ENOSPC
    The directory in which the entry for the new link is being placed cannot be extended because there is no space left on the file system containing the directory.
    Bq Er EDQUOT
    The directory in which the entry for the new 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.
    Bq Er EIO
    An I/O error occurred while reading from or writing to the file system to make the directory entry.
    Bq Er EROFS
    The requested link requires writing in a directory on a read-only file system.
    Bq Er EFAULT
    One of the pathnames specified is outside the process's allocated address space.

     

    SEE ALSO

    chflags(2), readlink(2), symlink(2), unlink(2)  

    STANDARDS

    The link ();
    system call is expected to conform to St -p1003.1-90 .  

    HISTORY

    The link ();
    function appeared in AT&T System v7 .

    The link ();
    system call traditionally allows the super-user to link directories which corrupts the file system coherency. This implementation no longer permits it.


     

    Index

    NAME
    LIBRARY
    SYNOPSIS
    DESCRIPTION
    RETURN VALUES
    ERRORS
    SEE ALSO
    STANDARDS
    HISTORY


    Поиск по тексту MAN-ов: 




    Спонсоры:
    PostgresPro
    Inferno Solutions
    Hosting by Hoster.ru
    Хостинг:

    Закладки на сайте
    Проследить за страницей
    Created 1996-2022 by Maxim Chirkov
    Добавить, Поддержать, Вебмастеру