Free echo 1 software for linux

ETrace is a configurable static port network tracing tool, similar to traceroute, but supporting ICMP, TCP, UDP and other IP protocols.

Usage:

etrace [ -BbCcnv ] [ -p profile ] [ -F config ] [ -i interface ] [ -I icmp-type ] [ -T port ] [ -U port ] [ -P protocol ] [ -r probe-count ] [ -t timeout ] [ -1 hop ] [ -h hop ] [ -m hop ] [ -A address ] [ -s port ] [ -f flags ] [ -d data ] [ -D data-file ] [ -R count ] [ -q seq] [ -w window ] target [...]

Options:

etrace has a wealth of options ranging in function from controlling output to the detailed construction of trace packets.

Profile Options:

A profile is a pre-configured list of options stored in a shared, or user specific configuration file. By defining profiles, complex etrace option sets can be easily accessed with a single command line option.

-p, --profile
Specify a profile.
-C, --clear
Clear the current list of probes. This option can be used to allow a profile to inherit options from another profile, but specify its own list of probes.
-F, --config
Specify an alternative profiles file.

Interface options

-i, --interface
Specify interface. If unspecified, etrace will examine the routing table and select the most appropriate interface for each target address.
-c, --promisc
Put in interface into promiscuous mode. As this option increases the load on the system in general, it should only be used if spoofing of source packets address is enabled with the "-A" option.
Trace Type Options
-I, --icmp
Specify an ICMP trace and the packet type to use. ICMP traces may use Echo (E or P), Timestamp (T or S), Netmask (N or M) or Info (I). The default trace probe is an ICMP Echo.
-h, --hop
Specify a specific hop to investigate.
-m, --maximum
Specify the maximum number of hops.
-r, --probes
Set the maximum number of probes to send per hop. The default is 3.
-t, --timeout
Set the maximum amount of time, in milli-seconds, to wait for a response to a probe. The default is 3000 (three seconds).

Packet Construction Options

-A, --address
Specify the source IP address of generated packets.
-s, --source
Set the source port of the generated probe packets. If unspecified, etrace uses a random high port.
-f, --flags
Specify TCP and/or IP flags. Takes a comma delimitered list of any of the following flags: RF, DF, MF, FIN, SYN, RST, PSH, ACK, URG, ECE, CWR (Default: SYN)
-d, --data
Specify the data content of generated probe packets. Standard meta-characters are recognised (e.g. "nt") as are binary values given in octal (e.g. " 00x00");
-D, --data-file
Load the data content of the generated probe packets from the specified file. Filenames beginning with @ a loaded from the etrace shared data directory (usually /usr/local/share/etrace). etrace currently ships with the following predfined packet data files: dns, ike.
-R, --random
Fill the data content of the generated probe packets with the specified number of random bytes.
-b, --badcksum
Generate and send probe packets with bad checksums.
-q, --seq
Specify the TCP sequence number.
-w, --window
Specify the TCP window size.

Output Options

-v, --verbose
Increase output verbosity.
-B, --debug
Enable debugging output.
-n, --numeric
Disable name resolution.

Examples:

etrace www.sample.com

Launches a trace ICMP Echo, the default, trace to www.sample.com. Specifiying the options "-I E" whould accomplish the same results.

etrace -T 80 www.sample.com

Similar to the previous example, except the trace is performed on TCP port 80.

etrace --udp 53 --data-file @dns ns.sample.com

Starts are trace to ns.sample.com on UDP port 53 with the trace packets containing data loaded from the file /usr/local/share/etrace/dns (a file supplied with etrace that contains a simple dns request to resolve 127.0.0.1).

etrace -p dns -p fast ns.sample.com

The default profiles shipped with etrace include "dns" (which equates to the options shown in the previous example) and "fast" (which decreases both timeouts and the number of probes sent for each hop, as well as disabling name resolution). Profiles are stackable, with latter options overriding those specified in earlier profiles.

