linux-kernel - REAL-TIME GRAPHICAL BANDWIDTH/CPU/RAM MONITOR FOR LINUX

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <1168894543.6007.2.camel@localhost.localdomain>
Date:	Mon, 15 Jan 2007 21:55:43 +0100
From:	Vincent Perrier <clowncoder@...wncode.net>
To:	linux-kernel@...r.kernel.org
Subject: REAL-TIME GRAPHICAL BANDWIDTH/CPU/RAM MONITOR FOR LINUX

 Hello,
 I have just finished coding a REAL-TIME GRAPHICAL MONITOR for linux.

 The most difficult function of the kernel-embedded spy has been the
 catching of the uid and the  name of a process for a spyed-upon
 connection (udp or tcp). I had some nasty freezes before my last resort
 solution which is not completely satisfying (I now use local_save_flags
 very punctually).

 For the real hackers who would help to resolve this issue, have a look
 in the klownspy directory, monitor.c, try_to_get_to_the_socket_owner
 function, this function is called from bottom half (or softirq?)
 through a subscription to all packets with dev_add_pack.

 Another thing: BionicClown007 brings back amongs other things the
 memory used in the system, at a point in the computation, we need
 total_swapcache_pages (= swapper_space.nrpages) and this symbol is
 not exported (see collect.c).
 Is there an other way to get the used memory info?

 The BionicClown007 is at http://clowncode.net,
 BionicClown007 is the total rewriting of the ClownToolKit.

 Regards to all
 Vincent Perrier

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/