rfio_unlink man page

RFIO_UNLINK(3)              Rfio Library Functions              RFIO_UNLINK(3)

[1mNAME[0m
      rfio_unlink - remove a file entry

[1mSYNOPSIS[0m
      [1m#include <sys/types.h>[0m
      [1m#include "rfio_api.h"[0m

      [1mint rfio_unlink (const char *[4m[22mpath[24m[1m);[0m
      [1mint rfio_munlink (const char *[4m[22mpath[24m[1m);[0m
      [1mint rfio_munlink_reset ();[0m
      [1mint rfio_unend ();[0m

[1mDESCRIPTION[0m
      [1mrfio_unlink [22mremoves a file entry.

      [4mpath[24m   specifies the logical pathname relative to the current directory
             or the full pathname.

      [1mrfio_munlink [22mis identical to [1mrfio_unlink [22mbut keeps the connection  open
      to  the  server  unless there are more than MAXMCON connections already
      opened. This is useful when issuing a series of unlink calls.  The last
      [1mrfio_munlink [22mcall should be followed by a call to [1mrfio_unend[22m.

      [1mrfio_munlink_reset  [22mis to be used when your program is forking. In such
      a case the permanent connections opened with [1mrfio_munlink [22mbecome shared
      between the parent and the child. Use [1mrfio_munlink_reset [22mto perform the
      necessary reset and close of the socket file descriptor in  the  parent
      or  the  child  in  order  to be sure that only of them will receice an
      answer from the RFIO daemon.

      [1mrfio_munlink_reset [22mis to be used when your program is forking. In  such
      a case the permanent connections opened with [1mrfio_munlink [22mbecome shared
      between the parent and the child. Use [1mrfio_munlink_reset [22mto perform the
      necessary  reset  and close of the socket file descriptor in the parent
      or the child in order to be sure that only  of  them  will  receice  an
      answer from the RFIO daemon.

      See NOTES section below.

[1mRETURN VALUE[0m
      This  routine  returns  0  if the operation was successful or -1 if the
      operation failed. In the latter case, [1mserrno [22mis set appropriately.

[1mNOTES[0m
      Multiple  connections  using  rfio_munlink  are  thread-safe  but   not
      process-wide,  therefore  a  forked  child  cann share file descriptors
      opened with rfio_munlink by its parent. Use [1mrfio_msymlink_reset [22min such
      case.

      Multiple  connections  behaviour  is  undefined if you work in a multi-
      threaded environment and with  threads  [1mnot  [22mcreated  using  the  LCG's
      [1mCthread [22minterface.

[1mERRORS[0m
      [1mEPERM        [4m[22mpath[24m is a directory.

      [1mENOENT       [22mThe named file does not exist or is a null pathname.

      [1mEACCES       [22mSearch  permission  is  denied  on a component of the [4mpath[0m
                   prefix or write permission is denied on the parent  direc-
                   tory or the parent has the sticky bit S_ISVTX set and

                     the  effective  user  ID of the requestor does not match
                     the owner ID of the file and

                     the effective user ID of the requestor  does  not  match
                     the owner ID of the directory and

                     the file is not writable by the requestor and

                     the requestor is not super-user.

      [1mEFAULT       [4m[22mpath[24m is a NULL pointer.

      [1mENOTDIR      [22mA component of [4mpath[24m prefix is not a directory.

      [1mENAMETOOLONG [22mThe  length of [4mpath[24m exceeds [1mCA_MAXPATHLEN [22mor the length of
                   a [4mpath[24m component exceeds [1mCA_MAXNAMELEN[22m.

      [1mSENOSHOST    [22mHost unknown.

      [1mSENOSSERV    [22mService unknown.

      [1mSECOMERR     [22mCommunication error.

[1mSEE ALSO[0m
      [1mCastor_limits(4)[22m, [1mrfio_rmdir(3)[22m, [1mCthread(3)[0m

[1mAUTHOR[0m
      [1mLCG Grid Deployment [22mTeam

LCG                      $Date: 2005/03/31 13:13:04 $           RFIO_UNLINK(3)

Referenced By

rfio_munlink(3) is an alias of rfio_unlink(3).