Return to rename.3 CVS log

Up to [CSRG BSD Unix] / 43BSDTahoe / man / man3f

Annotation of 43BSDTahoe/man/man3f/rename.3, revision 1.1

1.1     ! root        1: .\" Copyright (c) 1983 Regents of the University of California.
        !             2: .\" All rights reserved.  The Berkeley software License Agreement
        !             3: .\" specifies the terms and conditions for redistribution.
        !             4: .\"
        !             5: .\"    @(#)rename.3f   6.1 (Berkeley) 5/15/85
        !             6: .\"
        !             7: .TH RENAME 3F "May 15, 1985"
        !             8: .UC 5
        !             9: .SH NAME
        !            10: rename \- rename a file
        !            11: .SH SYNOPSIS
        !            12: .B integer function rename (from, to)
        !            13: .br
        !            14: .B character*(*) from, to
        !            15: .SH DESCRIPTION
        !            16: .I From
        !            17: must be the pathname of an existing file.
        !            18: .I To
        !            19: will become the new pathname for the file.
        !            20: If
        !            21: .I to
        !            22: exists, then both
        !            23: .I from
        !            24: and
        !            25: .I to
        !            26: must be the same type of file, and must reside on the same filesystem.
        !            27: If
        !            28: .I to
        !            29: exists, it will be removed first.
        !            30: .PP
        !            31: The returned value will be 0 if successful; a system error code otherwise.
        !            32: .SH FILES
        !            33: .ie \nM /usr/ucb/lib/libU77.a
        !            34: .el /usr/lib/libU77.a
        !            35: .SH "SEE ALSO"
        !            36: rename(2), perror(3F)
        !            37: .SH BUGS
        !            38: Pathnames can be no longer than MAXPATHLEN as defined in
        !            39: .RI < sys/param.h >.

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.