summaryrefslogtreecommitdiffstats
path: root/usr.bin
Commit message (Collapse)AuthorAgeFilesLines
...
* Note that all of the birthtime related primaries are non-standard.ceri2006-04-041-5/+5
|
* Bump .Dd for the birthtime options.ceri2006-04-031-1/+1
|
* Add -Btime, -Bnewer, -Bmin, -newerB[Bacmt], -newer[acmt]B options toceri2006-04-034-4/+59
| | | | | | | | | work with the st_birthtime field of struct stat. 'B' has been chosen to match the format specifier from stat(1). Approved by: jhb MFC after: 2 weeks
* If you see a broken symlink, don't try to follow it,kientzle2006-04-022-4/+7
| | | | | | | | just archive it as a symlink, even if -h was specified. Thanks to: Jin Guojun PR: bin/95175 MFC After: 1 week
* Don't call audit_logout() if pwd is NULL, as audit_logout() attempts tocognet2006-03-281-1/+4
| | | | | | | | | | dereference it. This will happen if we ^D at the Login: prompt without having provided a valid login before. Set pwd to NULL on bad login attempts to prevent audit_logout() from being called for a user which didn't actually log on. Reported by: Jerome Magnin jethro at docisland dot org
* Make gcore(1) 64 bit safe. It was trying to parse the /proc/*/map filepeter2006-03-251-3/+3
| | | | | | | | | using sscanf and truncating the start/end entries by writing them with a 32 bit int descriptor (%x). The upper bytes of the 64 bit vm_offset_t variables (for little endian machines) were uninitialized. For big endian machines, things would have been worse because it was storing the 32 bit value in the upper half of the 64 bit variable. I've changed it to use %lx and long types. That should work on all our platforms.
* Extended attribute support on write for Linux; FreeBSD hooks arekientzle2006-03-219-23/+140
| | | | | | | | | | forthcoming. This commit also has a number of style(9) fixes and minor corrections so the code works better with the build system being used for non-FreeBSD builds. Many thanks to: Jaakko Heinonen, who proposed a mechanism for extended attribute support and implemented both the machine-independent portion and the Linux-specific portion.
* Unbreak WITHOUT_LIBPHREAD/WITHOUT_LIBC_R option support, dependingru2006-03-211-0/+6
| | | | on platform.
* Extend coverage of the MK_IPX build option to the following:ru2006-03-201-0/+4
| | | | | | | | | | | | | | | | | | | | | - <netipx> headers [1] - IPX library (libipx) - IPX support in ifconfig(8) - IPXrouted(8) - new MK_NCP option New MK_NCP build option controls: - <netncp> and <fs/nwfs> headers - NCP library (libncp) - ncplist(1) and ncplogin(1) - mount_nwfs(8) - ncp and nwfs kernel modules User knobs: WITHOUT_IPX, WITHOUT_IPX_SUPPORT, WITHOUT_NCP. [1] <netsmb/netbios.h> unconditionally uses <netipx> headers so they are still installed. This needs to be dealt with.
* Convert NO_PROFILE and NO_LIB32 to new style.ru2006-03-181-1/+3
|
* add an entry for ozfod..jmg2006-03-181-0/+1
| | | | MFC after: 3 days
* fix spelling of ozfod... I've been wondering why we'd need to fill a pagejmg2006-03-181-1/+1
| | | | | | | w/ non-zero data, and it turns out we don't... This is really optimized zero filled on demand, or pages that were already zero'd for us... MFC after: 3 days
* A few minor corrections to the mkuzip.8 man page.sobomax2006-03-171-25/+24
| | | | | PR: 92576 Submitted by: Stefan Bethke
* Reimplementation of world/kernel build options. For details, see:ru2006-03-179-26/+46
| | | | | | | | http://lists.freebsd.org/pipermail/freebsd-current/2006-March/061725.html The src.conf(5) manpage is to follow in a few days. Brought to you by: imp, jhb, kris, phk, ru (all bugs are mine)
* Cross-reference basename(3) and dirname(3).jkoshy2006-03-161-1/+3
|
* When opening a trace file, open O_NONBLOCK so that ktrace doesn't stallrwatson2006-03-141-1/+4
| | | | | | | | | if the target is a fifo. After opening a trace file, check that it is a regular file, and if not, return an error. MFC after: 3 days Reported by: kris PR: 94278
* Update make glue for csup-snap-20060313.mux2006-03-141-0/+1
|
* Remove non-FreeBSD source from FreeBSD repository.kientzle2006-03-121-20/+0
|
* Remove including of libc sources. All the required functionsdeischen2006-03-101-8/+2
| | | | | are exported by libc with prototypes in our standard headers. I guess at one time this was necessary, but not any longer.
* Remove configure.ac.in and the 'distfile' target fromkientzle2006-03-084-164/+6
| | | | | the FreeBSD makefile. This is a step towards cleaning out the non-FreeBSD bits from the FreeBSD source tree.
* Add a check for Linux' "libacl" library and headers.kientzle2006-03-071-0/+4
|
* Change the output of --version to match GNU "gnits" standards.kientzle2006-03-071-5/+2
| | | | | | | | (I'm not using GPL, but I still think there are good ideas in the GNU projects. ;-) Among other things, this should make it easier for clients of bsdtar to recognize it automatically: bsdtar --version | grep bsdtar
* Fix a format mismatch (%d integer format, platform-dependentkientzle2006-03-071-1/+1
| | | | argument type).
* Add an override (DONTSTRIP) so that one can easily install debugableobrien2006-03-062-0/+14
| | | | | binaries when one cannot easily edit a package's Makefiles and/or configure scripts.
* Managing login.access is no longer a responsibility of login(1).yar2006-03-061-10/+6
| | | | | | Therefore give a xref, not details. MFC after: 3 days
* Remove the last reference to LOGIN_ACCESS from login(1).yar2006-03-061-2/+3
| | | | MFC after: 3 days
* login.access.5 and login_access.c are no longer usedyar2006-03-062-296/+0
| | | | | | | | | | | | | | | in usr.bin/login because the login.access feature has moved to PAM completely. Their counterparts in lib/libpam/modules/pam_login_access have been found to be in sync with, and even in better shape than, login.access.5 and login_access.c here. Therefore cvs rm login.access.5 and login_access.c from usr.bin/login so that nobody will waste their time on fixing or developing the files here. MFC after: 3 days
* login(1) no longer handles /etc/login.access by itself,yar2006-03-061-1/+0
| | | | | | it's PAM's job. MFC after: 3 days
* Since the whole login.access feature has moved to PAM,yar2006-03-061-1/+1
| | | | | | | login.access.5 will be installed from the respective PAM module's src directory. MFC after: 3 days
* Reduce number of spaces for full name by four, and reduce paddingrwatson2006-03-041-5/+5
| | | | | | | | | | | | | | | | | | | | | after tty entry by one space in order to provide extra spaces for the tty entry. As a result, full pts names are now visible (up to 999 pts's anyway): Before: Login Name TTY Idle Login Time Office Phone robert Robert Watson *v0 3:55 Fri 02:54 robert Robert Watson p0 19 Sat 11:01 robert Robert Watson pts Sat 14:55 After: Login Name TTY Idle Login Time Office Phone robert Robert Watson *v0 5:08 Fri 02:54 robert Robert Watson p0 8 Sat 11:01 robert Robert Watson pts/5 Sat 14:55 MFC after: 1 week
* Don't build csup if NO_CRYPT or NO_OPENSSL is defined, since we dependmux2006-03-031-1/+2
| | | | | | on those. Reported by: marius
* Connect csup the build!mux2006-03-031-0/+1
|
* - Don't put the .h in SRCS.mux2006-03-031-25/+25
| | | | | | | - Use LDADD += -lpthread and DPADD += ${LIBPTHREAD} instead of -pthread. - s/-I${.CURDIR}/-I./ to fix make obj. Submitted by: ru
* Add make glue for building csup. Not yet connected to the build.mux2006-03-031-0/+35
|
* Fix the way in which median is calculated. If the data source has evenwkoszek2006-02-231-7/+18
| | | | | | | number of data points, value should be calculated by adding two middle elements and dividing them by 2. Approved by: cognet (mentor)
* Add myself as a new src commiter:wkoszek2006-02-221-0/+1
| | | | | | | + extend calendar with my birth date Approved by: cognet (mentor) Reviewed by: cognet (mentor)
* If opendir(".") fails after descending into a subdirectory viapeadar2006-02-221-1/+2
| | | | | | | | | | chdir(), be sure to undo the effects of the chdir before continuing. Without this, after hitting a directory with mode 0111 (for example), tar will get lost, and won't add any yet unvisted files to your archive. (Or possibly add the wrong files, I suppose...) Reviewed By: kientzle@
* Add option -w to specify graph width.mdodd2006-02-221-3/+24
| | | | | | Use COLUMNS, terminal width for default graph width. Reviewed by: rwatson
* In wall and who, check that the utmp entry isn't stalled, as it is done in w.cognet2006-02-212-3/+36
| | | | | | | Apparently with the new pts code stalled entries are printed, when they are not with the BSD ptys. Submitted by: Michal Mertl <mime at traveller dot cz>
* Improved description for packet zone statistics.andre2006-02-181-1/+1
| | | | | Sponsored by: TCP/IP Optimization Fundraise 2005 MFC after: 3 days
* Print statistics on mbuf+clusters in packet zone.andre2006-02-181-0/+4
| | | | | Sponsored by: TCP/IP Optimization Fundraise 2005 MFC after: 3 days
* Print statistics on jumbo mbuf clusters.andre2006-02-181-2/+72
| | | | | Sponsored by: TCP/IP Optimization Fundraise 2005 MFC after: 3 days
* Move the "r p d s w" fields to the left to create space for expansion.bde2006-02-141-25/+26
| | | | | | | | | | | | | | | | | | | | | | 3 columns were wasted at the left, except these columns were used to make the header line up. Now there is no space on the same line for the "Proc:" part of the header. Try putting this on the line above although it clutters that line (there is already similar clutter for the "Interrupts" header). Leave 1 column between these fields. With the above and a previous change there is enough of space for this. Use 5 columns instead of 3 for the number of users since 3 is not quite enough and there was space to spare. This also fixes an off-by-2 error in a previous fix forthe column count in the comment on STATROW. Move all the pager fields 1 to the right so that the "count" and "pages" descriptors more clearly apply to the pager fields and not the memory fields. There was space to space. Waste some of the spare space at the right of the pager fields to expand all the pager field widths to their old values (but now with a column between the fields). There are fields more in need of expansion but most of them are not in places near spare space.
* Removed the frobbing of CPU percentages from > 99.9 to 99.9. Rev.1.35bde2006-02-141-2/+0
| | | | | | | | | | | | made it unnecessary. (Rev.1.6 had to reduce the field width to 4, and changed 100.0 and preposterous larger values down to 99.9 since 100.0 wouldn't have fitted. Rev.1.35 handles precentages > 99.9 well enough by changing the format to %.0f when the string given by the initial format is too wide.) Even with this change, during short testing I've never seen a percentage of 100 being displayed by systat -v, although top(1) displays percentages of 100 user or 100 idle for similar loads.
* Fix some minor bugs:bde2006-02-141-13/+21
| | | | | | | | | | | | | | | Always use snprintf()'s return value, since discarding it is a style bug at best and using it here gives slightly simpler code and better error checking. Use snprintf() in putlongdouble() the same as in putfloat(). (1.25 changed most sprintf()'s to snprintf()'s to fix non-bugs without changing the logic to use the result of snprintf(); 1.27 restored one of the sprintf()s by cloning a stale version of putfloat().) Don't print a too-long field in the unlikely case that the fallback to M units in putint() leaves the field still too long. (The fallback to printing stars was lost in rev.1.58 when the fallback to M units was added.)
* Reduce the field width by 1 for many numeric fields so that most fieldsbde2006-02-141-39/+39
| | | | | | | | | | | | | | | | | | | | | | | | | | | | cannot run into other fields or field descriptors. If the value is too large to fit in the field width, then the output format is adjusted so that the value (usually) fits, but with fields running together externally this adjustment usually didn't help. Mostly it doesn't matter to lose 1 digit of precision, but switching the output format is bad if it happens often or gives bogus units. The loss of width is most serious for fields near "Csw" (which are also the ones which must often ran together) since these have a high variance and large values relative to the possible field widths so the switch occurs more often now, and for the memory size fields where the switch gives the bogus units kKB or MKB. Now only the fields for r, p, d, s and w can run into each other. These fields have width 3, and 3 cannot be reduced to 2 without losing all precision when the value is between 100 and 999. Trim "pdwake" to "pdwak" at think time now that it doesn't get clobbered at runtime. The manpage doesn't need to be changed for this because it documents the clobbered descriptor, unlike for 4 other too-long descriptors which only get clobbered if there are lots of interrupt sources. Trim "% busy" to "%busy" since most other descriptors for percentages are spelled without the space and this change makes changing the widths of the %busy fields unnecessary.
* Oops, the "excessive" {} removed in the previous commit was neededbde2006-02-141-1/+3
| | | | | | around PUTRATE() because PUTRATE() only looked like a function -- it was multiple statements. Use "do {...} while(0)" as usual in PUTRATE() so that it is a single statement that can be used like a function.
* Fixed all (?) bitrot in the comments about the number of columns used bybde2006-02-141-8/+8
| | | | various groups of fields.
* Fix all (?) cases where the field width of a numeric field was far toobde2006-02-141-8/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | large. In most cases it is still 1 too large, so fields tend to run together, but in the following cases it was more than 1 too large, and the starting column was too small too, so the field started inside the previous field or descriptor and clobbered that: - "wire": the number for this overwrote 2 characters of the number for "Flt". Reduce the field width by 3 (2 to avoid the overwrite and 1 so that the fields don't run together). This was already done for the preceding number for "cow". - "inact": the number for this overwrote 1 character of the descriptor "Idle". Reducing the field width by 2 is enough. - "cache:" the number for this overwrote 3 characters of the scale "...| |". The field width should be reduced by 4 to keep things from running together, but that is a lot and not so necessary here since the final "|" in the scale serves as a delimiter. Only reduce it by 3. - "free": the number for this overwrote 2 characters of the bar graph. The character position under the final "|" in the scale is apparently not used, so reducing the field width by 3 is enough. When "zfod" is in the main vmstat display: - use the normal field width of 9 (not 5) for it since there is no shortage of space. Fix style bugs (excessive {}) in the statement that conditionally writes it. Write all reduced field widths for vmstat fields as "9 - <reduction>" as a hint that we don't want to reduce them.
* Fixed style bugs in rev.1.12. Rev.1.12 arranged to display the interruptbde2006-02-141-7/+7
| | | | | | | | | | | | number in more cases by stealing 2 characters from the count field to give more space in the descriptor field, but it did the column adjustments for this strangely using an off-by-2 error in the base column and compensating off-by-2 errors in 6 offsets from the base column (4 new errors and 2 from not changing the offsets that actually changed). Print the "Interrupts" header directly at its offset from the base column instead of spacing it half using the offset and half by printing a space character.
OpenPOWER on IntegriCloud