SHA256
1
0
forked from pool/coreutils
coreutils/coreutils-remove_kill_documentation.patch

127 lines
5.0 KiB
Diff
Raw Normal View History

---
doc/coreutils.texi | 90 -----------------------------------------------------
1 file changed, 90 deletions(-)
Index: doc/coreutils.texi
===================================================================
--- doc/coreutils.texi.orig
+++ doc/coreutils.texi
@@ -72,7 +72,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.
@@ -203,7 +202,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
- Update to 8.24: ** Bug fixes * dd supports more robust SIGINFO/SIGUSR1 handling for outputting statistics. Previously those signals may have inadvertently terminated the process. * df --local no longer hangs with inaccessible remote mounts. [bug introduced in coreutils-8.21] * du now silently ignores all directory cycles due to bind mounts. Previously it would issue a warning and exit with a failure status. [bug introduced in coreutils-8.1 and partially fixed in coreutils-8.23] * chroot again calls chroot(DIR) and chdir("/"), even if DIR is "/". This handles separate bind mounted "/" trees, and environments depending on the implicit chdir("/"). [bugs introduced in coreutils-8.23] * cp no longer issues an incorrect warning about directory hardlinks when a source directory is specified multiple times. Now, consistent with other file types, a warning is issued for source directories with duplicate names, or with -H the directory is copied again using the symlink name. * factor avoids writing partial lines, thus supporting parallel operation. [the bug dates back to the initial implementation] * head, od, split, tac, tail, and wc no longer mishandle input from files in /proc and /sys file systems that report somewhat-incorrect file sizes. * mkdir --parents -Z now correctly sets the context for the last component, even if the parent directory exists and has a different default context. [bug introduced with the -Z restorecon functionality in coreutils-8.22] * numfmt no longer outputs incorrect overflowed values seen with certain large numbers, or with numbers with increased precision. [bug introduced when numfmt was added in coreutils-8.21] * numfmt now handles leading zeros correctly, not counting them when settings processing limits, and making them optional with floating point. [bug introduced when numfmt was added in coreutils-8.21] * paste no longer truncates output for large input files. This would happen for example with files larger than 4GiB on 32 bit systems with a '\n' character at the 4GiB position. [the bug dates back to the initial implementation] * rm indicates the correct number of arguments in its confirmation prompt, on all platforms. [bug introduced in coreutils-8.22] * shuf -i with a single redundant operand, would crash instead of issuing a diagnostic. [bug introduced in coreutils-8.22] * tail releases inotify resources when unused. Previously it could exhaust resources with many files, or with -F if files were replaced many times. [bug introduced in coreutils-7.5] * tail -f again follows changes to a file after it's renamed. [bug introduced in coreutils-7.5] * tail --follow no longer misses changes to files if those files were replaced before inotify watches were created. [bug introduced in coreutils-7.5] * tail --follow consistently outputs all data for a truncated file. [bug introduced in the beginning] * tail --follow=name correctly outputs headers for multiple files when those files are being created or renamed. [bug introduced in coreutils-7.5] ** New features * chroot accepts the new --skip-chdir option to not change the working directory to "/" after changing into the chroot(2) jail, thus retaining the current wor- king directory. The new option is only permitted if the new root directory is the old "/", and therefore is useful with the --group and --userspec options. * dd accepts a new status=progress level to print data transfer statistics on stderr approximately every second. * numfmt can now process multiple fields with field range specifications similar to cut, and supports setting the output precision with the --format option. * split accepts a new --separator option to select a record separator character other than the default newline character. * stty allows setting the "extproc" option where supported, which is a useful setting with high latency links. * sync no longer ignores arguments, and syncs each specified file, or with the --file-system option, the file systems associated with each specified file. * tee accepts a new --output-error option to control operation with pipes and output errors in general. ** Changes in behavior * df no longer suppresses separate exports of the same remote device, as these are generally explicitly mounted. The --total option does still suppress duplicate remote file systems. [suppression was introduced in coreutils-8.21] * mv no longer supports moving a file to a hardlink, instead issuing an error. The implementation was susceptible to races in the presence of multiple mv instances, which could result in both hardlinks being deleted. Also on case insensitive file systems like HFS, mv would just remove a hardlinked 'file' if called like `mv file File`. The feature was added in coreutils-5.0.1. * numfmt --from-unit and --to-unit options now interpret suffixes as SI units, and IEC (power of 2) units are now specified by appending 'i'. * tee will exit early if there are no more writable outputs. * tee does not treat the file operand '-' as meaning standard output any longer, for better conformance to POSIX. This feature was added in coreutils-5.3.0. * timeout --foreground no longer sends SIGCONT to the monitored process, which was seen to cause intermittent issues with GDB for example. ** Improvements * cp,install,mv will convert smaller runs of NULs in the input to holes, and cp --sparse=always avoids speculative preallocation on XFS for example. * cp will read sparse files more efficiently when the destination is a non regular file. For example when copying a disk image to a device node. * mv will try a reflink before falling back to a standard copy, which is more efficient when moving files across BTRFS subvolume boundaries. * stat and tail now know about IBRIX. stat -f --format=%T now reports the file system type, and tail -f uses polling for files on IBRIX file systems. * wc -l processes short lines much more efficiently. * References from --help and the man pages of utilities have been corrected in various cases, and more direct links to the corresponding online documentation are provided. - Patches adapted because of changed sources: coreutils-disable_tests.patch coreutils-i18n.patch coreutils-misc.patch coreutils-ocfs2_reflinks.patch coreutils-remove_hostname_documentation.patch coreutils-remove_kill_documentation.patch coreutils-skip-gnulib-test-tls.patch coreutils-tests-shorten-extreme-factor-tests.patch sort-keycompare-mb.patch - Patches removed because they're included in 8.24: coreutils-chroot-perform-chdir-unless-skip-chdir.patch coreutils-df-doc-df-a-includes-duplicate-file-systems.patch coreutils-df-improve-mount-point-selection.patch coreutils-df-show-all-remote-file-systems.patch coreutils-df-total-suppress-separate-remotes.patch coreutils-doc-adjust-reference-to-info-nodes-in-man-pages.patch coreutils-fix_false_du_failure_on_newer_xfs.patch coreutils-fix-man-deps.patch coreutils-tests-aarch64-env.patch coreutils-tests-make-inotify-rotate-more-robust-and-efficient.patch coreutils-tests-rm-ext3-perf-increase-timeout.patch OBS-URL: https://build.opensuse.org/package/show/Base:System/coreutils?expand=0&rev=262
2015-07-09 17:40:19 +02:00
* Numeric operations:: factor numfmt seq
* File permissions:: Access modes
@@ -448,10 +446,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
@@ -16799,90 +16793,6 @@ the exit status of @var{command} otherwi
@end display
-@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