1.\" Copyright (c) 1990, 1991, 1993 2.\" The Regents of the University of California. All rights reserved. 3.\" 4.\" Redistribution and use in source and binary forms, with or without 5.\" modification, are permitted provided that the following conditions 6.\" are met: 7.\" 1. Redistributions of source code must retain the above copyright 8.\" notice, this list of conditions and the following disclaimer. 9.\" 2. Redistributions in binary form must reproduce the above copyright 10.\" notice, this list of conditions and the following disclaimer in the 11.\" documentation and/or other materials provided with the distribution. 12.\" 3. All advertising materials mentioning features or use of this software 13.\" must display the following acknowledgement: 14.\" This product includes software developed by the University of 15.\" California, Berkeley and its contributors. 16.\" 4. Neither the name of the University nor the names of its contributors 17.\" may be used to endorse or promote products derived from this software 18.\" without specific prior written permission. 19.\" 20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 23.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 30.\" SUCH DAMAGE. 31.\" 32.\" from: @(#)strmode.3 8.3 (Berkeley) 7/28/94 33.\" $NetBSD: strmode.3,v 1.13 2002/02/07 07:00:32 ross Exp $ 34.\" 35.Dd July 28, 1994 36.Dt STRMODE 3 37.Os 38.Sh NAME 39.Nm strmode 40.Nd convert inode status information into a symbolic string 41.Sh LIBRARY 42.Lb libc 43.Sh SYNOPSIS 44.Fd #include \*[Lt]unistd.h\*[Gt] 45.Ft void 46.Fn strmode "mode_t mode" "char *bp" 47.Sh DESCRIPTION 48The 49.Fn strmode 50function 51converts a file 52.Fa mode 53(the type and permission information associated with an inode, see 54.Xr stat 2 ) 55into a symbolic string which is stored in the location referenced by 56.Fa bp . 57This stored string is eleven characters in length plus a trailing 58.Dv NULL . 59.Pp 60The first character is the inode type, and will be one of the following: 61.Pp 62.Bl -tag -width flag -offset indent -compact 63.It \- 64regular file 65.It a 66regular file in archive state 1 67.It A 68regular file in archive state 2 69.It b 70block special 71.It c 72character special 73.It d 74directory 75.It l 76symbolic link 77.It p 78fifo 79.It s 80socket 81.It w 82whiteout 83.It ? 84unknown inode type 85.El 86.Pp 87The next nine characters encode three sets of permissions, in three 88characters each. 89The first three characters are the permissions for the owner of the 90file, the second three for the group the file belongs to, and the 91third for the ``other'', or default, set of users. 92.Pp 93Permission checking is done as specifically as possible. 94If read permission is denied to the owner of a file in the first set 95of permissions, the owner of the file will not be able to read the file. 96This is true even if the owner is in the file's group and the group 97permissions allow reading or the ``other'' permissions allow reading. 98.Pp 99If the first character of the three character set is an ``r'', the file is 100readable for that set of users; if a dash ``\-'', it is not readable. 101.Pp 102If the second character of the three character set is a ``w'', the file is 103writable for that set of users; if a dash ``\-'', it is not writable. 104.Pp 105The third character is the first of the following characters that apply: 106.Bl -tag -width xxxx 107.It S 108If the character is part of the owner permissions and the file is not 109executable or the directory is not searchable by the owner, and the 110set-user-id bit is set. 111.It S 112If the character is part of the group permissions and the file is not 113executable or the directory is not searchable by the group, and the 114set-group-id bit is set. 115.It T 116If the character is part of the other permissions and the file is not 117executable or the directory is not searchable by others, and the ``sticky'' 118.Pq Dv S_ISVTX 119bit is set. 120.It s 121If the character is part of the owner permissions and the file is 122executable or the directory searchable by the owner, and the set-user-id 123bit is set. 124.It s 125If the character is part of the group permissions and the file is 126executable or the directory searchable by the group, and the set-group-id 127bit is set. 128.It t 129If the character is part of the other permissions and the file is 130executable or the directory searchable by others, and the ``sticky'' 131.Pq Dv S_ISVTX 132bit is set. 133.It x 134The file is executable or the directory is searchable. 135.It \- 136None of the above apply. 137.El 138.Pp 139The last character is a plus sign ``+'' if there are any alternative 140or additional access control methods associated with the inode, otherwise 141it will be a space. 142.Pp 143Archive state 1 and archive state 2 represent file system dependent 144archive state for a file. Most file systems do not retain file archive 145state, and so will not report files in either archive state. 146msdosfs will report a file in archive state 1 if it has been 147archived more recently than modified. Hierarchical storage systems 148may have multiple archive states for a file and may define archive 149states 1 and 2 as appropriate. 150.Sh SEE ALSO 151.Xr chmod 1 , 152.Xr find 1 , 153.Xr stat 2 , 154.Xr getmode 3 , 155.Xr setmode 3 156.Sh HISTORY 157The 158.Fn strmode 159function first appeared in 160.Bx 4.4 . 161