| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
in grotty(1). This makes it possible to view colorized manpages in
color.
When MANPAGER environment variable is set, use it instead of PAGER.
Why another environment variable, one might ask? With color output
enabled, both a terminal and a pager should support the ANSI color
escapes. On a supporting terminal, less(1) with option -R would be
such a pager, while "more -s" (the current default pager for man(1))
will show garbage. It means a different default pager is needed when
color output is enabled, but many people have PAGER set customary,
and it's unlikely to support ANSI color escapes, so introducing yet
another variable (MANPAGER) seemed like a good option to me:
- if MANPAGER is set, use that unconditionally;
- if you disable color support (it is by default), and don't set
MANPAGER, you get an old behavior: -P pager, $PAGER, "more -s",
in that order;
- if you enable color support (by setting MANCOLOR), and don't set
MANPAGER, we ignore PAGER which is unlikely to support ANSI color
escapes, and you get: -P pager, "less -Rs", in that order;
- you might have good reasons for different man(1) and general
purpose pagers;
- later versions of GNU man(1) support MANPAGER.
|
|
|
|
|
|
|
| |
and because col(1) mangles ANSI color escapes if enabled. Spaces
to tabs compression is now done by passing -h to grotty(1).
Discussed with: uqs
|
| |
|
| |
|
|
|
|
|
|
|
| |
If set to a numeric value, used as the width manpages should be
displayed. Otherwise, if set to a special value ``tty'', and
output is to a terminal, the pages may be displayed over the
whole width of the screen.
|
|
|
|
|
|
|
|
| |
involved.
This fixes a regression introduced with r221303.
Noticed by: jilles
|
| |
|
| |
|
|
|
|
| |
Submitted by: bcr@
|
|
|
|
|
|
|
|
|
|
|
| |
rather than at the bottom of the manpage.
- Remove an obsolete comment about SWAIT being a stale state. It was
resurrected for a different purpose in FreeBSD 5 to mark idle ithreads.
- Add a comment documenting that the SLEEP and LOCK states typically
display the name of the event being waited on with lock names being
prefixed with an asterisk and sleep event names not having a prefix.
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
idle threads). The process is displayed by default (subject to whether or
not system processes are displayed) to preserve existing behavior. The
system idle process can be hidden via the '-z' command line argument or the
'z' key while top is running. When it is hidden, top more closely matches
the behavior of FreeBSD <= 4.x where idle time was not accounted to any
process.
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
This means these features do not work as expected with multibyte characters.
This perhaps less than ideal behaviour matches printf(3) and is specified by
POSIX.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Examples:
LC_ALL=en_US.UTF-8 printf '%d\n' $(printf \'\\303\\244)
LC_ALL=en_US.ISO8859-1 printf '%d\n' $(printf \'\\344)
Both of these should print 228.
Like some other shells, incomplete or invalid multibyte characters yield the
value of the first byte without a warning.
Note that there is no general way to go back from the character code to the
character.
|
|
|
|
|
|
|
|
|
|
|
| |
Although most of the primaries and operators start with "-", they are not
options.
Examples:
find . -xyz
find . -name xyz -or bad
MFC after: 1 week
|
|
|
|
|
| |
performance-sensitive and not that useful, so I won't be merging them
before 9.0.
|
|
|
|
| |
Approved by: adrian (mentor)
|
|
|
|
| |
do not check for symbolic link.
|
| |
|
|
|
|
|
|
|
|
| |
If WITH_BSD_GREP is not set, it will be 'bsdgrep' and GNUgrep will be
'[ef]grep'. Otherwise, BSD-grep will be the grep family, and GNUgrep
will be 'gnugrep'.
Discussed with: brooks
|
|
|
|
|
|
|
|
| |
net.isr.dispatch, and about per-protocol dispatch policies.
MFC after: 3 weeks
Reviewed by: bz
Sponsored by: Juniper Networks, Inc.
|
|
|
|
|
|
| |
PR: 157286
Submitted by: Marcus Reid
MFC after: 3 days
|
|
|
|
|
|
|
|
| |
When we are operating on a symbolic link pointing to an existing
file, bail out by default, but go ahead if -f is specified.
Submitted by: arundel
MFC after: 2 weeks
|
|
|
|
|
|
| |
handle more file formats including bzip2 and xz.
MFC after: 2 weeks
|
|
|
|
| |
MFC after: 1 week
|
|
|
|
|
|
| |
Found by: codespell
Reviewed by: kaiw
MFC after: 1 week
|
|
|
|
|
|
| |
Found by: codespell
Reviewed by: alfred
MFC after: 1 week
|
|
|
|
|
|
| |
Note: these were actually bugs (printf with no format string).
Approved by: philip (mentor)
|
|
|
|
|
| |
to vfs.oldnfs.xxx and vfs.nfs.xxx respectively. This makes
the default nfs client use vfs.nfs.xxx after r221124.
|
|
|
|
|
|
|
| |
- fuser(1) writes usernames to stderr, not stdout [1]
- Add history section.
Submitted by: Pieter de Goeje <pieter@degoeje.nl> [1]
|
|
|
|
|
|
| |
use a prototype.
MFC after: 2 weeks
|
|
|
|
| |
Reviewed by: sobomax
|
|
|
|
| |
Submitted by: avg@
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
file and processes information retrieval from the running kernel via sysctl
in the form of new library, libprocstat. The library also supports KVM backend
for analyzing memory crash dumps. Both procstat(1) and fstat(1) utilities have
been modified to take advantage of the library (as the bonus point the fstat(1)
utility no longer need superuser privileges to operate), and the procstat(1)
utility is now able to display information from memory dumps as well.
The newly introduced fuser(1) utility also uses this library and able to operate
via sysctl and kvm backends.
The library is by no means complete (e.g. KVM backend is missing vnode name
resolution routines, and there're no manpages for the library itself) so I
plan to improve it further. I'm commiting it so it will get wider exposure
and review.
We won't be able to MFC this work as it relies on changes in HEAD, which
was introduced some time ago, that break kernel ABI. OTOH we may be able
to merge the library with KVM backend if we really need it there.
Discussed with: rwatson
|
|
|
|
|
| |
more real-time logging, without forcing a write(2) on every single
character.
|
|
|
|
| |
MFC after: 1 month
|
|
|
|
| |
- Sync usage() with manpage's SYNOPSIS.
|
| |
|
|
|
|
|
|
|
| |
by r221455. This includes a new "-o" option for displaying
statistics from the old NFS client/server and a slightly
different description for the "-e" option.
This is a content change.
|
|
|
|
|
|
|
| |
new NFS client/server by default, in a format compatible
with the old NFS client/server. Also add a "-o" flag that
forces nfsstat(1) to get statistics for the old NFS
client/server.
|
|
|
|
|
|
| |
stats in the same way for the new client as the old one.
MFC after: 2 weeks
|
|
|
|
|
|
| |
NFS subsystem.
MFC after: 2 weeks
|
|
|
|
| |
server stats when "-c" or "-s" was specified.
|
| |
|
|
|
|
|
| |
on GSS-API authenticated NFS where the kerberos credentials need to be
saved so that the kernel can authenticate to the NFS server.
|
|
|
|
|
|
| |
structure, which acts as a proxy between them. This makes jail rules
persistent, i.e. they can be added before jail gets created, and they
don't disappear when the jail gets destroyed.
|
| |
|
| |
|
|
|
|
|
|
|
| |
the new NFS subsystems after r221308.
This is a content change.
MFC after: 2 weeks
|
|
|
|
|
|
| |
new NFS subsystem.
MFC after: 2 weeks
|