Free hearhere enables users software for linux

EtherEye is a web-based network host checking system written in PHP and standards compliant HTML.
You simply provide it with a list of IP addresses or domain names via the configuration interface and it will ping them on request and output the results as HTML.
You can also access the results via RSS feed for easier monitoring or to integrate into a website.
Installation:
To configure EtherEye, simply point your browser at the config.php file included with EtherEye. If it doesnt work or you get an error, PHP probably isnt properly configured on your server.
Language
Select your desired language here. This setting affects the language of the configuration interface as well as the results interface. Please read the README for instructions on how to translate EtherEye into your language if your language is not available.
Does the server run Windows?
If the server runs Windows, select "Yes", otherwise leave it on "No". If you set this to Yes, a few options will be filled in automatically, so you dont need to worry about them.
Which theme would you like to use?
Pretty self-explanatory really. The EtherEye interface will look different depending on which theme you select. Please see the README for instructions on how to write EtherEye themes.
Automatic refresh
If you enable automatic refreshing, the results page will be automatically re-loaded as frequently as specified by the option further down the page.
Ping command line option to specify the number of requests to send
If you selected the Windows server option you dont need to worry about this - it has been auto-filled. If not, the default should be OK for people running Linux. People running other UNIXes will need to check their ping man page.
Ping command line option to specify the ping timeout
The default value should be OK for everyone running Windows or Linux. Again, people running other UNIXes will need to check their ping man page.
Ping time-out
This value tells ping how long to wait for a response to ping requests. This value is in seconds if your server runs Linux or UNIX and milliseconds if your server runs Windows. The default value used by ping under Linux and UNIX is 3 seconds, Windows ping is 4000 milliseconds (4 seconds).
The lower this value, the less time EtherEye has to wait for ping to give up waiting for a response from a down machine, which makes the results get displayed quicker. However, bear in mind that if a machine is up but takes longer to respond than the time allowed by this value, EtherEye will report it as down! One second is probably a reasonable value for this setting.
Site name
This is simply a name used in a few places in the interface. It can be anything you want.
How often to refresh
If you enabled automatic refreshing above, you need to set this to how often you would like the results page to be automatically refreshed in seconds. The default, 300 seconds, is 5 minutes. If you didnt enable automatic refreshing above, you dont need to worry about this option.
How long to cache results for?
Each time EtherEye pings the hosts it saves the state of each host in the hosts file. This option determines how long these saved states are used for before EtherEye re-pings the hosts. If EtherEye has cached results available which have not expired, it will display them immediately without re-checking the hosts. This can be useful if you access EtherEye a lot (many times a minute) and dont need EtherEye to check the hosts that frequently. Most people will probably want to set this to 0 to disable caching completely.
Number of machines you want to watch
You need to specify here how many machines you want EtherEye to monitor. This is used to decide how many input boxes to give you on the next page.
If all is well, click on the button to save the options youve entered and move to the next page of the installation. If EtherEye is giving an error and not displaying the button, you need to check the permissions on the directory EtherEye is running from - you need to enable write access for all users (you can change it back later).
Entering the hosts
On this page, you need to enter the hosts you wish to monitor. Enter the IP address or domain name in the first box of each line, then a name for the machine in the second box (this can be anything you want) and finally select the machine type - this wont affect how EtherEye works, it is simply used to select an icon to display for the machine in the results.
Finishing the configuration
Once you have completed the installation, you may wish to change the permissions on the directory EtherEye is installed into so that every user cannot write to it (you cant be too careful).
Next, you may wish to change the permissions on the hosts-list.xml and ethereye-conf.xml files to ensure they are not writable (you dont want other people playing with your configuration). However, note that if you make hosts-list.xml non-writable, caching will not work (if you enabled it) and no error will be given to tell you this.
You may also wish to delete config.php for proper security, but then you wont be able to reconfigure EtherEye using the interface later.
Using EtherEye
Once you have EtherEye configured, you can check the machines you have configured EtherEye with by accessing the index.php file. If you use an RSS aggregator, you may wish to add rss.php to it to keep track of your network status. You could also integrate your EtherEye scan results into your website using the rss.php feed.
Enhancements:
- This release incorporates fixes for users receiving outdated results due to caching in the browser or server and for some configuration values not being remembered when reconfiguring using the configuration interface.

