Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | Per-variable\ entry headers, to allow the 'ps -otime -otime=FOO' or similar | jmallett | 2003-01-19 | 4 | -11/+19 |
| | | | | | case to do the right thing and affect exactly one column. This is consistent with GNU ps(1) in BSD mode, and POLA. | ||||
* | When inserting a non-user-specified (e.g. not via -o or -O) format, don't dupe | jmallett | 2003-01-19 | 3 | -16/+39 |
| | | | | | | | | one that is already there. This is consistent with GNU ps(1)'s BSD mode, and POLA. Reported by: Andy Farkas <andyf@speednet.com.au> Tested by: Andy Farkas <andyf@speednet.com.au> | ||||
* | Refer to the process label as proclabel, as there is a function called label, | jmallett | 2003-01-18 | 1 | -10/+10 |
| | | | | and that's what these locals were called before. | ||||
* | Fixed the abuses of .Ql visible on stderr in troff mode. | ru | 2002-12-23 | 1 | -1/+1 |
| | | | | PR: docs/37176 | ||||
* | The hw.availpages sysctl has an unsigned long value now, fix the retrieval | tmm | 2002-11-01 | 2 | -2/+3 |
| | | | | to match that. | ||||
* | Do not print a header line if it would be empty; required by 1003.1-2001. | tjr | 2002-10-31 | 1 | -0/+9 |
| | |||||
* | Use the MAC interface to list process MAC labels rather than using | rwatson | 2002-10-24 | 8 | -172/+58 |
| | | | | | | | | | | the LOMAC-specific interface (which is being deprecated). The revised LOMAC using the MAC framework will export levels listable using this mechanism. Approved by: re Obtained from: TrustedBSD Project Sponsored by: DARPA, Network Associates Laboratories | ||||
* | Oops, the previous version was a last minute test version with off_t | bde | 2002-10-03 | 1 | -1/+1 |
| | | | | | | replaced by int instead of size_t. Spotted by: fanf | ||||
* | Use a non-bogus type for representing the values of offsets in structs. | bde | 2002-10-03 | 1 | -1/+1 |
| | | | | | | | off_t is for offsets in files, and it is signed so it was no better than the original type of int for avoiding warnings from broken lints, except accidentally on machines like i386's where size_t is smaller than off_t. | ||||
* | Catch up to SMTX -> SLOCK changes. | jhb | 2002-10-02 | 4 | -25/+22 |
| | |||||
* | List valid keywords, ala kill(1), rather than the csh builtin kill, which | jmallett | 2002-09-27 | 1 | -2/+5 |
| | | | | | | | tells people to type kill -l, when no valid ones are specified. Sponsored by: Bright Path Solutions MFC after: 4 days | ||||
* | Ala kill(1), tell people to type 'ps -L' for a list of format keywords. | jmallett | 2002-09-27 | 1 | -1/+1 |
| | | | | | Sponsored by: Rachel Hestilow <rachel@jerkcity.com> MFC after: 2 weeks | ||||
* | Rename new PLONG type to PGTOK as the conversion is more important than the | jmallett | 2002-09-17 | 3 | -4/+4 |
| | | | | | | size (which is mostly undefined anyway). Submitted by: bde | ||||
* | Conglomerate printing of ps_pgtok'd data into a PLONG type. I couldn't think | jmallett | 2002-09-17 | 4 | -23/+6 |
| | | | | | of a better name, except PINT, but I decided to go with assuming LONG to be safe, rather than assuming INT. | ||||
* | Perform keyword.c:1.27 properly, implement -orss in the New World Order of | jmallett | 2002-09-16 | 3 | -2/+12 |
| | | | | | | | | ps(1) formatting, using pgtok() to get the value in K, rather than printing it in pages. This is consistent with behaviour before keyword.c:1.26 (et al) which exists in STABLE today, and which uses the same metric as VSZ. Submitted by: bde | ||||
* | Remove some NOTINUSE stuff. Good housekeeping. | jmallett | 2002-09-16 | 1 | -9/+0 |
| | |||||
* | Do not risk using the kernel pgtok() which assumes the page size is | peter | 2002-09-13 | 1 | -6/+2 |
| | | | | constant. | ||||
* | Prevent ps(1) from doing idiotic munging of things in a -ofmt= string. | jmallett | 2002-09-03 | 1 | -1/+8 |
| | | | | God I hate the backwards compatability crap here. | ||||
* | s/filesystem/file system/ as discussed on -developers | trhodes | 2002-08-21 | 1 | -1/+1 |
| | |||||
* | mdoc(7) police: whitespace nits. | ru | 2002-08-09 | 1 | -2/+3 |
| | |||||
* | Fixed a printf format error that was fatal on alphas. Adding WFORMAT=0 | bde | 2002-07-11 | 1 | -2/+1 |
| | | | | | | | | to the Makefile didn't affect this bug because WFORMAT only controls higher- level format checking (not the -Wformat that is implicit in -Wall). Fixed a nearby printf format error that was benign and 3 nearby style bugs. | ||||
* | err() is documented as allowing NULL for the format string but GCC isn't | dillon | 2002-07-10 | 1 | -1/+1 |
| | | | | happy about it any more so change the usage to make buildworld work again. | ||||
* | Bring back WFORMAT=0. | jmallett | 2002-07-08 | 1 | -0/+1 |
| | |||||
* | - Use (MAXLOGNAME - 1) where UT_NAMESIZE was used to be able to | robert | 2002-07-08 | 2 | -4/+2 |
| | | | | (-)remove the inclusions of <utmp.h>. | ||||
* | Make printval() take a 'void *' thus negating any assumptions the compiler | jmallett | 2002-07-07 | 1 | -2/+2 |
| | | | | may try to make about the alignment of the dereferenced datum. | ||||
* | Don't depend on pollution in <limits.h> for the definition of | mike | 2002-07-05 | 1 | -0/+1 |
| | | | | <stdint.h> macros. | ||||
* | Consistently use FBSDID | obrien | 2002-06-30 | 6 | -20/+10 |
| | |||||
* | Don't try to decode old-style options if the argv[1] begins with `-' and the | sobomax | 2002-06-20 | 1 | -10/+28 |
| | | | | | | | | | | | | | second character represents some option taking an argument. This fixes problem when ps(1) is invoked for examply as follows: $ ps -Ufoobar1234 the above example results in option string being interpreted as -U foobarp1234 - note extra `p'. Reported by: Vladimir Sotnikov <vovan@kyivstar.net> MFC after: 2 weeks | ||||
* | ps(1) appeared in v4 | jmallett | 2002-06-10 | 1 | -1/+1 |
| | | | | Submitted by: grog | ||||
* | Note early appearence of some commands. These actually appeared in PWB, but | jmallett | 2002-06-10 | 1 | -0/+5 |
| | | | | | it seems we don't have a macro for that yet, so list them in the first UNIX release since then that we have a .At for: v7. | ||||
* | Allow whitespace to act as a delimiter in the keywords list given to the -o, | jmallett | 2002-06-08 | 2 | -5/+14 |
| | | | | | | | | again, but also allow it in the user-specified header, too. This is far more backwards compatible and SUSv3-happy than allowing only comma to seperate the keywords list. Submitted by: tjr | ||||
* | Fixed unsorting. | bde | 2002-06-08 | 1 | -1/+1 |
| | |||||
* | Don't say that the list of formats can be space delimited, it no longer can be. | jmallett | 2002-06-08 | 1 | -2/+5 |
| | | | | | | Mention that more than one -o will concatenate formats. Submitted by: Jun Kuriyama <kuriyama@imgsrc.co.jp> | ||||
* | Back out previous back out of previously correct code. | jmallett | 2002-06-07 | 1 | -2/+1 |
| | | | | | Double-plus-pointy-hat to: jmallett Submitted by: bde | ||||
* | Remove tunables to hide warnings that no longer exist. | jmallett | 2002-06-07 | 1 | -2/+0 |
| | |||||
* | Cast to long to match format. Hidden by revision 1.18 of Makefile. | jmallett | 2002-06-07 | 1 | -1/+2 |
| | |||||
* | Use a global `now' variable for the current time, and initialise it at | jmallett | 2002-06-06 | 3 | -6/+5 |
| | | | | startup, right after calling setlocale(3). | ||||
* | Implement a SUSv3-ignorant but "time"-similar format for "etime", elapsed | jmallett | 2002-06-06 | 4 | -0/+21 |
| | | | | | run time (NOT cpu time). cputime() and elapsed() both need to honour SUSv3 now. | ||||
* | sysctlbyname(3) returns -1 on failure, not any other value < 0. | jmallett | 2002-06-06 | 1 | -3/+3 |
| | |||||
* | Support the SUSv3 `rgroup' format. | jmallett | 2002-06-06 | 4 | -5/+24 |
| | | | | Clean up some local style bogons. | ||||
* | Cast arg_max to size_t when comparing it (times 4, plus 1) against SIZE_MAX. I | jmallett | 2002-06-06 | 1 | -1/+2 |
| | | | | | | | | was worried about truncation of arg_max by this cast, but if it gets truncated, we know it'll obviously be greater than SIZE_MAX anyway. Big pointy hat to: jmallett Submitted by: keramida | ||||
* | SUSv3 conform on the "comm" and "args" formats, and make correct the "command" | jmallett | 2002-06-06 | 4 | -4/+41 |
| | | | | format, since it's BSDlike, and "comm" is actually different. | ||||
* | Refer to the command format by its SUSv3 name (comm), and list command as an | jmallett | 2002-06-06 | 1 | -2/+2 |
| | | | | alias. | ||||
* | As per behaviour on SVR4 systems, to allow any desirable type of header in the | jmallett | 2002-06-06 | 1 | -2/+4 |
| | | | | | | | | | | | | | | | | override, seperate by comma (',') only, rather than any type of whitespace (the literal space character (' ') had already been removed from this list). This allows things like: miamivice# ps -opid='Process > Identifier' Process Identifier 1350 1445 1450 To work. | ||||
* | Widen the scope of fmt.c::1.19 and consistently use errx(3) if malloc(3) [or | jmallett | 2002-06-05 | 3 | -10/+8 |
| | | | | | | | | | | realloc(3)] happens to fail, everywhere in ps(1). Discussed with: bde, charnier (a while ago) fmt_argv() can no longer return NULL, so don't bother checking. Submitted by: bde | ||||
* | Comma seperate format lists, since space is no longer up to the task. | jmallett | 2002-06-05 | 1 | -6/+6 |
| | | | | | Poked by: David Wolfskill <david@catwhisker.org> Pointy hat to: jmallett | ||||
* | Support the 'comm' keyword, which is equivalent to our 'command', but | jmallett | 2002-06-05 | 1 | -0/+2 |
| | | | | specified by SUSv3. | ||||
* | A space cannot be a header string seperator it appears given the SUSv3 | jmallett | 2002-06-05 | 1 | -1/+1 |
| | | | | | description of ps(1), which uses them. I question whether newline and tab can be either, but I'm not touching them. Yet. | ||||
* | To comply with SUSv3, duplicate the variable contents for each given format, | jmallett | 2002-06-05 | 1 | -1/+4 |
| | | | | | | | | | | | | so that multiple -ovar=header lines do not overwrite eachother. This means that ps -ouser=USERNAME -ouser=WHO would now possibly print: USERNAME WHO juli juli Whereas before it would be: WHO WHO juli juli | ||||
* | Returning NULL here if malloc(3) fails is silly, at this point in the codepath | jmallett | 2002-06-05 | 1 | -1/+1 |
| | | | | | we have't malloc(3)'d nearly as much as we probably will, so errx(3) away, instead of waiting for something to fail yet again later on. |