summaryrefslogtreecommitdiff
path: root/NEWS
Commit message (Collapse)AuthorAgeFilesLines
* w: Fix musl UT_HOSTSIZE issueCraig Small2023-05-071-0/+1
| | | | | | | | | | | | | While musl has utmpx.h, their header file does not define all the values, especially __UT_HOSTSIZE and friends. Instead it just hard codes the sizes :/ This change will look for that definition specifically and if not found will include utmp.h too. Checked on Alpine 3.17 musl just makes these a stub so w doesn't work anyway. Signed-off-by: Craig Small <csmall@dropbear.xyz>
* free: Show single line statisticsCraig Small2023-05-021-0/+1
| | | | | | | | | | | | Added the -L --line option to free to show a small set of memory statistics on a single line of 80 characters. Largely based on the work of @Ulenrich1 and updated to the new API. References: procps-ng/procps#156 Signed-off-by: Craig Small <csmall@dropbear.xyz>
* NEWS: darn, I forgot to label one change as issue #272Jim Warner2023-04-051-1/+1
| | | | Signed-off-by: Jim Warner <james.warner@comcast.net>
* NEWS: include several more changes since release 4.0.3Jim Warner2023-03-261-0/+5
| | | | Signed-off-by: Jim Warner <james.warner@comcast.net>
* pgrep: Use only --signal option for signalCraig Small2023-03-011-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | When pgrep was used to match on signal, it makes sense to use the same signal parsing code as pkill. Unfortunately the "find the signal" part is a little too enthusaistic about what a signal is, meaning pgrep -u -42 fails because the signal becomes "42" and then there is no UID. This is a bit sad for pkill but has been that way for a long time. For pgrep this is new so now only the long form pgrep --signal <X> will work. In addition, when using --signal if pgrep/pkill couldn't work out what the signal was it just silently ignored it. It now complains and aborts. References: https://bugs.debian.org/1031765 commit 866abacf8805a74fb7c59cae1f64963e0a540b14
* tests: Dont compare floats with ==Craig Small2023-03-011-0/+4
| | | | | | | | | | | | | | | Comparing floats with == is bad and I should feel bad I did this. The problem is if something is close to, but not quite the exact same fails tests. I have used an epsilon of 1 because we don't care about accuracy, just that the function works well enough. References: issue procps-ng/procps#271 https://how-to.fandom.com/wiki/Howto_compare_floating_point_numbers_in_the_C_programming_language Signed-off-by: Craig Small <csmall@dropbear.xyz>
* NEWS: Release 4.0.3v4.0.3Craig Small2023-02-161-1/+3
|
* pgrep: make --terminal respect other criteriaJason Cox2023-01-251-0/+1
| | | | | | | | In some cases the --terminal option to pgrep will cause all processes matching the terminal to be output, even if other criteria would exclude them. Specifically, I noticed that it overrides the --runstates option. Signed-off-by: Craig Small <csmall@dropbear.xyz>
* vmstat: precision issues in unitConvert()Qin Fandong2023-01-181-0/+1
| | | | | | | | | | | | | | Fix conversion errors due to precision issues in function unitConvert For example: unitConvert(98720620) will return 98720624, not 98720620. Because we do (unsigned long)(float)98720620 in function unitConvert and this is wrong! We should do (unsigned long)(double)98720620 here. Signed-off-by: Craig Small <csmall@dropbear.xyz> References: procps-ng/procps!75
* vmstat: Fixed initial si,so,bi,bo,in & cs valuesSanskriti Sharma2023-01-181-0/+2
| | | | | | | | | | | | In the default display option, the first line of stats output in the above mentioned columns was incorrect. References: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668580 procps-ng/procps!74 procps-ng/procps#15 Signed-off-by: Craig Small <csmall@dropbear.xyz>
* watch: Fix buggy line-deletion behaviour with --no-linewrapJustin Gottula2023-01-181-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This change is largely based upon Justin's patch, I just moved the reset_ansi() parts out otherwise you get strange colour reset behaviours. Original patch message: I used the --no-linewrap (-w) option for the first time today, watching some wide output that didn't quite fit in my tmux pane. Quickly I noticed a problem: while --no-linewrap did indeed eliminate the spillover of lines too long for the terminal "window" width, it *also* resulted in a bunch of lines from the program output being hidden entirely. After some fiddling around, the exact problematic behavior appears to be as follows: 1. Lines which would have wrapped (more than $COLUMNS chars long) are handled correctly. 2. Lines which would *not* have wrapped (shorter than $COLUMNS) are printed; but then the next line is *not* printed! For long sequences of non-wrap-length lines, you get an every-other-line-is-visible sort of effect. The logic underlying the problem seems to be this: in the run_command loop, if the x loop goes all the way to completion (meaning we've reached the right-side edge of the window area), there's a small block of code for --no-linewrap whose main purpose is to call find_eol, which eats input until it hits a newline (or EOF). Clearly this is intended to be done for lines that are too long, so that the excess characters are discarded and the input pointer is ready to go for the subsequent line. However, this code isn't in any way conditional on the value of eolseen! Short/wouldn't-wrap lines will have encountered a newline character before exhausting the entire x loop, and therefore eolseen will be true. Long/would-wrap lines will not have encountered a newline when the x loop is exhausted, and so eolseen will be false. Nevertheless, find_eol is called in *both* cases. For long lines, it does what it's meant to do. For short lines, *the newline has already been encountered and dealt with*, and so the actual effect of find_eol is to eat the entirety of the next line, all the way through to its newline, such that it isn't printed at all. References: procps-ng/procps!157 Signed-off-by: Craig Small <csmall@dropbear.xyz>
* watch: add -r to not rexec on terminal resizeCraig Small2023-01-171-0/+1
| | | | | | | | | | If you have the watched program doing some other thing every time its run and you resize the window, you might get unexpected results. The -r option lets you run only when the interval has expired. References: procps-ng/procps!125 procps-ng/procps#190
* watch: Pass through bellCraig Small2023-01-171-0/+1
| | | | | | | | Based upon merge request 104, closes #174 References: procps-ng/procps!104 procps-ng/procps#174
* docs: Update drs description in ps.1 from top.1Leonard Janis Robert König2023-01-151-0/+1
| | | | | References: procps-ng/procps!156
* misc: Add NEWS for w --pidsCraig Small2023-01-151-0/+1
| | | | | | References: commit 5baf1e6226f9aa051b5570b655ed49b73ae10061 procps-ng/procps!159
* misc: Add NEWS for pgrep -HCraig Small2023-01-151-0/+1
| | | | | | References: commit 866abacf8805a74fb7c59cae1f64963e0a540b14 procps-ng/procps!165
* top: include the '5' toggle on the primary help screenJim Warner2023-01-151-1/+2
| | | | | | | | | | | | | | | | | | | | | When the p/e-cores support (via the '5' key) was added in the patch referenced below, I intentionally omitted that key from the top primary help screen. This seemed appropriate since it only applied to select Intel cpus and, besides, that screen was getting kind of crowded. [ it remains an objective to fit on a 80x24 terminal ] Upon reflection, I found a way to squeeze it into that help screen and have decided to included it. Hopefully its presence will encourage use of top's new provision on any Intel platforms that distinguish between cores. Reference(s): Sep, 2022 - exploit p/e-cores provision commit 00f5c74b1bc583d37315fa094c6f50cef7961c0c Signed-off-by: Jim Warner <james.warner@comcast.net>
* vmstat: Update memory statisticsIngo Saitz2023-01-061-1/+3
| | | | | | | | | | vmstat <n> would update most fields, but the memory statistics were only fetched the first time. References: https://bugs.debian.org/1027963 Signed-off-by: Craig Small <csmall@dropbear.xyz>
* ps: Correct BSD c optionCraig Small2022-12-191-0/+1
| | | | | | | | | | | | procps 3.3.17 the c option changed the command/args field to cmd but this got removed as part of newlib Functionality is back in with a test case. References: https://bugs.debian.org/1026326 Signed-off-by: Craig Small <csmall@dropbear.xyz>
* skill: Restore the -p flag functionalityCraig Small2022-12-121-0/+4
| | | | | | | | When the skill program was ported to the new API the code to filter on PID, used by the -p option, was missed. It is now restored. References: https://bugs.debian.org/1025915
* build-sys: Set library to 0:1:0v4.0.2Craig Small2022-12-051-1/+1
| | | | | There was a bug fix in the library but no functions add/moved/changed Revision incremented.
* NEWS: Change to 4.0.2v4.0.2_rc1Craig Small2022-11-261-1/+1
|
* w: Show time with TIME_BITS=64 on 32bit envCraig Small2022-11-091-0/+1
| | | | | | | | | | | Thanks to @kabe-gl for this patch. w command shows ????? for LOGIN@ column when compiled on 32bit environment with -D_TIME_BITS=64. References: #256 Signed-off-by: Craig Small <csmall@dropbear.xyz>
* misc: Add NEWS item for missing core_idCraig Small2022-10-251-0/+5
| | | | | | | | Tracking what we do to the library so the N:N:N version strings are updated. This is just a NEWS item for previous commit. References: commit b89e3230b2baa5b82a2961b240731db95a887f26
* NEWS: Set version to 4.0.1v4.0.1Craig Small2022-10-201-1/+2
|
* NEWS: Add entry for free --si fixCraig Small2022-09-281-0/+1
| | | | | References: procps-ng/procps!163
* doc: updated with library p-core/e-core identificationJim Warner2022-09-281-0/+2
| | | | Signed-off-by: Jim Warner <james.warner@comcast.net>
* doc: top now has more than two abreast summary displayJim Warner2022-09-121-0/+1
| | | | Signed-off-by: Jim Warner <james.warner@comcast.net>
* misc: Update NEWS/man date for pgrep -ACraig Small2022-08-311-0/+1
| | | | | | | | Added NEWS item Update pgrep.1 date References: commit 4b44ab98c144dae099442e30a62966a7689818c6
* library: Rename to libproc2Craig Small2022-08-291-0/+1
| | | | | | | | | | The newlib library used to be called libproc-2 but the new name is preferred. References: https://www.freelists.org/post/procps/Next-for-newlib,3 Signed-off-by: Craig Small <csmall@dropbear.xyz>
* pgrep: Better warning if pidfd_open not implementedCraig Small2022-07-181-0/+1
| | | | | | | | | | | | | | | | | | If procps is built on a Linux 5.3+ system then pidwait is built with pidfd_open(). If that program is run on a system < 5.3 then it gives an odd generic error. If we get a ENOSYS from one pid, we will get it for all the others so its better to explain what happens and terminate. The man page is updated to note this issue. This came up due to killall in psmisc using pidfd_send_signal References: https://bugs.debian.org/1015228 Signed-off-by: Craig Small <csmall@dropbear.xyz>
* doc: Note new Used behavourCraig Small2022-06-251-0/+1
| | | | | | | Added note to NEWS in the lbirary section Updated free.1 as it specifies the calculation Signed-off-by: Craig Small <csmall@dropbear.xyz>
* NEWS: acknowledge that utf8 multi-byte character inputJim Warner2022-06-141-0/+2
| | | | Signed-off-by: Jim Warner <james.warner@comcast.net>
* doc: acknowledge the top 'message log' display abilityJim Warner2022-06-051-0/+1
| | | | | | | [ along the way, we'll fix-up the section 4 commands ] [ summary which has gotten a little outdated lately. ] Signed-off-by: Jim Warner <james.warner@comcast.net>
* docs: Update news for watch equexitCraig Small2022-05-181-0/+1
| | | | | References: commit 3ac20bf5366b5784d8ee4b1f927e96f4dd164f28
* doc: detail 'Ctrl' bottom window namespaces plus focusJim Warner2022-05-161-1/+2
| | | | | | | [ along the way we will restore '^R' to keys summary ] [ plus correct a leftover reference to 'Ctrl-V' too. ] Signed-off-by: Jim Warner <james.warner@comcast.net>
* doc: add variable width data display without scrollingJim Warner2022-05-031-0/+2
| | | | Signed-off-by: Jim Warner <james.warner@comcast.net>
* pmap: Don't reopen stdin for reading fileCraig Small2022-04-261-0/+1
| | | | | | | | pmap uses freopen to read /proc/self/maps. There doesn't seem to be a good reason to do this and if pmap has its stdin previously closed then it fails. Signed-off-by: Craig Small <csmall@dropbear.xyz>
* doc: added provision for autogroup nice (AGNI) changesJim Warner2022-04-261-0/+1
| | | | Signed-off-by: Jim Warner <james.warner@comcast.net>
* top: remove those winflags which restricted 'x' toggleJim Warner2022-04-171-0/+1
| | | | | | | | | | | | | | | | | | | | On occasion, even as the top author, I wonder why that 'x' toggle has stopped working. Of course, it actually was working but a locate request ('L') or other filter ('O') operation was active and thus temporarily turned if off. Such behavior is documented in top's man page. Well, with this patch that 'x' suppression is no more. [ the original justification, however, remains true. ] [ but there's really only one character which causes ] [ any potential trouble & i'm gonna' keep it secret. ] [ besides, if a display is corrupted, there's always ] [ that '=' key which restores things back to normal. ] Signed-off-by: Jim Warner <james.warner@comcast.net>
* library: fix 'smaps' bug preventing a build with clangJim Warner2022-04-111-0/+1
| | | | | | | | | | | | | | | | | | | | | As a result of the issue referenced below, we'll trade our homegrown offset generator for an 'offsetof' macro found in the stddef.h header file. This pleases clang. [ and thanks to Daniel Kolesa for the report and fix ] Reference(s): . bug report & recommended solution https://gitlab.com/procps-ng/procps/-/issues/235 . clang error message proc/readproc.c:673:9: error: initializer element is not a compile-time constant mkENT(Rss), ^~~~~~~~~~ proc/readproc.c:661:34: note: expanded from macro 'mkENT' #define mkENT(F) { #F ":", -1, (int)((void*)&q->smap_ ## F - (void*)&q->fZERO) } ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Signed-off-by: Jim Warner <james.warner@comcast.net>
* sysctl: print dotted keys againCraig Small2022-04-091-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | When the globbing update was put into sysctl, you could no longer simply use the keys because one key could potentially be multiple paths once the glob expansion occured. Using the path instead gave a unique output. Except certain programs, such as salt, expected the output to use the dotted path "kernel.hostname" and not "kernel/hostname". We can no longer use the original key, so now for each path: Copy the path strip off /proc/ convert all / to . The sysctl testsuite was also updated to check for a few different types of conversion failures. References: commit 6389deca5bf667f5fab5912acde78ba8e0febbc7 https://www.freelists.org/post/procps/some-procpsn4400-fixes,4 https://repo.saltproject.io/ Signed-off-by: Craig Small <csmall@dropbear.xyz>
* NEWS: update with 2 ps related release 4.0.0 bug fixesJim Warner2022-04-091-0/+2
| | | | Signed-off-by: Jim Warner <james.warner@comcast.net>
* NEWS: Mention elogind mergeCraig Small2022-04-011-0/+4
| | | | | Reference: procps-ng/procps!151
* misc: Add v4.0.0 to NEWSCraig Small2022-03-231-1/+1
|
* doc: document 'scale_tics' function for Ctrl-E scalingJim Warner2022-03-061-1/+2
| | | | | | | | [ i also tweaked that 'STARTED' narrative just a bit ] [ since its original wording implied the value could ] [ change, whereas it's fixed when a task is started. ] Signed-off-by: Jim Warner <james.warner@comcast.net>
* doc: updated with new 'start time' & 'cpu utilization'Jim Warner2022-02-271-0/+2
| | | | Signed-off-by: Jim Warner <james.warner@comcast.net>
* free: Use wstr width and not lengthCraig Small2022-02-011-0/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | The previous commit used the value from mbstowcs() to work out the spacing required, as printf() got it completely wrong. However, for alignment of text you don't use the string length but the string width. As the referenced website says: Use wcslen when allocating memory for wide characters, and use wcswidth to align text. Which is what free does now. Chinese is still off by one but I cannot see why this is so. It's close enough for now. If someone can work it out, I'd love to know what the fix is. As a side effect, #213 is fixed because we are putting the correct number of spaces in. French is still an issue (see #24 ) but this is because the string is too long! References: procps-ng/procps#24 procps-ng/procps#213 procps-ng/procps#229 commit 9f4db0fb5606e4872829bd44b29443d5707b1505 https://www.linux.com/news/programming-wide-characters/ Signed-off-by: Craig Small <csmall@dropbear.xyz>
* free: Fix first column justificationCraig Small2022-01-311-0/+1
| | | | | | | | | | | | | | | | | | | free has for many years had a problem with translated header columns or the first column. This is because printf("-9s", str) doesn't use the wide length of the string but the char length meaning they are mis-aligned. Using the mbstowcs() function to get the wide length and then a precision parameter to append the right number of spaces after the number means we get what we need. References: procps-ng/procps#229 procps-ng/procps#204 procps-ng/procps#206 https://bugs.debian.org/1001689 Signed-off-by: Craig Small <csmall@dropbear.xyz>
* NEWS: updated to acknowledge 'LIBPROC_HIDE_KERNEL' varJim Warner2022-01-311-0/+1
| | | | Signed-off-by: Jim Warner <james.warner@comcast.net>
View Lorry Controller Status