Ucron is a cron daemon allows crontabs to be centrally managed and distributed to any number of nodes.
Ucron - A Centrally Managed Cron Daemon - is cron daemon that allows crontabs to be centrally managed and distributed to any number of nodes. It runs alongside the systems standard crond. It runs alongside the systems standard crond.
The crontabs of all nodes are stored in any database supported by LibSDB.
This program is known to work on Linux, HP-UX and Solaris. Other Unixes should work as well; editing the Makefile may be necessary.
Installation:
Create a group called ucron and a user called ucron. The user should
have /opt/ucron as home directory and /opt/ucron/myshell as shell.
Unfortunately those dont exist until we install ucron, so for now:
vi /etc/group
useradd -g ucron
No configuration script, just type:
make
make install
By default the programs are installed into /opt/ucron. This can
be changed in the Makefile or by typing (example):
make install PREFIX=/usr/local BINDIR=/usr/local/bin
Make sure you understand what you break before attempting to
relocate anything.
Now we can fix the user created earlier:
usermod -d /opt/ucron -s /opt/ucron/myshell ucron
Finally fix your start scripts so ucrond will run automatically.
Highly system specific, but for Slackware Linux stick this line in
/etc/rc.d/rc.local:
/opt/ucron/ucrond
For Solaris, put this script in /etc/init.d/ucron:
#!/bin/sh
case "$1" in
start )
/opt/ucron/ucrond
;;
stop )
pkill ucrond
;;
- )
echo $0 start | stop
;;
esac
and link it to /etc/rc0.d/K01ucron and /etc/rc2.d/S99ucron.
Enhancements:
- Updated Makefile.

jZeno is a meta-project that integrates a collection of java open source libraries, to form a ready-to-use web development environment. jZeno is made to allow people to create web applications by using pure java development as much as possible. The main architectural goal of Largely reducing the need to know technologies like javascript, HTML, CSS, database specific SQL, and tons of different APIs.
Limiting the amount of APIs, technologies and programming styles allows developers to learn a smaller set of skills much deeper. We think this set of skills should be : a thorough understanding of java, OO development and design patterns.
We decided to create jZeno after growing more and more frustrated with JSP and Struts over the years. We hoped JSF would improve things but have come to the conclusion that it is mainly a commercially-driven API that does not really make development life any easier. So we started looking further and came across Echo, a toolkit for developing web applications in pure java. In a nutshell Echo provides you with an implementation of the Swing API for developing web applications. We have created an optimized version of the Echo toolkit to allow partial, and highly compressed updates of web pages, providing AJAX like performance (available in the upcoming 0.9 release).
While Echo provides an easy way of creating the presentation layer of a web application, some glue was still missing to turn it into a rapid development platform. So we decided to add a set of easy to use dynamic components, that provide an easy way to do data-binding, validation, event handling and such. Many useful components are also provided by the EchoPoint library, a collection of rich Echo components.
Besides the presentation layer jZeno also provides a number of services for facilitating the creation of business facades. This environment is similar to stateless session beans in the EJB specification, but witout the overhead of EJBs. These services include transaction management, dead-lock detection and retrying, performance monitoring, security checking, etc...
jZeno also uses Hibernate for O/R mapping inside you business facades. Besides these major functions jZeno contains out-of-the-box solutions for a host of other features any real-life web application needs. This inluces things like genrating reports in a pdf,xls,rtf and other formats (through JasperReports). It also includes live performance monitoring (JAMon) and heap monitoring of your application in its production environment, among other features...
jZeno applications have a traditional layered architecture. The tradidional 3 tiers are seperated : the presentation tier, the business tier and the domain model. The first tier is created by using the jZeno dynamic components and the lower level Echo and EchoPoint components. The business tier contains support for running your business logic, decorated with a stack of aspects that together create an environment very similar to stateless session beans (but with less requirements and configuration overhead). The domain model tier is basically the O/R mapping provided by Hibernate. jZeno provides a tightly integrated environment for all these tiers. In the future support for deploying on an EJB container may be added if required.
Enhancements:
- A bug in errormessagescomponent (warnings) has been fixed.
- Validation has been fixed to pre-render/rebind invisible pages on DynaTables before validation.
- The TTL for DNS caching has been set to a maximum of 5 minutes.
- SessionSyncFilter will always serialize unless using an image/script service.
- A McKoi startup bug when using hibernate annotations has been fixed.
- Processing of radio buttons with action listeners has been fixed.
- BigDecimalViewer and ComponentUI have been added for consistency.
- A bug in the NewsTicker component has been fixed.

