On Sun, Jun 03, 2012 at 13:37, Brynet wrote:
> On Sat, Jun 02, 2012 at 03:09:54PM -0400, Brynet wrote:
>> I wasn't sure about the interactions between getopt(3) and having an
>> '-' as an optarg.
>>
>> Seems there isn't anything obvious, so this allows users to be hidden
>> using: top -U -user
-u
> Hopefully this is the final diff.
>
> Showing a single user and then hiding them will now work as one would
> expect.
>
> I also forgot to update usage().
looks reasonable. ok lum@
On Sat, Jun 02, 2012 at 03:09:54PM -0400, Brynet wrote:
> I wasn't sure about the interactions between getopt(3) and having an
> '-' as an optarg.
>
> Seems there isn't anything obvious, so this allows users to be hidden
> using: top -U -user
>
> Any comments?
> -Bryan.
Hopefully this is the fin
I wasn't sure about the interactions between getopt(3) and having an
'-' as an optarg.
Seems there isn't anything obvious, so this allows users to be hidden
using: top -U -user
Any comments?
-Bryan.
Index: display.c
===
RCS file: /c
On Fri, Jun 01, 2012 at 04:02:11PM -0400, Brynet wrote:
> Hi,
>
> Sometimes it's handy to hide a user from top(1) output, on a desktop
> system for example you might want to quickly hide yourself and see what
> else is running.
>
> The syntax for interactive mode is u -user, passwd(5) entries sho
Hi,
Sometimes it's handy to hide a user from top(1) output, on a desktop
system for example you might want to quickly hide yourself and see what
else is running.
The syntax for interactive mode is u -user, passwd(5) entries shouldn't
begin with that character.
'-', like '+', will clear all filte
