jay alvarez wrote:
> Hi,
> 
> I have a directory of flow-captured flows for a whole month(Dec2006) and
> I'm trying to do a
> flow-cat "flows_dir" | flowstat -f8 -S2 > topdestination
> 
> I left it in background and it's been running for 30 hours now.
> Doing a "top" shows flow-stat being on top of the list from time to time
> consuming around 60% of memory on a debian system. Noticeably, flow-cat
> doesn't appear in "top" (perhaps it's done with its job)
> 
> however ps shows them both.
> 
> #ps -aux |grep flow
> 
> root     22604  0.9  0.0  6448  284 ?        S    Jan09  16:31 flow-cat
> /var/netflow/ft/all/dec2006/
> root     22605  7.0 52.3 875204 474452 ?     D    Jan09 123:07 flow-stat
> -f8 -S2
> 
> 
> 
> Also lsof
> 
> # lsof |grep flow-cat
> 
> flow-cat  22604     root  cwd       DIR        8,3      224      36536
> flow-cat  22604     root  rtd       DIR        8,4      584          2 /
> flow-cat  22604     root  txt       REG        8,3    88716      25290
> /usr/bin/flow-cat
> flow-cat  22604     root  mem       REG        8,4    90248        110
> /lib/ld-2.3.2.so
> flow-cat  22604     root  mem       REG        8,4    73304       5891
> /lib/tls/libnsl-2.3.2.so
> flow-cat  22604     root  mem       REG        8,4    28880       6019
> /lib/libwrap.so.0.7.6
> flow-cat  22604     root  mem       REG        8,3    67468       5598
> /usr/lib/libz.so.1.2.2
> flow-cat  22604     root  mem       REG        8,4  1254660       5886
> /lib/tls/libc-2.3.2.so
> flow-cat  22604     root  mem       REG        8,1  3548008      48872
> /var/netflow/ft/all/dec2006/ft-v05.2006-12-21.133000+0800
> flow-cat  22604     root    0u      CHR      136,0                   2
> /dev/pts/0 (deleted)
> flow-cat  22604     root    1w     FIFO        0,7            12005820 pipe
> flow-cat  22604     root    2u      CHR      136,0                   2
> /dev/pts/0 (deleted)
> flow-cat  22604     root    3r      REG        8,1  3548008      48872
> /var/netflow/ft/all/dec2006/ft-v05.2006-12-21.133000+0800
> 
> Above shows flow-cat seems to have stopped processing at Dec 21, don't
> know why.
> 
> 
> # lsof |grep flow-stat
> 
> flow-stat 22605     root  cwd       DIR        8,3      224      36536
> /usr/local/home/jayson/topcountries
> flow-stat 22605     root  rtd       DIR        8,4      584          2 /
> flow-stat 22605     root  txt       REG        8,3   130208      25291
> /usr/bin/flow-stat
> flow-stat 22605     root  mem       REG        8,4    90248        110
> /lib/ld-2.3.2.so
> flow-stat 22605     root  mem       REG        8,4    73304       5891
> /lib/tls/libnsl-2.3.2.so
> flow-stat 22605     root  mem       REG        8,4    28880       6019
> /lib/libwrap.so.0.7.6
> flow-stat 22605     root  mem       REG        8,3    67468       5598
> /usr/lib/libz.so.1.2.2
> flow-stat 22605     root  mem       REG        8,4  1254660       5886
> /lib/tls/libc-2.3.2.so
> flow-stat 22605     root    0r     FIFO        0,7            12005820 pipe
> flow-stat 22605     root    1w      REG        8,3        0      36353
> /usr/local/home/jayson/topcountries/topdestinationip
> flow-stat 22605     root    2u      CHR      136,0                   2
> /dev/pts/0 (deleted)
> 
> As you can see above, I have redirected the output to "topdestinatioip"
> But up to now, the file is still empty.
> 
> Do you know am I going to find out the progress of what I'm doing?
> I'm just afraid that the program might have stopped running and I am
> waiting for nothing now.
> 
> Thanks
> - jay
> 
> 
> 
> ------------------------------------------------------------------------
> Want to start your own business? Learn how on Yahoo! Small Business.
> <http://us.rd.yahoo.com/evt=41244/*http://smallbusiness.yahoo.com/r-index>
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Flow-tools mailing list
> [EMAIL PROTECTED]
> http://mailman.splintered.net/mailman/listinfo/flow-tools

Just as a personal preference, I like to start my flow-cat sessions in
the background, find their process id, and watch it. Literally:

flow-cat &
ps -aef|grep flow-cat
watch "lsof -p <flow-cat-pid>"

So I can see exactly what files flow-cat is processing, and watch for it
to die.

-- 
Jonathan Glass, RHCE, MCP    Information Security Engineer III
OIT Information Security       Georgia Institute of Technology
Atlanta, Georgia 30332-0700          Office/Cell: 404-385-6900
Key ID: 0xAB50FF20     Size: 2048 Bits     Created: 11/17/2004
Fingerprint: 3CD2 1BC6 4485 720B AB45 FF3E 8B3B D6F5 AB50 FF20
_______________________________________________
Flow-tools mailing list
[EMAIL PROTECTED]
http://mailman.splintered.net/mailman/listinfo/flow-tools

Reply via email to