| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Submitted by: Mike Barcroft <mike@q9media.com>
|
| |
|
|
|
|
|
| |
Submitted by: Mike Barcroft <mike@q9media.com>
MFC after: 2 weeks
|
|
|
|
| |
Submitted by: Mike Barcroft <mike@q9media.com>
|
|
|
|
|
|
|
| |
and a final directory already exists.
Reviewed by: freebsd-audit
MFC after: 5 days
|
|
|
|
|
|
|
|
| |
which is also called from handle_hup(), uses stdio(3). Furthermore,
this means that calling exit(3) (via quit()) there is required to
flush the buffer write_file() was working on.
Submitted by: bde
|
|
|
|
| |
Approved by: cracauer
|
|
|
|
|
|
|
|
|
| |
signal. Fix it by adding an explicit call to summary() in terminate()
(it was previously called implicitly by exit() because summary() was
registered with atexit()). summary() is supposed to be signal-safe--
it handles SIGINFO almost exclusively--so this should be safe.
Submitted by: bde
|
|
|
|
| |
builtins (e.g., exit, strcmp).
|
|
|
|
| |
Obtained from: OpenBSD
|
| |
|
|
|
|
| |
Submitted by: Mike Barcroft <mike@q9media.com>
|
| |
|
| |
|
| |
|
|
|
|
| |
(ki_sflag).
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the !(pflag && setfile()) case for regular files unless the copy is
owned by the same user and group. These bits have already been lost
(or never gained) in the correct way. The code didn't actually lose
the bits; it depended on them being lost already (apparently in all
cases) and attempted to gain them as necessary, but it often gained
them (and sometimes collateral bits) when wrong:
- pflag && setfile() == 0 case (i.e., for a successful cp -p):
setfile() copies all the attributes as correctly as possible (as
specified by POSIX), and we sometimes messed up the up the mode by
setting it again. Also, if the file is immutable, then setting the
mode again gave spurious errors (PR 20646).
- !pflag case. If the target is created, POSIX requires it to not
have the set[ug]id bits, but we sometimes copied them from the source.
If the target already exists, POSIX requires its mode to be unchanged,
but we sometimes copied the whole mode from the source.
PR: 20646
MFC after: 4 weeks
|
| |
|
| |
|
|
|
|
|
| |
PR: 27986
Submitted by: Cyrille Lefevre <clefevre@redirect.to>
|
|
|
|
| |
Submitted by: Alexey V. Neyman <avn@any.ru>
|
|
|
|
|
| |
While we're at it, this file seems to prefer `unsigned int'
over `u_int', so go with that.
|
|
|
|
| |
MFC after: 2 weeks
|
| |
|
|
|
|
|
|
| |
PR: bin/27240
Reviewed by: GAWollman
MFC after: 2 weeks
|
|
|
|
|
| |
PR: 24804
Submitted by: Mike Meyer <mwm@mired.org>
|
| |
|
|
|
|
|
|
|
|
| |
errexit (-e) processing. This solves a problem where 'make clean' would
fail with an unspecified error in certain automake-generated makefiles.
Reviewed by: no objections from -hackers...
MFC after: 2 weeks
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
``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).
|
|
|
|
|
|
|
|
|
|
| |
in okname() in util.c and second, returning != 0 when you do have an
error from okname in two places in rcp.c.
Thanks to Garrett for the POSIX defintion of valid login and group names.
PR: bin/25757
MFC after: 3 weeks
|
| |
|
|
|
|
| |
Also use sizeof(path) in preference to PATH_MAX.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
error caused by the -1 being on the wrong side of the comparison.
This would not cause an overflow, as near as I can tell, because we
truncate later anyway. We'd just fail to get a diagnostic for 1024
and 1025 byte file names.
|
|
|
|
|
| |
Also sort declarations per style(9) (big arrays come last) while I'm
in the area.
|
|
|
|
|
|
|
| |
is changed if -h option is given.
Requested by: bde
Obtained from: NetBSD (code part)
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Reviewed by: bde
|
|
|
|
| |
PR: docs/27629
|
|
|
|
|
| |
PR: 27600
Submitted by: Iain Templeton <iain@ugh.net.au>
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC After: 1 week
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
| |
MFC After: 1 week
|