Squid Users Manager is a web-enabled and intuitive user interface written upon Ruby on Rails web development framework that manager Squid Proxy NCSA auth users across MD5 digest files.
The project is Open Source and distributed under the terms of the GPL licence.
Enhancements:
- Application Web 2.0 compliant
- New design with css and light layout.
- Ajax enabled app.
- More intuitive and elegant application.

KNetworkManager is the KDE front end for NetworkManager. KNetworkManager project provides a sophisticated and intuitive user interface which enables users easily to switch their network environment.

The range of functions encompasses the features implemented by NetworkManager daemon. Up until now NetworkManager supports:

Wired Ethernet Devices (IEEE 802.3)
Wireless Ethernet Devices (IEEE 802.11): Unencrypted, WEP, WPA Personal, WPA Enterprise
Virtual Private Network (VPN): OpenVPN, VPNC
Dial-Up (PPP)

How does it work?

For both, Wireless LAN and Wired LAN, NetworkManager supports devices known to HAL. Unless working in offline mode, NetworkManager tries to keep the system connected at any time. For this, NetworkManager follows the following policy.

Once started, NetworkManager asks HAL about available network interfaces. If a wired network interface with a carrier is found, NetworkManager connects to this. Either by DHCP (default) or by setting up previously defined static configuration. Later on, when KNetworkManager starts up, NetworkManager will expose its information about network devices and wireless networks found by scanning to the applet.

At this point, if a user decides to unplug the wired connection, NetworkManager will not connect to an arbitrary wireless network. By default all available networks are untrusted. Only if a user decides to connect to a network manually once, this specific network n henceforth being marked as trusted.

n = { ESSID, Hardware address or addresses of the access point}

The trusted networks are stored individually for each user. KNetworkManager stores them and informs NetworkManager about the known, trusted networks. If a wired connection drops due to unplugging the cable NetworkManager will automatically connect to a trusted network. As this step was done without user interaction, NetworkManager will reconnect to the wired connection once it has a carrier.

If a user joins a wireless network by manual intervention (e.g. user clicks on a network listed in the context menu of KNetworkManager or connects to a hidden wireless network), NetworkManager will take down any previous connection. If one unplugs the wired connection after such a step, NetworkManager will not connect to the wired connection once it has a carrier.

Print OpenOffice 2 documents is a service menu that enables the user to right click on an OpenOffice 2 document and print it.

PwManager is a secure password manager.
With PwManager you can easily manage your passwords. PwManager saves your passwords blowfish-encrypted in one file, so you have to remember only one master-password instead of all. Instead of the master-password you can use a chipcard, so you dont have to remember a password to access the list.
Main features:
- Manage passwords the convenient way with the support of password categories, five information columns and an additional comment field.
- Locking mechanism to prevent strangers from looking at your passwords while you are away and not using PwManager.
- Deep-Locking mechanism to encrypt all security critical data, write it to disk and delete it in memory. This enables you to enjoy maximum security with almost no loss of useability.
- The integrated KWallet emulation enables all applications on your KDE Desktop to access the PwManager database in an easy, flexible and secure way.
- A fairly good seaching and sorting mechanism to find entries very fast.
- Chipcard (smartcard) interface. With the chipcard you can replace the "master-password" to easily access all your passwords with a "key-card".
- Printing support to easily print out a complete list of all your passwords.
- System-Tray (kicker) icon to enable the user to access PwManager very fast.
- GPasman and KPasman interface to import and export your data to and from these file formats.