03-03-2005
There are too many to name. I don't want to persuade you into a product you don't need. Seach the web and you should be able to find several. I also work for a company that makes several of them and don't want to be biased.
7 More Discussions You Might Find Interesting
1. News, Links, Events and Announcements
About 4 years ago I wrote this tool inspired by Rob Urban's collect tool for DEC's Tru64 Unix. What makes this tool as different as collect was in its day is its ability to run at a low overhead and collect tons of stuff. I've expanded the general concept and even include data not available in... (0 Replies)
Discussion started by: MarkSeger
0 Replies
2. HP-UX
Hello,
there. We want to write application on HP-UX to monitor system resource,such as CPU,Network Traffic Load,Disk Usage,etc. Anyone know these API functions except the system command ? thanks. (6 Replies)
Discussion started by: Frank2004
6 Replies
3. Shell Programming and Scripting
Hello,
I would like to write a script that use the display as an input.
In the display there is a list of file. I want to use it as an array and this would be the input in my script. Does somebody know how do I make it? (2 Replies)
Discussion started by: mig8
2 Replies
4. AIX
Dear experts ,
Pls advice for any good Tool to monitor the CPU and performance of AIX the system ..
to keep monitoring to show me the utilization of that system .. (12 Replies)
Discussion started by: Mr.AIX
12 Replies
5. Programming
Hi,
May i know the tools which will give the below details in a consolidated fashion for some 'X' duration in single and multicore processors,
1) How many times and how long scheduler code and kernel threads are executing ?
2) Details about each process, time spent in each state (run, wait... (0 Replies)
Discussion started by: tkarthi85
0 Replies
6. Hardware
Hi, I am experiencing troubles with dual monitors in fedora 16. During boot time both monitors are working, but when system starts one monitor automatically shut down. It happend out of the blue. Some time before when I updated system this happend but then I booted older kernel release and... (0 Replies)
Discussion started by: wakatana
0 Replies
7. Infrastructure Monitoring
Sorry if this is the wrong forum
Searching for Saas Monitor service which monitor my servers which are sitting in different providers .
This monitor tool will take as less CPU as possible , and will send info about the server to main Dashboard.
The info I need is CPU / RAM / my servers status (... (1 Reply)
Discussion started by: umen
1 Replies
LEARN ABOUT DEBIAN
anyevent::impl::tk
AnyEvent::Impl::Tk(3pm) User Contributed Perl Documentation AnyEvent::Impl::Tk(3pm)
NAME
AnyEvent::Impl::Tk - AnyEvent adaptor for Tk
SYNOPSIS
use AnyEvent;
use Tk;
# this module gets loaded automatically as required
DESCRIPTION
This module provides transparent support for AnyEvent. You don't have to do anything to make Tk work with AnyEvent except by loading Tk
before creating the first AnyEvent watcher.
Tk is buggy. Tk is extremely buggy. Tk is so unbelievably buggy that for each bug reported and fixed, you get one new bug followed by
reintroduction of the old bug in a later revision. It is also basically unmaintained: the maintainers are not even interested in improving
the situation - reporting bugs is considered rude, and fixing bugs is considered changing holy code, so it's apparently better to leave it
broken.
I regularly run out of words to describe how bad it really is.
To work around some of the many, many bugs in Tk that don't get fixed, this adaptor dup()'s all filehandles that get passed into its I/O
watchers, so if you register a read and a write watcher for one fh, AnyEvent will create two additional file descriptors (and handles).
This creates a high overhead and is slow, but seems to work around most known bugs in Tk::fileevent on 32 bit architectures (Tk seems to be
terminally broken on 64 bit, do not expect more than 10 or so watchers to work on 64 bit machines).
Do not expect these workarounds to avoid segfaults and crashes inside Tk.
Note also that Tk event ids wrap around after 2**32 or so events, which on my machine can happen within less than 12 hours, after which Tk
will stomp on random other events and kill them. So don't run Tk programs for more than an hour or so.
To be able to access the Tk event loop, this module creates a main window and withdraws it immediately. This might cause flickering on some
platforms, but Tk perversely requires a window to be able to wait for file handle readyness notifications. This window is always created
(in this version of AnyEvent) and can be accessed as $AnyEvent::Impl::Tk::mw.
SEE ALSO
AnyEvent, Tk.
AUTHOR
Marc Lehmann <schmorp@schmorp.de>
http://anyevent.schmorp.de
perl v5.14.2 2012-04-08 AnyEvent::Impl::Tk(3pm)