summaryrefslogtreecommitdiffstats
path: root/usr.sbin/chown
Commit message (Collapse)AuthorAgeFilesLines
* Add a "-x" option to chown(8)/chgrp(1) similar to the same option ingavin2010-02-213-13/+26
| | | | | | | | | du(1), cp(1) etc, to prevent the crossing of mountpoints whilst using the commands recursively. PR: bin/130855 Submitted by: keramida MFC after: 1 month
* The last big commit: let usr.sbin/ use WARNS=6 by default.ed2010-01-021-2/+0
|
* In preparation for raising NGROUPS and NGROUPS_MAX, change basebrooks2009-06-191-2/+6
| | | | | | | | | | | | | | | | | | | | | | system callers of getgroups(), getgrouplist(), and setgroups() to allocate buffers dynamically. Specifically, allocate a buffer of size sysconf(_SC_NGROUPS_MAX)+1 (+2 in a few cases to allow for overflow). This (or similar gymnastics) is required for the code to actually follow the POSIX.1-2008 specification where {NGROUPS_MAX} may differ at runtime and where getgroups may return {NGROUPS_MAX}+1 results on systems like FreeBSD which include the primary group. In id(1), don't pointlessly add the primary group to the list of all groups, it is always the first result from getgroups(). In principle the old code was more portable, but this was only done in one of the two places where getgroups() was called to the overall effect was pointless. Document the actual POSIX requirements in the getgroups(2) and setgroups(2) manpages. We do not yet support a dynamic NGROUPS, but we may in the future. MFC after: 2 weeks
* Fix punctuation.trhodes2009-04-011-1/+1
| | | | | PR: 132834 Submitted by: "Alan R. S. Bueno" <alan.bsd@gmail.com>
* Expand *n't contractions.ru2005-02-132-2/+2
|
* Sort sections.ru2005-01-181-5/+5
|
* Added the EXIT STATUS section where appropriate.ru2005-01-172-2/+2
|
* Per letter dated July 22, 1999, delete clause 3 from code directlyimp2004-08-073-12/+0
| | | | from Berkeley.
* Use uid_t.charnier2003-09-071-3/+4
|
* Erase whitespace at EOL.ru2003-05-221-1/+1
| | | | Approved by: re (blanket)
* Use __FBSDID over rcsid[]. Protect copyright[] where needed.obrien2003-05-031-3/+2
|
* Similar to chmod(1); make -v -v mean very verbose and showjohan2003-04-254-6/+44
| | | | | | | | the old and new uid/gid. PR: 41341 Submitted by: Edward Brocklesby <nighthawk@unrealircd.com> Reviewed by: bde@ (an older version)
* style.Makefile(5)obrien2003-04-041-1/+2
|
* Reword the description of -R a bit and add a note about being carefulkeramida2003-01-261-2/+6
| | | | | | | when -R is combined with patterns that might match ".." (like ".*"). PR: 46415 Submitted by: Gary W. Swearingen <swear@attbi.com>
* Use basename(3).obrien2002-12-301-3/+2
|
* Fix a spelling mistake.dwmalone2002-07-171-1/+1
| | | | | | PR: 40695 Submitted by: Maxim Maximov <mcsi@agava.com> MFC after: 1 week
* The .Nm utilitycharnier2002-07-141-4/+5
|
* Kill __P(), use ANSI C function declarations, remove local prototype for main,jmallett2002-06-301-21/+14
| | | | and add a __FBSDID() while I'm here.
* In the SUPPORT_DOT case, warn that seperation with a period is deprecated.jmallett2002-06-271-0/+1
| | | | | | | | | | | In -STABLE, this is default, in -CURRENT it is not, which leads to many a headache for a user coming to -CURRENT without remembering this fact. It is one of the POLA violations we have not avoided by preparing the users for it appopriately. Therefore, a warnx(3) is added here, explicitly to be MFC'd shortly to start the re-education process rolling. Reviewed by: General murmurs of approval in that IRC channel. MFC after: 3 days
* Don't exit immediately if an error occurs, continue but exit non-zero.tjr2002-06-021-5/+9
|
* mdoc(7) police: removed an extra .Op call.ru2002-05-301-1/+1
|
* chown(8) was not describing symlinks correctly, fixed.trhodes2002-04-091-3/+6
| | | | | | PR: 36447 No objections from: ru MFC after: 3 days
* Add prototypes for main() so that these programs compile with -Werrorluigi2001-12-141-0/+1
| | | | | | | | | | | | (which somehow now seems to be the default for compiling -current). This error popped up while doing a PicoBSD cross-compile on a 4.3-ish system, it may well be that there are other apps which have similar problems, but I did not spot them as they are not included in my picobsd config. Whether adding prototypes for main() is the correct solution or not I have no idea, a request to -current on the matter went basically unanswered. Those who have better ideas are welcome to back this out and replace it with the correct fix.
* Clean up, WARNSify, unbreak -v option handling.ru2001-09-132-52/+52
|
* If a sentence starts inside parenthesis, it should end insidedd2001-09-111-1/+1
| | | | parenthesis.
* mdoc(7) police: utilize the new .Ex macro.ru2001-08-152-7/+3
|
* Perform a major cleanup of the usr.sbin Makefiles.obrien2001-07-201-1/+1
| | | | | These are not perfectly in agreement with each other style-wise, but they are orders of orders of magnitude more consistent style-wise than before.
* mdoc(7) police: removed HISTORY info from the .Os call.ru2001-07-102-2/+2
|
* Starting with 5.0-R, do not support `.' as a owner / group delimiter.obrien2001-05-311-1/+0
|
* Fixed the bug from the previous revision.ru2001-05-311-1/+1
| | | | | | | | | | | | | | | ``chown -h owner symlink'' did not set the symlink's owner if the file the symlink points to already had that owner: # ls -l alink afile -rw-r--r-- 1 nobody ru 0 May 31 14:14 afile lrwxr-xr-x 1 root ru 5 May 31 14:14 alink -> afile # ./chown -h -v nobody alink # ls -l alink afile -rw-r--r-- 1 nobody ru 0 May 31 14:14 afile lrwxr-xr-x 1 root ru 5 May 31 14:14 alink -> afile Similarly for chgrp(1) and chmod(1).
* Follow symbolic links named as command line arguments if run without -R.ru2001-05-281-2/+3
| | | | | | | | | | | | | | This is required by symlink(7), ``Commands not traversing a file tree'' subsection, third paragraph: : It is important to realize that this rule includes commands which may : optionally traverse file trees, e.g. the command ``chown file'' is : included in this rule, while the command ``chown -R file'' is not. For chown(8) and chgrp(1), this is also is compliance with the latest POSIX 1003.1-200x draft. MFC after: 1 week
* Make it clear that -P is the default.ru2001-05-252-0/+2
| | | | PR: docs/27629
* - Backout botched attempt to introduce MANSECT feature.ru2001-03-261-2/+1
| | | | - MAN[1-9] -> MAN.
* mdoc(7) police: use the default ``file ...'' feature of the .Ar macro.ru2001-02-131-1/+1
|
* mdoc(7) police: split punctuation characters + misc fixes.ru2001-02-011-2/+2
|
* mdoc(7) police: use the new features of the Nm macro.ru2000-11-202-3/+3
|
* Initialize vflag like the rest (not necessary, but this keeps it together)peter2000-07-291-1/+4
| | | | Optimize out chown(2) syscalls if there is no change in uid or gid.
* Somehow I didn't get all the "-v" code commited.obrien2000-03-083-10/+7
| | | | | | | Submitted by: Arindum Mukerji <rmukerji@execpc.com> Approved by: JKH Make the manpage more style(9) complient.
* Revert rev 1.3. chown(8)-like functionality has been added to mknod(8)obrien2000-01-061-6/+1
| | | | | and MAKEDEV(8) will be changed to not use chown(8), thus removing the depdendance on a having /usr mounted.
* Install `chown' into /sbin rather than /usr/sbin as `chown' is needed byobrien1999-12-141-1/+7
| | | | | `MAKEDEV'. And one might need to `MAKEDEV' inorder to get a device node in order to mount /usr from.
* Add "-v".obrien1999-11-273-4/+29
|
* add .Sh DIAGNOSTICScharnier1999-10-171-5/+5
|
* space is not allowed between owner and :group.charnier1999-10-081-1/+1
|
* $Id$ -> $FreeBSD$peter1999-08-283-3/+3
|
* Add $Id$, to make it simpler for members of the translation teams tonik1999-07-121-0/+1
| | | | | | | | | | | | | | | | | track. The Id line is normally at the bottom of the main comment block in the man page, separated from the rest of the manpage by an empty comment, like so; .\" $Id$ .\" If the immediately preceding comment is a @(#) format ID marker than the the $Id$ will line up underneath it with no intervening blank lines. Otherwise, an additional blank line is inserted. Approved by: bde
* Backed out previous commit. chown(8) doesn't follow symlinks bybde1998-05-031-1/+2
| | | | | | | | | | | | | | | | | | | | | | | | default, at least in BSD. This used to be automatic, because chown(2) didn't follow symlinks. When chown(2) was changed to follow symlinks in BSD4.4, chown(8) was changed to not follow symlinks by default. The previous commit broke this. The first victim was bsd.prog.mk, which uses a plain chown in an attempt to change the ownership of the symlinks to `dm' in /usr/games. This fails when it is done before dm is installed, or messes up the ownership of dm if dm is installed. Unfixed problems: 1. When lchown(2) was implemented, chown(8) wasn't changed to implement the historical behaviour of changing ownership of symlinks. I'm not sure if it should have been. The -HLP options give more complete control, but they unfortunately don't apply unless the -R option is specified (a problem shared with other commands, e.g., cp; I guess we're supposed to use -R even for non-recursive traversals). 2. If we implement the historical behaviour, then -h would become a no-op and should be left undocumented. 3. The man page suggests that without option -h, all symlinks (to files specified in the command line?) are followed. It's not clear what "the file" is. These bugs were introduced when -h was documented. 4. The correct interaction of -h with the other flags is not clear.
* Don't ignore symbolic links in the absence of -h, -H or -L options.helbig1998-05-021-2/+1
| | | | Instead change the user ID/group ID of the file that the link points to.
* Allow -R and -h to be combined as long as no symlink-following flagsjkh1998-03-091-2/+2
| | | | | are also requested. Submitted by: Andre Albsmeier <andre.albsmeier@mchp.siemens.de>
* Chown(8) compiled with -DSUPPORT_DOT (backward compatibility) doeswosch1997-09-211-6/+6
| | | | | | | | | | first check for a `.' and then for `:' as a delimiter. Usernames with a dot will fail. # chown r.r:bin /tmp/bla chown: r:bin: illegal group name Fix: first check for a `:' and then for a `.'
* Cosmetic in man page. Sync usage() with man page.charnier1997-09-043-19/+25
|
OpenPOWER on IntegriCloud