Manoj Srivastava writes:
>On Thu, Sep 10 2009, Cameron Hutchison wrote:
>> Version 3 (below) is "properly" written, in a functional style. It's much
>> longer, but much easier to read. The main() function is very simple,
>> as is each individual function. It's written in such a way that you
>> c
On Thu, Sep 10 2009, Cameron Hutchison wrote:
> Version 3 (below) is "properly" written, in a functional style. It's much
> longer, but much easier to read. The main() function is very simple,
> as is each individual function. It's written in such a way that you
> can add extra filters if you wan
Javier Barroso writes:
>On Thu, Sep 10, 2009 at 11:33 PM, Cameron Hutchison wrote:
>>
>> /proc/pid/cmdline usually has ASCII NUL separated fields, which awk does
>> not split, so usually you have to use xargs -0. I noticed some cases
>> where the args were space separated (perl script), so I nee
On Fri, 11 Sep 2009, Thomas Dickey wrote:
On Fri, 11 Sep 2009, Thomas Dickey wrote:
however, Debian's packagage maintainer for mawk has not responded to any of
package...
--
Thomas E. Dickey
http://invisible-island.net
ftp://invisible-island.net
--
To UNSUBSCRIBE, email t
On Fri, 11 Sep 2009, Thomas Dickey wrote:
On Fri, 11 Sep 2009, Javier Barroso wrote:
On Thu, Sep 10, 2009 at 11:33 PM, Cameron Hutchison wrote:
/proc/pid/cmdline usually has ASCII NUL separated fields, which awk does
not split, so usually you have to use xargs -0. I noticed some cases
where
On Fri, 11 Sep 2009, Javier Barroso wrote:
On Thu, Sep 10, 2009 at 11:33 PM, Cameron Hutchison wrote:
/proc/pid/cmdline usually has ASCII NUL separated fields, which awk does
not split, so usually you have to use xargs -0. I noticed some cases
where the args were space separated (perl script),
On Thu, Sep 10, 2009 at 11:33 PM, Cameron Hutchison wrote:
> Javier Barroso writes:
>
>>> is this "xargs: echo: terminated by signal 13" the output it should be?
>>Probably, substituting:
>
>> bin=$(xargs -n 1 -0 echo < /proc/$pid/cmdline | awk '{print $1 ; exit}')
>
>>with
>
>>bin=$(awk '{print
Israel Garcia writes:
>[...] it seems when the script found
>duplicate lines, like named/tcp and named/udp it only show one, se
>below:
>vps204:/usr/local/bin# netstat -lntup
>tcp0 0 67.212.94.125:530.0.0.0:* >LISTEN 23874/named
>tcp0 0 127.0.0.1:53
On 9/10/09, Cameron Hutchison wrote:
> Cameron Hutchison writes:
>
>>Israel Garcia writes:
>>>On 9/10/09, Cameron Hutchison wrote:
>
Version 3 (below) is "properly" written, in a functional style. [...]
>
>>>Well, in version 3 I see no output when I run the script...I double
>>>check but I
Cameron Hutchison writes:
>Israel Garcia writes:
>>On 9/10/09, Cameron Hutchison wrote:
>>> Version 3 (below) is "properly" written, in a functional style. [...]
>>Well, in version 3 I see no output when I run the script...I double
>>check but I dont know where the problem is.
>Hmmm, work fo
Israel Garcia writes:
>On 9/10/09, Cameron Hutchison wrote:
>> Version 3 (below) is "properly" written, in a functional style. [...]
>Well, in version 3 I see no output when I run the script...I double
>check but I dont know where the problem is.
Hmmm, work for me (tm). Try isolating the failu
Javier Barroso writes:
>> is this "xargs: echo: terminated by signal 13" the output it should be?
>Probably, substituting:
> bin=$(xargs -n 1 -0 echo < /proc/$pid/cmdline | awk '{print $1 ; exit}')
>with
>bin=$(awk '{print $1; exit}' /proc/$pid/cmdline)
>will solved the issue
>But I'm not su
On Thu, Sep 10, 2009 at 4:21 PM, Israel Garcia wrote:
>>>case ruby. See below:
> Hi Cameron,
>
>>
>> Ok. Here's version 2. Fixes are:
>> * Sorted the output by port number and removed duplicates. Duplicates
>> happen when a daemon listens on multiple IP addresses (samba is one).
>> * Skip
On 9/10/09, Cameron Hutchison wrote:
> Cameron Hutchison writes:
>
>>Ok. Here's version 2. Fixes are:
>
> One more iteration before I go to bed.
>
> Version 2 was the quickly knocked together script that looks ugly and
> hard to read, but is nice and compact. Maybe "nice" isn't the right
> word.
>>case ruby. See below:
Hi Cameron,
>
> Ok. Here's version 2. Fixes are:
> * Sorted the output by port number and removed duplicates. Duplicates
> happen when a daemon listens on multiple IP addresses (samba is one).
> * Skip non-existent processes
> * remove (delete) from the end of rea
Cameron Hutchison writes:
>Ok. Here's version 2. Fixes are:
One more iteration before I go to bed.
Version 2 was the quickly knocked together script that looks ugly and
hard to read, but is nice and compact. Maybe "nice" isn't the right
word.
Version 3 (below) is "properly" written, in a funct
Israel Garcia writes:
>On 9/9/09, Cameron Hutchison wrote:
>> Israel Garcia writes:
>>
>>>I have more than 10 debian (etch and lenny) servers and I want to find
>>>a way to know remotely on every server:
>>
>>>1. Name of running daemons and ports (tcp/udp) they're using.
>>>2. Version of the pac
On 9/9/09, Ron Johnson wrote:
> On 2009-09-09 23:30, Israel Garcia wrote:
>> On 9/9/09, Cameron Hutchison wrote:
>>> Israel Garcia writes:
>>>
I have more than 10 debian (etch and lenny) servers and I want to find
a way to know remotely on every server:
1. Name of running daemons
On 2009-09-09 23:30, Israel Garcia wrote:
On 9/9/09, Cameron Hutchison wrote:
Israel Garcia writes:
I have more than 10 debian (etch and lenny) servers and I want to find
a way to know remotely on every server:
1. Name of running daemons and ports (tcp/udp) they're using.
2. Version of the p
On 9/9/09, Cameron Hutchison wrote:
> Israel Garcia writes:
>
>>I have more than 10 debian (etch and lenny) servers and I want to find
>>a way to know remotely on every server:
>
>>1. Name of running daemons and ports (tcp/udp) they're using.
>>2. Version of the package (installed by APT) used by
Israel Garcia writes:
>I have more than 10 debian (etch and lenny) servers and I want to find
>a way to know remotely on every server:
>1. Name of running daemons and ports (tcp/udp) they're using.
>2. Version of the package (installed by APT) used by these daemons.
>3. Version of the latest pac
I have more than 10 debian (etch and lenny) servers and I want to find
a way to know remotely on every server:
1. Name of running daemons and ports (tcp/udp) they're using.
2. Version of the package (installed by APT) used by these daemons.
3. Version of the latest package (from deb mirros) used b
22 matches
Mail list logo
