forked from pool/coreutils
e7f4664e8f
- update to 9.3:
Bug fixes:
* cp --reflink=auto (the default), mv, and install
will again fall back to a standard copy in more cases.
Previously copies could fail with permission errors on
more restricted systems like android or containers etc.
[bug introduced in coreutils-9.2]
* cp --recursive --backup will again operate correctly.
Previousy it may have issued "File exists" errors when
it failed to appropriately rename files being replaced.
[bug introduced in coreutils-9.2]
* date --file and dircolors will now diagnose a failure to read a file.
Previously they would have silently ignored the failure.
[This bug was present in "the beginning".]
* md5sum --check again correctly prints the status of each file checked.
Previously the status for files was printed as 'OK' once any file had passed.
This also applies to cksum, sha*sum, and b2sum.
[bug introduced in coreutils-9.2]
* wc will now diagnose if any total counts have overflowed.
[This bug was present in "the beginning".]
* `wc -c` will again correctly update the read offset of inputs.
Previously it deduced the size of inputs while leaving the offset unchanged.
[bug introduced in coreutils-8.27]
* Coreutils programs no longer fail for timestamps past the year 2038
on obsolete configurations with 32-bit signed time_t, because the
build procedure now rejects these configurations.
[This bug was present in "the beginning".]
Changes in behavior:
* 'cp -n' and 'mv -n' now issue an error diagnostic if skipping a file,
to correspond with -n inducing a nonzero exit status as of coreutils 9.2.
Similarly 'cp -v' and 'mv -v' will output a message for each file skipped
due to -n, -i, or -u.
New features:
* cp and mv now support --update=none to always skip existing files
in the destination, while not affecting the exit status.
This is equivalent to the --no-clobber behavior from before v9.2.
- drop fix-reflink-fallback.patch (upstream).
- add coreutils-tests-skip-cpuinfo-replaced.patch: avoid FP test failure.
OBS-URL: https://build.opensuse.org/request/show/1080971
OBS-URL: https://build.opensuse.org/package/show/Base:System/coreutils?expand=0&rev=350
127 lines
5.1 KiB
Diff
127 lines
5.1 KiB
Diff
---
|
|
doc/coreutils.texi | 90 -----------------------------------------------------
|
|
1 file changed, 90 deletions(-)
|
|
|
|
Index: doc/coreutils.texi
|
|
===================================================================
|
|
--- doc/coreutils.texi.orig
|
|
+++ doc/coreutils.texi
|
|
@@ -76,7 +76,6 @@
|
|
* id: (coreutils)id invocation. Print user identity.
|
|
* install: (coreutils)install invocation. Copy files and set attributes.
|
|
* join: (coreutils)join invocation. Join lines on a common field.
|
|
-* kill: (coreutils)kill invocation. Send a signal to processes.
|
|
* link: (coreutils)link invocation. Make hard links between files.
|
|
* ln: (coreutils)ln invocation. Make links between files.
|
|
* logname: (coreutils)logname invocation. Print current login name.
|
|
@@ -207,7 +206,6 @@ Free Documentation License''.
|
|
* System context:: date arch nproc uname hostid uptime
|
|
* SELinux context:: chcon runcon
|
|
* Modified command invocation:: chroot env nice nohup stdbuf timeout
|
|
-* Process control:: kill
|
|
* Delaying:: sleep
|
|
* Numeric operations:: factor numfmt seq
|
|
* File permissions:: Access modes
|
|
@@ -455,10 +453,6 @@ Modified command invocation
|
|
* stdbuf invocation:: Run a command with modified I/O buffering
|
|
* timeout invocation:: Run a command with a time limit
|
|
|
|
-Process control
|
|
-
|
|
-* kill invocation:: Sending a signal to processes.
|
|
-
|
|
Delaying
|
|
|
|
* sleep invocation:: Delay for a specified time
|
|
@@ -18628,90 +18622,6 @@ timeout -s INT 5s env --ignore-signal=IN
|
|
timeout -s INT -k 3s 5s env --ignore-signal=INT sleep 20
|
|
@end example
|
|
|
|
-@node Process control
|
|
-@chapter Process control
|
|
-
|
|
-@cindex processes, commands for controlling
|
|
-@cindex commands for controlling processes
|
|
-
|
|
-@menu
|
|
-* kill invocation:: Sending a signal to processes.
|
|
-@end menu
|
|
-
|
|
-
|
|
-@node kill invocation
|
|
-@section @command{kill}: Send a signal to processes
|
|
-
|
|
-@pindex kill
|
|
-@cindex send a signal to processes
|
|
-
|
|
-The @command{kill} command sends a signal to processes, causing them
|
|
-to terminate or otherwise act upon receiving the signal in some way.
|
|
-Alternatively, it lists information about signals. Synopses:
|
|
-
|
|
-@example
|
|
-kill [-s @var{signal} | --signal @var{signal} | -@var{signal}] @var{pid}@dots{}
|
|
-kill [-l | --list | -t | --table] [@var{signal}]@dots{}
|
|
-@end example
|
|
-
|
|
-@mayConflictWithShellBuiltIn{kill}
|
|
-
|
|
-The first form of the @command{kill} command sends a signal to all
|
|
-@var{pid} arguments. The default signal to send if none is specified
|
|
-is @samp{TERM}@. The special signal number @samp{0} does not denote a
|
|
-valid signal, but can be used to test whether the @var{pid} arguments
|
|
-specify processes to which a signal could be sent.
|
|
-
|
|
-If @var{pid} is positive, the signal is sent to the process with the
|
|
-process ID @var{pid}. If @var{pid} is zero, the signal is sent to all
|
|
-processes in the process group of the current process. If @var{pid}
|
|
-is @minus{}1, the signal is sent to all processes for which the user has
|
|
-permission to send a signal. If @var{pid} is less than @minus{}1, the signal
|
|
-is sent to all processes in the process group that equals the absolute
|
|
-value of @var{pid}.
|
|
-
|
|
-If @var{pid} is not positive, a system-dependent set of system
|
|
-processes is excluded from the list of processes to which the signal
|
|
-is sent.
|
|
-
|
|
-If a negative @var{pid} argument is desired as the first one, it
|
|
-should be preceded by @option{--}. However, as a common extension to
|
|
-POSIX, @option{--} is not required with @samp{kill
|
|
--@var{signal} -@var{pid}}. The following commands are equivalent:
|
|
-
|
|
-@example
|
|
-kill -15 -1
|
|
-kill -TERM -1
|
|
-kill -s TERM -- -1
|
|
-kill -- -1
|
|
-@end example
|
|
-
|
|
-The first form of the @command{kill} command succeeds if every @var{pid}
|
|
-argument specifies at least one process that the signal was sent to.
|
|
-
|
|
-The second form of the @command{kill} command lists signal information.
|
|
-Either the @option{-l} or @option{--list} option, or the @option{-t}
|
|
-or @option{--table} option must be specified. Without any
|
|
-@var{signal} argument, all supported signals are listed. The output
|
|
-of @option{-l} or @option{--list} is a list of the signal names, one
|
|
-per line; if @var{signal} is already a name, the signal number is
|
|
-printed instead. The output of @option{-t} or @option{--table} is a
|
|
-table of signal numbers, names, and descriptions. This form of the
|
|
-@command{kill} command succeeds if all @var{signal} arguments are valid
|
|
-and if there is no output error.
|
|
-
|
|
-The @command{kill} command also supports the @option{--help} and
|
|
-@option{--version} options. @xref{Common options}.
|
|
-
|
|
-A @var{signal} may be a signal name like @samp{HUP}, or a signal
|
|
-number like @samp{1}, or an exit status of a process terminated by the
|
|
-signal. A signal name can be given in canonical form or prefixed by
|
|
-@samp{SIG}@. The case of the letters is ignored, except for the
|
|
-@option{-@var{signal}} option which must use upper case to avoid
|
|
-ambiguity with lower case option letters.
|
|
-@xref{Signal specifications}, for a list of supported
|
|
-signal names and numbers.
|
|
-
|
|
@node Delaying
|
|
@chapter Delaying
|
|
|