0.45
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 23
XML::DT 0.45
XML::DT is a package for down translation of XML files. more>>
XML::DT is a package for down translation of XML files.
SYNOPSIS
use XML::DT;
%xml=( music => sub{"Music from: $cn"},
lyrics => sub{"Lyrics from: $v{name}n"},
title => sub{ uc($c) },
-default => sub{"$q:$c"} );
print dt($filename,%xml);
ABSTRACT
This module is a XML down processor. It maps tag (element) names to functions to process that element and respective contents.
This module processes XML files with an approach similar to OMNIMARK. As XML parser it uses XML::Parser or XML::LibXML module in an independent way. At configure stage, you should choose one of the back-ends.
<<lessSYNOPSIS
use XML::DT;
%xml=( music => sub{"Music from: $cn"},
lyrics => sub{"Lyrics from: $v{name}n"},
title => sub{ uc($c) },
-default => sub{"$q:$c"} );
print dt($filename,%xml);
ABSTRACT
This module is a XML down processor. It maps tag (element) names to functions to process that element and respective contents.
This module processes XML files with an approach similar to OMNIMARK. As XML parser it uses XML::Parser or XML::LibXML module in an independent way. At configure stage, you should choose one of the back-ends.
Download (0.028MB)
Added: 2006-09-14 License: Perl Artistic License Price:
1135 downloads
Download (23.3MB)
Added: 2007-07-12 License: GPL (GNU General Public License) Price:
708 downloads
Exam4Fun 0.45
Exam4Fun is an examination program designed to test your vocabulary. more>>
Exam4Fun is an examination program designed to test your vocabulary.
Exam4Fun project allows user to create their own sets of questions and choose from different type of exam(Flashcard, etc.).
Several features will be added to this quiz program.
<<lessExam4Fun project allows user to create their own sets of questions and choose from different type of exam(Flashcard, etc.).
Several features will be added to this quiz program.
Download (0.25MB)
Added: 2006-11-01 License: GPL (GNU General Public License) Price:
1196 downloads
Sys::CPU 0.45
Sys::CPU is a Perl extension for getting CPU information. more>>
Sys::CPU is a Perl extension for getting CPU information. Currently only number of CPUs supported.
SYNOPSIS
use Sys::CPU;
$number_of_cpus = Sys::CPU::cpu_count();
printf("I have %d CPUsn",$number_of_cpus);
print " Speed : ",Sys::CPU::cpu_clock(),"n";
print " Type : ",Sys::CPU::cpu_type(),"n";
In responce to a post on perlmonks.org, a module for counting the number of CPUs on a system. Support has now also been added for type of CPU and clock speed. While much of the code is from UNIX::Processors, win32 support has been added (but not tested).
<<lessSYNOPSIS
use Sys::CPU;
$number_of_cpus = Sys::CPU::cpu_count();
printf("I have %d CPUsn",$number_of_cpus);
print " Speed : ",Sys::CPU::cpu_clock(),"n";
print " Type : ",Sys::CPU::cpu_type(),"n";
In responce to a post on perlmonks.org, a module for counting the number of CPUs on a system. Support has now also been added for type of CPU and clock speed. While much of the code is from UNIX::Processors, win32 support has been added (but not tested).
Download (0.005MB)
Added: 2007-04-13 License: Perl Artistic License Price:
928 downloads
karamTop 0.45
karamTop is a superkaramba theme that parses /proc. more>>
karamTop is a superkaramba theme that parses /proc. Shows an X number of running processes with CPU, Memory usage and program name, sorted by CPU. The default number of processes to show is 5.
Idea based on the gkrelltop a plugin for GKrellM. pytop.py is the core class file. It can be used within any kind of script.
Keep in mind since it reads /proc directly, this means its Linux only. As FreeBSD and possibly other *nixes have a completely different /proc layout.
The GUI configuration isnt that great. There isnt much error checking. You can always modify the theme configuration files for fine tuning. Any more options and it just becomes too tedious to code. Right click on Karamtop, Configure Theme:
- Choose Theme
- Whether to hide processes with a cpu percent of 0
- Set the alignment for the command (program name) text
- Set the column order of the output
For theme creaters. The theme layout is designed so you can create a directory inside of the theme directory with the name of your theme. Which will contain the configuration file and images. That way you can tar up everything easily. This wont work with the skz format. I suppose maybe Ill make something that will automatically install themes in tar.gz format at some point.
Designed to work with my theme, MiniKaramba. http://www.kde-look.org/content/show.php?content=27802
A karamtop theme with an alternative background: http://www.kde-look.org/content/show.php?content=25626
Work like this is encouraged. Thanks.
Enhancements:
- Sometimes karamtop/superkaramba would run for weeks without crashing and other times it would crash relatively soon.
- Now karamtop defaults with threading off, but supports turning it back on through the config.
<<lessIdea based on the gkrelltop a plugin for GKrellM. pytop.py is the core class file. It can be used within any kind of script.
Keep in mind since it reads /proc directly, this means its Linux only. As FreeBSD and possibly other *nixes have a completely different /proc layout.
The GUI configuration isnt that great. There isnt much error checking. You can always modify the theme configuration files for fine tuning. Any more options and it just becomes too tedious to code. Right click on Karamtop, Configure Theme:
- Choose Theme
- Whether to hide processes with a cpu percent of 0
- Set the alignment for the command (program name) text
- Set the column order of the output
For theme creaters. The theme layout is designed so you can create a directory inside of the theme directory with the name of your theme. Which will contain the configuration file and images. That way you can tar up everything easily. This wont work with the skz format. I suppose maybe Ill make something that will automatically install themes in tar.gz format at some point.
Designed to work with my theme, MiniKaramba. http://www.kde-look.org/content/show.php?content=27802
A karamtop theme with an alternative background: http://www.kde-look.org/content/show.php?content=25626
Work like this is encouraged. Thanks.
Enhancements:
- Sometimes karamtop/superkaramba would run for weeks without crashing and other times it would crash relatively soon.
- Now karamtop defaults with threading off, but supports turning it back on through the config.
Download (0.063MB)
Added: 2006-06-27 License: GPL (GNU General Public License) Price:
1214 downloads
TclMagick 0.45
TclMagick is a Tcl extension that works with both the GraphicsMagick and ImageMagick image manipulation libraries. more>>
TclMagick is Tcl and Tk Interfaces to GraphicsMagick and ImageMagick
TclMagick is a Tcl extension that works with both the GraphicsMagick and ImageMagick image manipulation libraries.
TkMagick is a small, simple extension that lets you pass images back and forth between Tk and the TclMagick extension.
<<lessTclMagick is a Tcl extension that works with both the GraphicsMagick and ImageMagick image manipulation libraries.
TkMagick is a small, simple extension that lets you pass images back and forth between Tk and the TclMagick extension.
Download (0.75MB)
Added: 2006-04-26 License: Other/Proprietary License Price:
1279 downloads
Inkscape 0.45.1
Inkscape is an SVG-based graphics editor featuring alpha blending, node editing, SVG to PNG export, and more. more>>
Inkscape is an open source SVG editor with capabilities similar to Illustrator, CorelDraw, Visio, etc. Supported SVG features include basic shapes, paths, text, alpha blending, transforms, gradients, node editing, svg-to-png export, grouping, and more.
Inkscapes main motivation is to provide the Open Source community with a fully XML, SVG, and CSS2 compliant SVG drawing tool.
Additional planned work includes conversion of the codebase from C/Gtk to C++/Gtkmm, emphasizing a lightweight core with powerful features added through an extension mechanism, and establishment of a friendly, open, community-oriented development processes.
Enhancements:
- Patch [ 1667939 ]: fix crash when tile-tracing with too small clones
- Patch [ 1666532 ]: Broken link in inkview man page
- Patch [ 1665447 ]: fix for the blur quantization bug 1617082
- Patch [ 1664849 ]: fix for 1662589: increase blur margins
- Patch [ 1664004 ]: embedimage.py with fixed search order
- Patch [ 1662649 ]: markers.svg with reversed order
- Crudely improve check-markup for { markup, fix translations with bugs in that area (dz and zh_TW).
- Patch [ 1659404 ]: Set locale directory from environment variable
- Patch [ 1657072 ]: fix for bug 1654495
- Patch [ 1654636 ]: defocus dropper checkboxes
- Adding japanese.nsh and russian.nsh into files that should go into the release tarball
- Correct russian translation
- Patch [ 1651797 ]: fix for attributes when saving/save-a-copy
- Patch [ 1651752 ]: fix dropper tool
- Pattern along path extension fixed on Windows
- Include libtiff3.dll in the Windows distribution, fixing crash when opening TIFF files
- Patch [ 1673067 ]: fix blur export on flowtext
- Patch [ 1678075 ]: fix FontInstance.cpp compile issue
- Patch [ 1673502 ]: fix broken Envelope (Summers Night) effect
- Patch [ 1680182 ]: fix pattern inversion on bool op (bug 1659445)
- Patch [ 1681754 ]: fix crash when editing text with multiple tspans
- Patch [ 1682425 ]: fix bug 1679477 (crash exporting gradients to ODG)
- Khmer translation now installs correctly
- Updated Slovak translation
- Updated Bulgarian translation
- Updated Catalan translation
- Updated Czech translation
- Security: fixed format string overflows in dialogs (CVE-2007-1463) and whiteboard Jabber protocol (CVE-2007-1464).
<<lessInkscapes main motivation is to provide the Open Source community with a fully XML, SVG, and CSS2 compliant SVG drawing tool.
Additional planned work includes conversion of the codebase from C/Gtk to C++/Gtkmm, emphasizing a lightweight core with powerful features added through an extension mechanism, and establishment of a friendly, open, community-oriented development processes.
Enhancements:
- Patch [ 1667939 ]: fix crash when tile-tracing with too small clones
- Patch [ 1666532 ]: Broken link in inkview man page
- Patch [ 1665447 ]: fix for the blur quantization bug 1617082
- Patch [ 1664849 ]: fix for 1662589: increase blur margins
- Patch [ 1664004 ]: embedimage.py with fixed search order
- Patch [ 1662649 ]: markers.svg with reversed order
- Crudely improve check-markup for { markup, fix translations with bugs in that area (dz and zh_TW).
- Patch [ 1659404 ]: Set locale directory from environment variable
- Patch [ 1657072 ]: fix for bug 1654495
- Patch [ 1654636 ]: defocus dropper checkboxes
- Adding japanese.nsh and russian.nsh into files that should go into the release tarball
- Correct russian translation
- Patch [ 1651797 ]: fix for attributes when saving/save-a-copy
- Patch [ 1651752 ]: fix dropper tool
- Pattern along path extension fixed on Windows
- Include libtiff3.dll in the Windows distribution, fixing crash when opening TIFF files
- Patch [ 1673067 ]: fix blur export on flowtext
- Patch [ 1678075 ]: fix FontInstance.cpp compile issue
- Patch [ 1673502 ]: fix broken Envelope (Summers Night) effect
- Patch [ 1680182 ]: fix pattern inversion on bool op (bug 1659445)
- Patch [ 1681754 ]: fix crash when editing text with multiple tspans
- Patch [ 1682425 ]: fix bug 1679477 (crash exporting gradients to ODG)
- Khmer translation now installs correctly
- Updated Slovak translation
- Updated Bulgarian translation
- Updated Catalan translation
- Updated Czech translation
- Security: fixed format string overflows in dialogs (CVE-2007-1463) and whiteboard Jabber protocol (CVE-2007-1464).
Download (5.6MB)
Added: 2007-03-20 License: GPL (GNU General Public License) Price:
600 downloads
chkrootkit 0.45
chkrootkit is a tool to locally check for signs of a rootkit. more>>
chkrootkit is a tool to locally check for signs of a rootkit.
It contains:
- chkrootkit: shell script that checks system binaries for rootkit modification.
- ifpromisc.c: checks if the interface is in promiscuous mode.
- chklastlog.c: checks for lastlog deletions.
- chkwtmp.c: checks for wtmp deletions.
- check_wtmpx.c: checks for wtmpx deletions. (Solaris only)
- chkproc.c: checks for signs of LKM trojans.
- chkdirs.c: checks for signs of LKM trojans.
- strings.c: quick and dirty strings replacement.
- chkutmp.c: checks for utmp deletions.
The following tests are made:
aliens asp bindshell lkm rexedcs sniffer w55808 wted scalper slapper z2 chkutmp amd basename biff chfn chsh cron date du dirname echo egrep env find fingerd gpm grep hdparm su ifconfig inetd inetdconf identd init killall ldsopreload login ls lsof mail mingetty netstat named passwd pidof pop2 pop3 ps pstree rpcinfo rlogind rshd slogin sendmail sshd syslogd tar tcpd tcpdump top telnetd timed traceroute vdir w write
The following rootkits, worms and LKMs are currently detected:
01. lrk3, lrk4, lrk5, lrk6 (and variants);
02. Solaris rootkit;
03. FreeBSD rootkit;
04. t0rn (and variants);
05. Ambients Rootkit (ARK);
06. Ramen Worm;
07. rh[67]-shaper;
08. RSHA;
09. Romanian rootkit;
10. RK17;
11. Lion Worm;
12. Adore Worm;
13. LPD Worm;
14. kenny-rk;
15. Adore LKM;
16. ShitC Worm;
17. Omega Worm;
18. Wormkit Worm;
19. Maniac-RK;
20. dsc-rootkit;
21. Ducoci rootkit;
22. x.c Worm;
23. RST.b trojan;
24. duarawkz;
25. knark LKM;
26. Monkit;
27. Hidrootkit;
28. Bobkit;
29. Pizdakit;
30. t0rn v8.0;
31. Showtee;
32. Optickit;
33. T.R.K;
34. MithRas Rootkit;
35. George;
36. SucKIT;
37. Scalper;
38. Slapper A, B, C and D;
39. OpenBSD rk v1;
40. Illogic rootkit;
41. SK rootkit.
42. sebek LKM;
43. Romanian rootkit;
44. LOC rootkit;
45. shv4 rootkit;
46. Aquatica rootkit;
47. ZK rootkit;
48. 55808.A Worm;
49. TC2 Worm;
50. Volc rootkit;
51. Gold2 rootkit;
52. Anonoying rootkit;
53. Shkit rootkit;
54. AjaKit rootkit;
55. zaRwT rootkit;
56. Madalin rootkit;
57. Fu rootkit;
58. Kenga3 rootkit;
59. ESRK rootkit;
chkrootkit has been tested on: Linux 2.0.x, 2.2.x, 2.4.x and 2.6.x, FreeBSD 2.2.x, 3.x, 4.x and 5.x, OpenBSD 2.x and 3.x., NetBSD 1.6.x, Solaris 2.5.1, 2.6, 8.0 and 9.0, HP-UX 11, Tru64 and BSDI.
Enhancements:
chkutmp.c (Thanks to Jeremy Miller)
- the idea of this program is to display users that may have wiped themselves from the utmp log
chkproc.c
- fix: better support for Linux threads
chkrootkit
- new test: chkutmp
- new rootkits detected: Fu, Kenga3, ESRK
- some bug fixes
homepage redesign (Thanks to Cristine Hoepers)
- navigability improvement
- the page now validates as strict XHTML
- still lynx friendly
<<lessIt contains:
- chkrootkit: shell script that checks system binaries for rootkit modification.
- ifpromisc.c: checks if the interface is in promiscuous mode.
- chklastlog.c: checks for lastlog deletions.
- chkwtmp.c: checks for wtmp deletions.
- check_wtmpx.c: checks for wtmpx deletions. (Solaris only)
- chkproc.c: checks for signs of LKM trojans.
- chkdirs.c: checks for signs of LKM trojans.
- strings.c: quick and dirty strings replacement.
- chkutmp.c: checks for utmp deletions.
The following tests are made:
aliens asp bindshell lkm rexedcs sniffer w55808 wted scalper slapper z2 chkutmp amd basename biff chfn chsh cron date du dirname echo egrep env find fingerd gpm grep hdparm su ifconfig inetd inetdconf identd init killall ldsopreload login ls lsof mail mingetty netstat named passwd pidof pop2 pop3 ps pstree rpcinfo rlogind rshd slogin sendmail sshd syslogd tar tcpd tcpdump top telnetd timed traceroute vdir w write
The following rootkits, worms and LKMs are currently detected:
01. lrk3, lrk4, lrk5, lrk6 (and variants);
02. Solaris rootkit;
03. FreeBSD rootkit;
04. t0rn (and variants);
05. Ambients Rootkit (ARK);
06. Ramen Worm;
07. rh[67]-shaper;
08. RSHA;
09. Romanian rootkit;
10. RK17;
11. Lion Worm;
12. Adore Worm;
13. LPD Worm;
14. kenny-rk;
15. Adore LKM;
16. ShitC Worm;
17. Omega Worm;
18. Wormkit Worm;
19. Maniac-RK;
20. dsc-rootkit;
21. Ducoci rootkit;
22. x.c Worm;
23. RST.b trojan;
24. duarawkz;
25. knark LKM;
26. Monkit;
27. Hidrootkit;
28. Bobkit;
29. Pizdakit;
30. t0rn v8.0;
31. Showtee;
32. Optickit;
33. T.R.K;
34. MithRas Rootkit;
35. George;
36. SucKIT;
37. Scalper;
38. Slapper A, B, C and D;
39. OpenBSD rk v1;
40. Illogic rootkit;
41. SK rootkit.
42. sebek LKM;
43. Romanian rootkit;
44. LOC rootkit;
45. shv4 rootkit;
46. Aquatica rootkit;
47. ZK rootkit;
48. 55808.A Worm;
49. TC2 Worm;
50. Volc rootkit;
51. Gold2 rootkit;
52. Anonoying rootkit;
53. Shkit rootkit;
54. AjaKit rootkit;
55. zaRwT rootkit;
56. Madalin rootkit;
57. Fu rootkit;
58. Kenga3 rootkit;
59. ESRK rootkit;
chkrootkit has been tested on: Linux 2.0.x, 2.2.x, 2.4.x and 2.6.x, FreeBSD 2.2.x, 3.x, 4.x and 5.x, OpenBSD 2.x and 3.x., NetBSD 1.6.x, Solaris 2.5.1, 2.6, 8.0 and 9.0, HP-UX 11, Tru64 and BSDI.
Enhancements:
chkutmp.c (Thanks to Jeremy Miller)
- the idea of this program is to display users that may have wiped themselves from the utmp log
chkproc.c
- fix: better support for Linux threads
chkrootkit
- new test: chkutmp
- new rootkits detected: Fu, Kenga3, ESRK
- some bug fixes
homepage redesign (Thanks to Cristine Hoepers)
- navigability improvement
- the page now validates as strict XHTML
- still lynx friendly
Download (0.036MB)
Added: 2005-09-01 License: GPL (GNU General Public License) Price:
1522 downloads
dkftpbench 0.45
dkftpbench is an FTP benchmark program inspired by SPECweb99. more>>
dkftpbench application is an FTP benchmark program inspired by SPECweb99. The result of the benchmark is a number-of-simultaneous-users rating; after running the benchmark properly, you have a good idea how many simultaneous dialup clients a server can support. The target bandwidth per client is set at 28.8 kilobits/second to model dialup users; this is important for servers on the real Internet, which often serve thousands of clients on only 10 MBits/sec of bandwidth.
The final result of the benchmark is "the number of simultaneous 28.8 kilobits/second dialup users". To estimate this number, the benchmark starts up a new simulated user as soon as the last one has finished connecting. It stops increasing the number of users when one fails to connect, fails to maintain the desired bandwidth, or the limit specified by the -n option is reached. It runs the simulated users until the amount of time specified by the -t option has elapsed since the last simulated user birth or death; the final score is the number of users still alive at the end.
Main features:
- Compiles and runs on Linux, FreeBSD, and Solaris (or did, last I tried)
- fetches many files in parallel
- waits for each connect to finish (and then a bit) before starting next one; slows down to < 1 connect/second when it reaches 75% of desired number of users. This spreads out user activity more evenly.
- checks bandwidth continuously during each file fetch, stops adding users if any fetch too slow
- throttles each fetch to use only the specified bandwidth
- search for the max number of supported users
- Displays verbose error message when any user fails
- Aborts if it detects the client system running out of resources
- Aborts if connecting to the server takes > 5 seconds
- Aborts if it takes longer than 5 seconds to get first packet of a file
- Uses new Poller class for scalability; you can specify which Poller to use on the commandline
- Supports slow datarates (before, it only handles rates above 80kbits/sec on some systems)
- Lets you set how picky it is about datarates (before, its must be faster than threshold was fixed at 3/4 the target bandwidth)
- Supports alternative readiness notification methods like O_ASYNC and O_ONESIGFD
- Provided both as a standalone executable, and as a Corba object. (Thanks to http://corbaconf.kiev.ua/ for the Corba autoconf macros.
- Switches to BINARY mode after login. (The client API lets you choose; edit robouser.cc to skip the START_TYPE state if you want to use ASCII.)
Example:
After unpacking the sources, configure them for your system with the command
./configure
This will generate Makefile from Makefile.in.
To make sure the sources arrived intact and work properly on your system, type
make check
It will build all unit tests, and fail if any unit test fails. You must be connected to the Internet, as this will try to download a file from ftp.uu.net.
To build the system tuning tool dklimits, type
make dklimits
Run it on both the client and the server machine; make sure that the number of files it can open is about three times the desired number of users, and that the number of ports it can bind is higher than the desired number of users. You should not be running X Windows or any other programs on the client and server machines when running the benchmark.
To build the benchmark, type
make
This produces the executable dkftpbench, the tuning program dklimits, and a bunch of unit tests (executables with names ending in _test) that you can ignore for now.
Heres a simple use of dkftpbench:
./dkftpbench -n1 -hftp.uu.net -t15 -v
This tells bench to simulate one user fetching the default file from ftp.uu.net repeatedly, and stop after fifteen seconds. The program produces this output:
Option values:
-hftp.uu.net host name of ftp server
-P21 port number of ftp server
-n1 number of users
-t15 length of run (in seconds)
-b3600 desired bandwidth (in bytes per second)
-uanonymous user name
-probouser@ user password
-fusenet/rec.juggling/juggling.FAQ.Z file to fetch
-m1500 bytes per packet
-v1 verbosity
1 users
User0: fetching 22708 bytes took 6.530000 seconds, 3477 bytes per second
User0: fetching 22708 bytes took 6.530000 seconds, 3477 bytes per second
Test over. 1 users left standing.
<<lessThe final result of the benchmark is "the number of simultaneous 28.8 kilobits/second dialup users". To estimate this number, the benchmark starts up a new simulated user as soon as the last one has finished connecting. It stops increasing the number of users when one fails to connect, fails to maintain the desired bandwidth, or the limit specified by the -n option is reached. It runs the simulated users until the amount of time specified by the -t option has elapsed since the last simulated user birth or death; the final score is the number of users still alive at the end.
Main features:
- Compiles and runs on Linux, FreeBSD, and Solaris (or did, last I tried)
- fetches many files in parallel
- waits for each connect to finish (and then a bit) before starting next one; slows down to < 1 connect/second when it reaches 75% of desired number of users. This spreads out user activity more evenly.
- checks bandwidth continuously during each file fetch, stops adding users if any fetch too slow
- throttles each fetch to use only the specified bandwidth
- search for the max number of supported users
- Displays verbose error message when any user fails
- Aborts if it detects the client system running out of resources
- Aborts if connecting to the server takes > 5 seconds
- Aborts if it takes longer than 5 seconds to get first packet of a file
- Uses new Poller class for scalability; you can specify which Poller to use on the commandline
- Supports slow datarates (before, it only handles rates above 80kbits/sec on some systems)
- Lets you set how picky it is about datarates (before, its must be faster than threshold was fixed at 3/4 the target bandwidth)
- Supports alternative readiness notification methods like O_ASYNC and O_ONESIGFD
- Provided both as a standalone executable, and as a Corba object. (Thanks to http://corbaconf.kiev.ua/ for the Corba autoconf macros.
- Switches to BINARY mode after login. (The client API lets you choose; edit robouser.cc to skip the START_TYPE state if you want to use ASCII.)
Example:
After unpacking the sources, configure them for your system with the command
./configure
This will generate Makefile from Makefile.in.
To make sure the sources arrived intact and work properly on your system, type
make check
It will build all unit tests, and fail if any unit test fails. You must be connected to the Internet, as this will try to download a file from ftp.uu.net.
To build the system tuning tool dklimits, type
make dklimits
Run it on both the client and the server machine; make sure that the number of files it can open is about three times the desired number of users, and that the number of ports it can bind is higher than the desired number of users. You should not be running X Windows or any other programs on the client and server machines when running the benchmark.
To build the benchmark, type
make
This produces the executable dkftpbench, the tuning program dklimits, and a bunch of unit tests (executables with names ending in _test) that you can ignore for now.
Heres a simple use of dkftpbench:
./dkftpbench -n1 -hftp.uu.net -t15 -v
This tells bench to simulate one user fetching the default file from ftp.uu.net repeatedly, and stop after fifteen seconds. The program produces this output:
Option values:
-hftp.uu.net host name of ftp server
-P21 port number of ftp server
-n1 number of users
-t15 length of run (in seconds)
-b3600 desired bandwidth (in bytes per second)
-uanonymous user name
-probouser@ user password
-fusenet/rec.juggling/juggling.FAQ.Z file to fetch
-m1500 bytes per packet
-v1 verbosity
1 users
User0: fetching 22708 bytes took 6.530000 seconds, 3477 bytes per second
User0: fetching 22708 bytes took 6.530000 seconds, 3477 bytes per second
Test over. 1 users left standing.
Download (0.26MB)
Added: 2007-06-26 License: GPL (GNU General Public License) Price:
853 downloads
log_analysis 0.45
log_analysis is a log file analysis engine that extracts relevant data for any of the recognised log. more>>
log_analysis is a log file analysis engine that extracts relevant data for any of the recognised log messages and produces a summary that is much easier to read.
Main features:
- Logs contain lots of extraneous stuff that I want to be logged, but that I dont want to sift through when I review logs (ie. routine, error-free daemon operation.)
- Logs contain a lot of repetition, which drowns out the interesting entries.
- Noting repetition can be tricky because each entry usually has extra features to make it unique, such as a date, maybe a PID (ie. for syslog), and maybe application-specific information (ie. sendmail queue IDs.)
- One needs to remember to review them. :)
- One needs to be root to looks at logs for some OSs.
- On most systems, looking at the logs for just one day can be a pain.
- If I attack each box I deal with and write a separate script to do all this, Ill waste a lot of time duplicating effort.
- Writing patterns is a pain even if you know regular expressions.
log_analysis is my solution to these problems. It goes through several different kinds of logs (currently syslog, wtmp, and sulog), over some period (defaults to yesterday). It strips out the date and PID, and throws away certain entries. Then it tries each entry against a list of perl regular expressions. Each perl regular expression is associated with a category name and a rule for extracting data. When theres a match, the data-extracting rule is applied, and filed under the category.
If a log entry is unknown, its filed under a special category for unknowns. Identical entries for a given category are sorted and counted. Theres an option to mail the output, so you can just run it out of cron. You can also save a local copy of the output. If you prefer to PGP-mail yourself the output, you can do this, too. The whole thing is designed to be easily extended, complete with an easy plug-in interface. The default mode is for reporting, but it also "real" and "gui" modes for continuous monitoring, complete with action support. Oh, and you can edit patterns in a GUI that helps write regular expressions quickly and easily.
Security
The program needs to run with permissions to read your log files in order to be useful, which usually means root. It does not default to SUID root, and I recommend not making it SUID, so just run it as root (ie. manually or out of cron). Ive tried to avoid temp files everywhere that I can, and in the one case where I do use a temp file, I make sure to use the POSIX tmpnam function instead of trying to make up my own temp file algorithm. The default umask is 077. If you use action commands, there is nothing to stop you from using parts of the log message in insecure ways, so for goodness sake, be careful.
Local extensions
log_analysis already has lots of rules, but chances are that you have log entries that arent already covered. So, log_analysis can easily be extended via a local config file, as documented in the log_analysis manpage. Theres even an easy way to do modular plug-ins.
Enhancements:
- This release includes a "find" feature in the GUI, various bugfixes, and assorted minor features.
<<lessMain features:
- Logs contain lots of extraneous stuff that I want to be logged, but that I dont want to sift through when I review logs (ie. routine, error-free daemon operation.)
- Logs contain a lot of repetition, which drowns out the interesting entries.
- Noting repetition can be tricky because each entry usually has extra features to make it unique, such as a date, maybe a PID (ie. for syslog), and maybe application-specific information (ie. sendmail queue IDs.)
- One needs to remember to review them. :)
- One needs to be root to looks at logs for some OSs.
- On most systems, looking at the logs for just one day can be a pain.
- If I attack each box I deal with and write a separate script to do all this, Ill waste a lot of time duplicating effort.
- Writing patterns is a pain even if you know regular expressions.
log_analysis is my solution to these problems. It goes through several different kinds of logs (currently syslog, wtmp, and sulog), over some period (defaults to yesterday). It strips out the date and PID, and throws away certain entries. Then it tries each entry against a list of perl regular expressions. Each perl regular expression is associated with a category name and a rule for extracting data. When theres a match, the data-extracting rule is applied, and filed under the category.
If a log entry is unknown, its filed under a special category for unknowns. Identical entries for a given category are sorted and counted. Theres an option to mail the output, so you can just run it out of cron. You can also save a local copy of the output. If you prefer to PGP-mail yourself the output, you can do this, too. The whole thing is designed to be easily extended, complete with an easy plug-in interface. The default mode is for reporting, but it also "real" and "gui" modes for continuous monitoring, complete with action support. Oh, and you can edit patterns in a GUI that helps write regular expressions quickly and easily.
Security
The program needs to run with permissions to read your log files in order to be useful, which usually means root. It does not default to SUID root, and I recommend not making it SUID, so just run it as root (ie. manually or out of cron). Ive tried to avoid temp files everywhere that I can, and in the one case where I do use a temp file, I make sure to use the POSIX tmpnam function instead of trying to make up my own temp file algorithm. The default umask is 077. If you use action commands, there is nothing to stop you from using parts of the log message in insecure ways, so for goodness sake, be careful.
Local extensions
log_analysis already has lots of rules, but chances are that you have log entries that arent already covered. So, log_analysis can easily be extended via a local config file, as documented in the log_analysis manpage. Theres even an easy way to do modular plug-ins.
Enhancements:
- This release includes a "find" feature in the GUI, various bugfixes, and assorted minor features.
Download (0.13MB)
Added: 2006-10-04 License: GPL (GNU General Public License) Price:
1115 downloads
Acme::Pythonic 0.45
Acme::Pythonic is a Python whitespace conventions for Perl. more>>
Acme::Pythonic is a module that contains Python whitespace conventions for Perl.
SYNOPSIS
use Acme::Pythonic; # this semicolon yet needed
sub delete_edges:
my $G = shift
while my ($u, $v) = splice(@_, 0, 2):
if defined $v:
$G->delete_edge($u, $v)
else:
my @e = $G->edges($u)
while ($u, $v) = splice(@e, 0, 2):
$G->delete_edge($u, $v)
Acme::Pythonic brings Python whitespace conventions to Perl. Just use it and Pythonic code will become valid on the fly. No file is generated, no file is modified.
This module is thought for those who embrace contradictions. A humble contribution for walkers of the Whitespace Matters Way in their pursuit of highest realization, only attained with SuperPython.
<<lessSYNOPSIS
use Acme::Pythonic; # this semicolon yet needed
sub delete_edges:
my $G = shift
while my ($u, $v) = splice(@_, 0, 2):
if defined $v:
$G->delete_edge($u, $v)
else:
my @e = $G->edges($u)
while ($u, $v) = splice(@e, 0, 2):
$G->delete_edge($u, $v)
Acme::Pythonic brings Python whitespace conventions to Perl. Just use it and Pythonic code will become valid on the fly. No file is generated, no file is modified.
This module is thought for those who embrace contradictions. A humble contribution for walkers of the Whitespace Matters Way in their pursuit of highest realization, only attained with SuperPython.
Download (0.020MB)
Added: 2007-04-19 License: Perl Artistic License Price:
918 downloads
PerlPoint::Tags 0.45
PerlPoint::Tags is a Perl module that can processes PerlPoint tag declarations. more>>
PerlPoint::Tags is a Perl module that can process PerlPoint tag declarations.
SYNOPSIS
# declare a tag declaration package
package PerlPoint::Tags::New;
# declare base "class"
use base qw(PerlPoint::Tags);
PerlPoint is built a modularized way. The base packages provide parsing and stream processing for all translators into target formats and are therefore intended to be as general as possible. Thats why they not even define tags, because every translator author may wish to provide own tags special to the addressed target projector (or format, respectively). On the other hand, the parser needs to know about tags to recognize them correctly. That is where this module comes in. It serves as a base of tag declaration modules by providing a general import() method to be inherited by them. This method scans the invoking module for certain data structures containing tag declarations and imports these data into a structure in its own namespace. The parser knows about this PerlPoint::Tags collection and makes it the base of its tag handling.
It is recommended to have a "top level" tag declaration module for each PerlPoint translator, so there could be a PerlPoint::Tags::HTML, a PerlPoint::Tags::Latex, PerlPoint::Tags::SDF, a PerlPoint::Tags::XML and so on. (These modules of course may simply invoke lower level declarations.)
Note: We are speaking in terms of "classes" here but of course we are actually only using the mechanism of import() together with inheritance to provide an intuitive and easy to use way of declaration.
As an additional feature, the module provides a method addTagSets() to allow translator users to declare tags additionally.
<<lessSYNOPSIS
# declare a tag declaration package
package PerlPoint::Tags::New;
# declare base "class"
use base qw(PerlPoint::Tags);
PerlPoint is built a modularized way. The base packages provide parsing and stream processing for all translators into target formats and are therefore intended to be as general as possible. Thats why they not even define tags, because every translator author may wish to provide own tags special to the addressed target projector (or format, respectively). On the other hand, the parser needs to know about tags to recognize them correctly. That is where this module comes in. It serves as a base of tag declaration modules by providing a general import() method to be inherited by them. This method scans the invoking module for certain data structures containing tag declarations and imports these data into a structure in its own namespace. The parser knows about this PerlPoint::Tags collection and makes it the base of its tag handling.
It is recommended to have a "top level" tag declaration module for each PerlPoint translator, so there could be a PerlPoint::Tags::HTML, a PerlPoint::Tags::Latex, PerlPoint::Tags::SDF, a PerlPoint::Tags::XML and so on. (These modules of course may simply invoke lower level declarations.)
Note: We are speaking in terms of "classes" here but of course we are actually only using the mechanism of import() together with inheritance to provide an intuitive and easy to use way of declaration.
As an additional feature, the module provides a method addTagSets() to allow translator users to declare tags additionally.
Download (0.41MB)
Added: 2007-02-13 License: Perl Artistic License Price:
983 downloads
Netscape::Cache 0.45
Netscape::Cache is a Perl object class for accessing Netscape cache files. more>>
Netscape::Cache is a Perl object class for accessing Netscape cache files.
SYNOPSIS
The object oriented interface:
use Netscape::Cache;
$cache = new Netscape::Cache;
while (defined($url = $cache->next_url)) {
print $url, "n";
}
while (defined($o = $cache->next_object)) {
print
$o->{URL}, "n",
$o->{CACHEFILE}, "n",
$o->{LAST_MODIFIED}, "n",
$o->{MIME_TYPE}, "n";
}
The TIEHASH interface:
use Netscape::Cache;
tie %cache, Netscape::Cache;
foreach (sort keys %cache) {
print $cache{$_}->{URL}, "n";
}
The Netscape::Cache module implements an object class for accessing the filenames and URLs of the cache files used by the Netscape web browser.
Note: You can also use the undocumented pseudo-URLs about:cache, about:memory-cache and about:global-history to access your disk cache, memory cache and global history.
There is also an interface for using tied hashes.
Netscape uses the old Berkeley DB format (version 1.85) for its cache index index.db. Version 2.x.x is incompatible with the old format (db_intro(3)), so you have either to downgrade or to convert the database using db_dump185 and db_load. See convert_185_2xx for a (experimental) converter function.
<<lessSYNOPSIS
The object oriented interface:
use Netscape::Cache;
$cache = new Netscape::Cache;
while (defined($url = $cache->next_url)) {
print $url, "n";
}
while (defined($o = $cache->next_object)) {
$o->{URL}, "n",
$o->{CACHEFILE}, "n",
$o->{LAST_MODIFIED}, "n",
$o->{MIME_TYPE}, "n";
}
The TIEHASH interface:
use Netscape::Cache;
tie %cache, Netscape::Cache;
foreach (sort keys %cache) {
print $cache{$_}->{URL}, "n";
}
The Netscape::Cache module implements an object class for accessing the filenames and URLs of the cache files used by the Netscape web browser.
Note: You can also use the undocumented pseudo-URLs about:cache, about:memory-cache and about:global-history to access your disk cache, memory cache and global history.
There is also an interface for using tied hashes.
Netscape uses the old Berkeley DB format (version 1.85) for its cache index index.db. Version 2.x.x is incompatible with the old format (db_intro(3)), so you have either to downgrade or to convert the database using db_dump185 and db_load. See convert_185_2xx for a (experimental) converter function.
Download (0.016MB)
Added: 2007-03-24 License: Perl Artistic License Price:
945 downloads
PerlPoint::Parser 0.45
PerlPoint::Parser Perl module is a PerlPoint Parser. more>>
PerlPoint::Parser Perl module is a PerlPoint Parser.
SYNOPSIS
# load the module:
use PerlPoint::Parser;
# build the parser and run it
# to get intermediate data in @stream
my ($parser)=new PerlPoint::Parser;
$parser->run(
stream => @stream,
files => @files,
);
The PerlPoint format, initially designed by Tom Christiansen, is intended to provide a simple and portable way to generate slides without the need of a proprietary product. Slides can be prepared in a text editor of your choice, generated on any platform where you find perl, and presented by any browser which can render the chosen output format.
To sum it up, PerlPoint Software takes an ASCII text and transforms it into slides written in a certain document description language. This is, by tradition, usually HTML, but you may decide to use another format like XML, SGML, TeX or whatever you want.
Well, this sounds fine, but how to build a translator which transforms ASCII into the output format of your choice? Thats what PerlPoint::Parser is made for. It performs the first translation step by parsing ASCII and transforming it into an intermediate stream format, which can be processed by a subsequently called translator backend. By separating parsing and output generation we get the flexibility to write as many backends as necessary by using the same parser frontend for all translators.
PerlPoint::Parser supports the complete GRAMMAR with exception of certain tags. Tags are supported the most common way: the parser recognizes any tag which is declared by the author of a translator. This way the parser can be used for various flavours of the PerlPoint language without having to be modified. So, if there is a need of a certain new flag, it can quickly be added without any change to PerlPoint::Parser.
The following chapters describe the input format (GRAMMAR) and the generated stream format (STREAM FORMAT). Finally, the class methods are described to show you how to build a parser.
<<lessSYNOPSIS
# load the module:
use PerlPoint::Parser;
# build the parser and run it
# to get intermediate data in @stream
my ($parser)=new PerlPoint::Parser;
$parser->run(
stream => @stream,
files => @files,
);
The PerlPoint format, initially designed by Tom Christiansen, is intended to provide a simple and portable way to generate slides without the need of a proprietary product. Slides can be prepared in a text editor of your choice, generated on any platform where you find perl, and presented by any browser which can render the chosen output format.
To sum it up, PerlPoint Software takes an ASCII text and transforms it into slides written in a certain document description language. This is, by tradition, usually HTML, but you may decide to use another format like XML, SGML, TeX or whatever you want.
Well, this sounds fine, but how to build a translator which transforms ASCII into the output format of your choice? Thats what PerlPoint::Parser is made for. It performs the first translation step by parsing ASCII and transforming it into an intermediate stream format, which can be processed by a subsequently called translator backend. By separating parsing and output generation we get the flexibility to write as many backends as necessary by using the same parser frontend for all translators.
PerlPoint::Parser supports the complete GRAMMAR with exception of certain tags. Tags are supported the most common way: the parser recognizes any tag which is declared by the author of a translator. This way the parser can be used for various flavours of the PerlPoint language without having to be modified. So, if there is a need of a certain new flag, it can quickly be added without any change to PerlPoint::Parser.
The following chapters describe the input format (GRAMMAR) and the generated stream format (STREAM FORMAT). Finally, the class methods are described to show you how to build a parser.
Download (0.41MB)
Added: 2007-02-12 License: Perl Artistic License Price:
985 downloads
PerlPoint::Anchors 0.45
PerlPoint::Anchors is a simple anchor collection class. more>>
PerlPoint::Anchors is a simple anchor collection class.
SYNOPSIS
# make a new object
my $anchors=new PerlPoint::Anchors;
# register an anchor
$anchors->add(page number, 500);
# check an anchor for being known
... if $anchors->query(page number);
# get a list of all registered anchors
my %regAnchors=%{$anchors->query};
Anchors are no part of the PerlPoint language definition, but used by various tags which either define or reference them. To support those tags, this simple collection class was implemented. It provides a consistent and general interface for dealing with anchors.
By using the module, one can register an anchor together with a value and query these data later, to check if a certain anchor was already registered or to access the anchor related value. A value can be any valid Perl data. Additionally, the complete collection can be requested.
<<lessSYNOPSIS
# make a new object
my $anchors=new PerlPoint::Anchors;
# register an anchor
$anchors->add(page number, 500);
# check an anchor for being known
... if $anchors->query(page number);
# get a list of all registered anchors
my %regAnchors=%{$anchors->query};
Anchors are no part of the PerlPoint language definition, but used by various tags which either define or reference them. To support those tags, this simple collection class was implemented. It provides a consistent and general interface for dealing with anchors.
By using the module, one can register an anchor together with a value and query these data later, to check if a certain anchor was already registered or to access the anchor related value. A value can be any valid Perl data. Additionally, the complete collection can be requested.
Download (0.41MB)
Added: 2007-02-19 License: Perl Artistic License Price:
978 downloads
Secleted [ 0 ] software to compare
- Page: 1 of 2
- 1
- 2
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above 0.45 search only lists software in full, demo and trial versions for free download. Download links are directly from our mirror sites or publisher sites, torrent files or links from rapidshare.com, yousendit.com or megaupload.com are not allowed