camE is a Webcam grabber designed for video4linux devices. It is based on the xawtv webcam app, but extended to use imlib2 for applying antialised, blended truetype fonts to the image before upload.
A large number of new options have been added including scp support (in addition to ftp), image archiving, and much more. It runs as a daemon and needs no X connection to operate.
Main features:
- ttf fonts
- blended transparent text
- title text
- options in ~/.camErc
- message read from separate file (eg echo "eating my dinner" > ~/.caminfo)
- color the text as you like
- text background any color/alpha value
- scp support for uploading
- ftp support for uploading using libcurl, reconnect for each upload or reuse one connection
- proper logging to file
- user defined actions to be run before and after shots, and after upload (use to play sounds, beep, run scripts, copy files, whatever)
- file for stopping uploads temporarily (touch ~/BLOCKCAM to stop shooting, remove it to resume)
- now a proper daemon that can run without X forever if wanted
- control of brightness, contrast, gamma, hue, colour, etc
- control of framerate and use of snapshot mode for Philips cams
- image archiving (timestamped into a directory of your choice after upload), every frame or every n frames
- lag reduction (for some cams, when mmaped, the image grabbed lags behind the cam by up to 20 seconds. I use lag_reduce 5 in my ~/.camErc for example. This takes 5 shots in a row, which clears the mmap buffers, and then keeps the last shot, lag-free)

Das_Watchdog is a program heavily and shamefully inspired by the rt_watchdog program made by Florian Schmidt.

However, this one has some improvements:

1. It works with 2.4 kernels as well as 2.6.
2. Instead of permanently setting all realtime processes to run non-realtime, das_watchdog only sets them temporary.
3. When the watchdog kicks in, an X window should pop up that tells you whats happening. (just close it after reading the message).

Installation:

make
cp das_watchdog /usr/local/sbin/
echo /usr/local/sbin/das_watchdog >/dev/null & >>/etc/rc.sysinit
reboot

Usage:

Whenever a program locks up the machine, the watchdog temporarily sets all realtime process to non-realtime for 8 seconds. You will get an xmessage window up on the screen whenever that happens.

To test it, run the attached program "test_rt", which immediatley freezes your machine. However, a window should pop up after about 5-6 seconds telling you that the watchdog set the process to non-realtime.

Use the "--force" option to set the priority of all timer processes to SCHED_FIFO/99.

If the xmessage window does not show up, it can be because the user logged into the machine has the home area placed on a non-root mounted disk.

When that happens, root is unable to read the users .Xauthority file. Unfortunately,
I have no (good) solution for that situation. But if thats not the case, please
report the problem to me.

mimic provides a server that mimics ftpd and telnetd servers.

mimic is a server that mimics Internet servers. It includes imitators for ftpd and telnetd, and can be extended with scripting to support other types of imitation. Users will believe they are connected to authentic services (such as ftpd or telnetd) but will never be able to log in.

Everything that they type is logged. In addition, scripting new imitator services is simple. The program includes a one-liner example of a fully-functional echo server.

The projects goal is to create a script for imitating most, if not all, popular Internet services.

Compilation:

Use: make all, make myftpd, make mytelnetd or make myscript

Your ftpd and telnetd servers will be found in ftpd/ and telnetd/ respectively.
Your scripted server will be found in script/.

php-json is an extremely fast PHP C extension for JSON (JavaScript Object Notation) serialisation. php-json project library uses a forked version of json-c.
It can be used in conjunction with XMLHTTPRequest to exchange JavaScript-encoded data with a browser.
Usage:
A simple ./configure; make; make install should do the trick. Make sure to add an extension=json.so line to your php.ini/php.d. Note: you need to compile php-json with gcc 3.x and up.
Then, just use json_encode to encode your PHP values into JSON, and json_decode to decode JSON into a PHP value.
For example:
$output = json_encode($val);
echo $output."n";
Would produce:
{ "abc": 12, "foo": "bar", "bool0": false, "bool1": true, "arr": [ 1, 2, 3, null, 5 ], "float": 1.2345 }
While:
$input = { "abc": 12, "foo": "bar", "bool0": false, "bool1": true, "arr": [ 1, 2, 3, null, 5 ], "float": 1.2345 };
$val = json_decode($input);
echo $val->abc."n";
Would produce:
12
As of version 1.0.5, json_decode takes an optional parameter, assoc (boolean), that returns an associative array instead of an object.
A PHP object correlates to a JavaScript object (associative array, i.e., key => value pairs), so the above would be referenced in JavaScript like so:
var obj = ...; /* retrieve JSON and eval() it, returning an object */
var result = obj["abc"] * obj["float"];
alert("result is " + result);
This should display an alert box with the value of result, i.e., 14.814.
Enhancements:
- A complete rewrite using JSON_checker as the base for the parser.
- Implements the JSON specification.
- Significant performance improvements on encoding.
- Re-licensed under the PHP license.