policy daemon
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 1041
Policy Daemon 1.81
Policy Daemon is an anti-spam plugin for Postfix. more>>
Policy Daemon project is an anti-spam plugin for Postfix (written in C) that does Greylisting, Sender-(envelope, SASL or host / ip)-based throttling (on messages and/or volume per defined time unit), Recipient rate limiting, Spamtrap monitoring / blacklisting, HELO auto blacklisting and HELO randomization preventation.
Enhancements:
- Merged OSX -L < libdir > vs. -L< libdir > fix into v1.8x branch
- Added quirk for SIGPIPE on Apple
- Added quirk for some versions of NetBSD which dont have SO_NOSIGPIPE
- Added error message that if we cannot find how to handle SIGPIPE on the host platform to contact the devel mailing list
- Make "stats" command a bit better aligned
- Be paranoid bout our read buffer size check
- Better check to see if weve run out of available slots, if we have emit a warning and close connection
- Fixed potential buffer overflow when line length exceeds MAXLINE
<<lessEnhancements:
- Merged OSX -L < libdir > vs. -L< libdir > fix into v1.8x branch
- Added quirk for SIGPIPE on Apple
- Added quirk for some versions of NetBSD which dont have SO_NOSIGPIPE
- Added error message that if we cannot find how to handle SIGPIPE on the host platform to contact the devel mailing list
- Make "stats" command a bit better aligned
- Be paranoid bout our read buffer size check
- Better check to see if weve run out of available slots, if we have emit a warning and close connection
- Fixed potential buffer overflow when line length exceeds MAXLINE
Download (0.35MB)
Added: 2007-07-11 License: GPL (GNU General Public License) Price:
835 downloads
ACL Policy Daemon for Postfix 0.60
ACL Policy Daemon is a program that communicates with the Postfix MTA using the Policy Delegation Protocol implementing an ACL. more>>
ACL Policy Daemon is a program that communicates with the Postfix MTA using the Policy Delegation Protocol implementing an ACL (Access Control List) system, making very easy to improve and create nice controls on your e-mail traffic. You can use it to verify SPF records to.
The project is developed using Python and has no other dependencies and licensed by GPL version 2.
The rules are loaded from a regular text file. It is planned to load the rules from a SQL database or LDAP directory in the future.
Greylisting functionality will be implemented soon.
For news and updated information about ACL Policy Daemon, you can always check the project page at GNA: https://gna.org/projects/apolicy/
Installation:
You must have Python installed, version 2.3 or above. Run python to check:
miguel@debian:~$ python
Python 2.4.4c0 (#2, Jul 30 2006, 15:43:58)
[GCC 4.1.2 20060715 (prerelease) (Debian 4.1.1-9)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>
It is very easy to install apolicy. In some distributions, Postfixs daemons are located in /usr/libexec/postfix, check your distribution.
The following commands should do just fine, you must be root:
debian:~# tar zcf apolicy-0.3.tar.gz
debian:~# cp apolicy-0.3/src/apolicy.py /usr/lib/postfix/
debian:~# chmod 755 /usr/lib/postfix/apolicy.py
debian:~# mkdir /etc/apolicy/
debian:~# cp apolicy.conf /etc/apolicy/
debian:~# chmod 644 /etc/apolicy/apolicy.conf
debian:~# echo "apolicy unix - n n - - spawn" >> /etc/postfix/master.cf
debian:~# echo " user=nobody argv=/usr/lib/postfix/apolicy.py" >> /etc/postfix/master.cf
The apolicy.conf is a sample file with examples, you must edit it to fit your needs.
Install the complementary modules for apolicy. We will install 3 packages: apolicy, pyspf and pydns. Note that the directory that contains Python libraries is not the same on all operating systems. Sometimes it is inside /usr/lib or /usr/libexec, and may be named python or python< version >:
debian:~# mkdir /usr/lib/ /site-packages/apolicy
debian:~# mkdir /usr/lib/ /site-packages/spf
debian:~# mkdir /usr/lib/ /site-packages/DNS
debian:~# cp apolicy-0.3/src/apolicy/* /usr/lib/ /site-packages/apolicy
debian:~# cp apolicy-0.3/src/spf/* /usr/lib/ /site-packages/spf
debian:~# cp apolicy-0.3/src/DNS/* /usr/lib/ /site-packages/DNS
debian:~# echo apolicy > /usr/lib/ /site-packages/apolicy.pth
debian:~# echo spf > /usr/lib/ /site-packages/spf.pth
debian:~# echo DNS > /usr/lib/ /site-packages/DNS.pth
Before setting Postfix, it is wise to test apolicy and check if everything is right. The configuration file is loaded by default from /etc/apolicy/apolicy.conf, you can use -c parameter to change to point where your configuration file is. It is possible to debug your configuration using the parameter -d, it will send a lot of output to syslog mail facility:
debian:~# /usr/lib/postfix/apolicy.py -d
The program must keep running and waiting input from stdin. Take a look at mail.log for any problem. You can press ctrl+c to finish it. If no errors happened, then lets move forward.
Finally, add to your main.cf:
smtpd_recipient_restrictions =
reject_unlisted_recipient
...
reject_unauth_destination
check_policy_service unix:private/apolicy
For the size acl works, apolicy need to be called this way:
smtpd_end_of_data_restrictions = check_policy_service unix:private/apolicy
<<lessThe project is developed using Python and has no other dependencies and licensed by GPL version 2.
The rules are loaded from a regular text file. It is planned to load the rules from a SQL database or LDAP directory in the future.
Greylisting functionality will be implemented soon.
For news and updated information about ACL Policy Daemon, you can always check the project page at GNA: https://gna.org/projects/apolicy/
Installation:
You must have Python installed, version 2.3 or above. Run python to check:
miguel@debian:~$ python
Python 2.4.4c0 (#2, Jul 30 2006, 15:43:58)
[GCC 4.1.2 20060715 (prerelease) (Debian 4.1.1-9)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>>
It is very easy to install apolicy. In some distributions, Postfixs daemons are located in /usr/libexec/postfix, check your distribution.
The following commands should do just fine, you must be root:
debian:~# tar zcf apolicy-0.3.tar.gz
debian:~# cp apolicy-0.3/src/apolicy.py /usr/lib/postfix/
debian:~# chmod 755 /usr/lib/postfix/apolicy.py
debian:~# mkdir /etc/apolicy/
debian:~# cp apolicy.conf /etc/apolicy/
debian:~# chmod 644 /etc/apolicy/apolicy.conf
debian:~# echo "apolicy unix - n n - - spawn" >> /etc/postfix/master.cf
debian:~# echo " user=nobody argv=/usr/lib/postfix/apolicy.py" >> /etc/postfix/master.cf
The apolicy.conf is a sample file with examples, you must edit it to fit your needs.
Install the complementary modules for apolicy. We will install 3 packages: apolicy, pyspf and pydns. Note that the directory that contains Python libraries is not the same on all operating systems. Sometimes it is inside /usr/lib or /usr/libexec, and may be named python or python< version >:
debian:~# mkdir /usr/lib/ /site-packages/apolicy
debian:~# mkdir /usr/lib/ /site-packages/spf
debian:~# mkdir /usr/lib/ /site-packages/DNS
debian:~# cp apolicy-0.3/src/apolicy/* /usr/lib/ /site-packages/apolicy
debian:~# cp apolicy-0.3/src/spf/* /usr/lib/ /site-packages/spf
debian:~# cp apolicy-0.3/src/DNS/* /usr/lib/ /site-packages/DNS
debian:~# echo apolicy > /usr/lib/ /site-packages/apolicy.pth
debian:~# echo spf > /usr/lib/ /site-packages/spf.pth
debian:~# echo DNS > /usr/lib/ /site-packages/DNS.pth
Before setting Postfix, it is wise to test apolicy and check if everything is right. The configuration file is loaded by default from /etc/apolicy/apolicy.conf, you can use -c parameter to change to point where your configuration file is. It is possible to debug your configuration using the parameter -d, it will send a lot of output to syslog mail facility:
debian:~# /usr/lib/postfix/apolicy.py -d
The program must keep running and waiting input from stdin. Take a look at mail.log for any problem. You can press ctrl+c to finish it. If no errors happened, then lets move forward.
Finally, add to your main.cf:
smtpd_recipient_restrictions =
reject_unlisted_recipient
...
reject_unauth_destination
check_policy_service unix:private/apolicy
For the size acl works, apolicy need to be called this way:
smtpd_end_of_data_restrictions = check_policy_service unix:private/apolicy
Download (0.034MB)
Added: 2006-12-27 License: GPL (GNU General Public License) Price:
1032 downloads
LDAP Mailing Lists Access Policy Daemon 0.2
LDAP Mailing Lists Access Policy Daemon (MLAPD) is a mailing list manager that uses LDAP to control list access. more>>
LDAP Mailing Lists Access Policy Daemon (MLAPD) is a mailing list manager that uses LDAP (instead of BDB or GDBM) to control list access. Its designed to work in conjunction with Postfix as an access policy delegation daemon. It manages electronic mail discussion and e-newsletter lists. Its goal is to store/read list data on/from LDAP.
It works as a Postfix access policy delegation agent, so it can be installed one time and used by multiple Postfix instances, or installed multiple times and not suffer database access concurrency issues (because it uses LDAP).
Enhancements:
- This can be considered the first stable and usable release.
<<lessIt works as a Postfix access policy delegation agent, so it can be installed one time and used by multiple Postfix instances, or installed multiple times and not suffer database access concurrency issues (because it uses LDAP).
Enhancements:
- This can be considered the first stable and usable release.
Download (0.040MB)
Added: 2007-03-24 License: GPL (GNU General Public License) Price:
944 downloads
Python Music Daemon 0.3
Python Music Daemon is yet another jukebox written in Python. more>>
PyMusicD is yet another jukebox daemon written in python. It was born out of my frustration with the current mp3 jukeboxes, mostly the lack of features that I want. Ive also been playing with python quite a lot lately, and this is my first attempt at a large project in python.
The player is being written to satisfy my own requirements for a car mp3 player, although theres no reason you couldnt use this for a home mp3 player, or work mp3 player.
It assumes that your network users are (mostly) benign, and doesnt take a lot of precautions against malicious users who want to screw with your mp3s. Take appropriate measures to only allow trusted users to play with it, at least until I secure it a bit better.
Its primary purpose is to run in the background, and play mp3s whenever they are in the playlist.
Usage
Unpack this to its own directory. Edit the pymusicd.conf file to your liking. Run python PyMusicD, then run python pymusic to play around with it. The client operates very similarly to most shells, and includes tab completion for commands (but not arguments... yet.)
If you wish to install this to the system, you may do so by running python setup.py install. This will install the server binary in the default place for your platform (according to distutils.) You may then edit the config file (/etc/pymusicd.conf by default) and run the server by running PyMusicD. The cli client will be named pymusic.
This software is currently in development. It is not ready for end users yet. You should have familiarity with scripting in python before you set about to use this software. That being said, if you find bugs that arent listed in TODO, and/or have problems with the software that arent listed in TODO, email me (zwhite@darkstar.frop.org) and Ill see what I can do to help you. Code patches/suggestions are always welcome.
This is known to work on my Slackware 9.0 machine using the Python 2.2.2 package that came with it. I have also tested it on my Mac OSX 10.2.8 machine with Python 2.2. I have no reason to believe that it wont work on any machine with a Python 2.x interpreter and
either mpg123 or mpg321. Your mileage may vary. If it doesnt work on your platform, please let me know. My goal is to have this work on any platform that python runs on.
Enhancements:
- Fixed a bug when adding an entire directory with %2A instead of *
- Added a debug command to get server state, currently only playstatus is reported, will add more as needed.
- Changed the way the stop command works to eliminate a bug.
- Check to make sure a file exists before we add it to the playlist.
- We no longer start playing music as soon as the playlist has entries.
- Instead, we wait for a play command to be issued.
- Added config file support. Defaults to /etc/pymusicd.conf or ./pymusicd.conf
- Added a setup.py and setup.cfg file. Now users can install PyMusicD using the standard "python setup.py install" method that other scripts and modules use.
<<lessThe player is being written to satisfy my own requirements for a car mp3 player, although theres no reason you couldnt use this for a home mp3 player, or work mp3 player.
It assumes that your network users are (mostly) benign, and doesnt take a lot of precautions against malicious users who want to screw with your mp3s. Take appropriate measures to only allow trusted users to play with it, at least until I secure it a bit better.
Its primary purpose is to run in the background, and play mp3s whenever they are in the playlist.
Usage
Unpack this to its own directory. Edit the pymusicd.conf file to your liking. Run python PyMusicD, then run python pymusic to play around with it. The client operates very similarly to most shells, and includes tab completion for commands (but not arguments... yet.)
If you wish to install this to the system, you may do so by running python setup.py install. This will install the server binary in the default place for your platform (according to distutils.) You may then edit the config file (/etc/pymusicd.conf by default) and run the server by running PyMusicD. The cli client will be named pymusic.
This software is currently in development. It is not ready for end users yet. You should have familiarity with scripting in python before you set about to use this software. That being said, if you find bugs that arent listed in TODO, and/or have problems with the software that arent listed in TODO, email me (zwhite@darkstar.frop.org) and Ill see what I can do to help you. Code patches/suggestions are always welcome.
This is known to work on my Slackware 9.0 machine using the Python 2.2.2 package that came with it. I have also tested it on my Mac OSX 10.2.8 machine with Python 2.2. I have no reason to believe that it wont work on any machine with a Python 2.x interpreter and
either mpg123 or mpg321. Your mileage may vary. If it doesnt work on your platform, please let me know. My goal is to have this work on any platform that python runs on.
Enhancements:
- Fixed a bug when adding an entire directory with %2A instead of *
- Added a debug command to get server state, currently only playstatus is reported, will add more as needed.
- Changed the way the stop command works to eliminate a bug.
- Check to make sure a file exists before we add it to the playlist.
- We no longer start playing music as soon as the playlist has entries.
- Instead, we wait for a play command to be issued.
- Added config file support. Defaults to /etc/pymusicd.conf or ./pymusicd.conf
- Added a setup.py and setup.cfg file. Now users can install PyMusicD using the standard "python setup.py install" method that other scripts and modules use.
Download (0.013MB)
Added: 2005-05-10 License: Freely Distributable Price:
1629 downloads
OLSR daemon 0.4.10
OLSR daemon project is an implementation of the Optimized Link State Routing protocol for mobile ad-hoc networks (MANETs). more>>
OLSR daemon project is an implementation of the Optimized Link State Routing protocol for mobile ad-hoc networks (MANETs).
OLSR is a routing protocol for mobile ad-hoc networks. The protocol is pro-active, table driven and utilizes a technique called multipoint relaying for message flooding. olsrd also implements a popular optional link quality extension. Currently the implementation compiles on GNU/Linux, Windows, OS X, FreeBSD and NetBSD systems.
Olsrd is ment to be a well structured and well coded implementation that should be easy to maintain, expand and port to other platforms. The implementation is RFC3626 compliant with respect to both core and auxiliary functioning.
Olsrd supports use of loadable plugins. These can be used to to handle and generate custom packettypes to be carried by OLSRs MPR flooding scheme or for any other desired functioning.
Enhancements:
- Network simulator (olsr_switch) added. Read more in the README file included in the release.
- New experimental fish eye link distribution algorithm. Read more in the README file included in the release.
- Tiny Application Server(TAS) plugin added
- Plugin interface changes. Olsrd now exports all symbols mening that plugins can access all olsrd functions easily.
- Olsrd now builds and runs on OpenBSD
- Build system rewrites(OS detection is now done automagically)
- Lots of bugfixes and minor changes
<<lessOLSR is a routing protocol for mobile ad-hoc networks. The protocol is pro-active, table driven and utilizes a technique called multipoint relaying for message flooding. olsrd also implements a popular optional link quality extension. Currently the implementation compiles on GNU/Linux, Windows, OS X, FreeBSD and NetBSD systems.
Olsrd is ment to be a well structured and well coded implementation that should be easy to maintain, expand and port to other platforms. The implementation is RFC3626 compliant with respect to both core and auxiliary functioning.
Olsrd supports use of loadable plugins. These can be used to to handle and generate custom packettypes to be carried by OLSRs MPR flooding scheme or for any other desired functioning.
Enhancements:
- Network simulator (olsr_switch) added. Read more in the README file included in the release.
- New experimental fish eye link distribution algorithm. Read more in the README file included in the release.
- Tiny Application Server(TAS) plugin added
- Plugin interface changes. Olsrd now exports all symbols mening that plugins can access all olsrd functions easily.
- Olsrd now builds and runs on OpenBSD
- Build system rewrites(OS detection is now done automagically)
- Lots of bugfixes and minor changes
Download (0.21MB)
Added: 2006-01-05 License: BSD License Price:
1391 downloads
Music daemon 0.0.4
Music daemon(musicd) is a music playing server that supports multiple formats through plugins and multiple playlists. more>>
Music daemon(musicd) is a music playing server that supports multiple formats through plugins and multiple playlists. Musicd supports plugins to enable playing of different audioformats. The plugin-api is quite similiar to one that the popular XMMS uses. Currently XMMS-plugins are not directly supported, but if I find the time, Ill make a meta-plugin to support them.
The first reason to make the player a server is to make it possible to use many different frontends and even at the same time. You can use a GUI if you like them, but anything it can do, can be done from commandline too.
The second reason is to make sure that the GUI or X does not crash the whole player. I have found that many software with a GUI tend to crash. With musicd the player is unaffected by this and you can start the interface again.
Main features:
- Musicd has its own simple text-based protocol for player-frontend communication.
- Support for unlimited number of playlists, songs per playlist and frontends connect at the same time
- Support for both IPv4 and IPv6. Also UNIX-sockets are supported for local connections.
- Currently supported audioformats: mp3 (ffmpeg), ogg vorbis (vorbisfile) and mods (libmikmod).
- Support for OSS and Solaris ouput.
- Musicd has been tested on x86 Linux and Solaris 9.
Enhancements:
- Calling play while already playing shouldnt cause deadlocks anymore
- Load command on a file that has too long line as the last line locked up the daemon, this shouldnt happen anymore
- Invalid id3tags shouldnt give random data anymore
- Invalid filenames shouldnt crash the player anymore
<<lessThe first reason to make the player a server is to make it possible to use many different frontends and even at the same time. You can use a GUI if you like them, but anything it can do, can be done from commandline too.
The second reason is to make sure that the GUI or X does not crash the whole player. I have found that many software with a GUI tend to crash. With musicd the player is unaffected by this and you can start the interface again.
Main features:
- Musicd has its own simple text-based protocol for player-frontend communication.
- Support for unlimited number of playlists, songs per playlist and frontends connect at the same time
- Support for both IPv4 and IPv6. Also UNIX-sockets are supported for local connections.
- Currently supported audioformats: mp3 (ffmpeg), ogg vorbis (vorbisfile) and mods (libmikmod).
- Support for OSS and Solaris ouput.
- Musicd has been tested on x86 Linux and Solaris 9.
Enhancements:
- Calling play while already playing shouldnt cause deadlocks anymore
- Load command on a file that has too long line as the last line locked up the daemon, this shouldnt happen anymore
- Invalid id3tags shouldnt give random data anymore
- Invalid filenames shouldnt crash the player anymore
Download (0.18MB)
Added: 2006-08-04 License: GPL (GNU General Public License) Price:
1179 downloads
PXE daemon 1.4.2
The PXE daemon allows network managers to boot PXE-enabled machines over the network. more>>
The PXE daemon allows network managers to boot PXE-enabled machines over the network. Basically it envolves BOOTP, TFTP (so far so good) and a PXE daemon. This is where all the trouble starts. There is only one implementation arround, and if doesnt work on anything other than little endian machines.
I originally tried to correct some of the major problems in this code. However firstly, I could not find anyone with at Red Hat or Intel to deal with and secondly, Intel seem very unintrested in porting the code the big endian machines. The source is also very messy and it would have taken longer to correct the original code, than to re-write the whole daemon. If you dont believe me on this point, just have a look at it, IMHO any daemon that responds to keyboard input is a bad thing (it thinks it had packets coming from the keyboard even when in daemon mode)
You are lucky then, but a lot of places have already got a bootserver, and most likely it will be a UNIX based machine that is not x86. So, why put in another machine when there is already one there?
If you know enough about PC, you will know there are several operating modes. The mode the PC boots in is only able to access the low 640KB of memory. By using the PXELINUX bootstrap code it is possible to boot using the full amount to memory in the system. The means you can do some nice things including boot a Linux kernel + Ramdisk over the network, as you would for a Sun. Please note that the Intel bootstraping code is very limited in this sense.
I dont recommend it anymore, I just havent had time to do a lot of updates, PXELINUX is far far better (see link below). However Intels PXE daemon is naff (IMHO)
Enhancements:
- Increase the interface buffer to hold more than three interfaces
- Fixed a segfault in when multicast was disabled
- Fixed null pointer dereference when looking at interfaces with no IP address
<<lessI originally tried to correct some of the major problems in this code. However firstly, I could not find anyone with at Red Hat or Intel to deal with and secondly, Intel seem very unintrested in porting the code the big endian machines. The source is also very messy and it would have taken longer to correct the original code, than to re-write the whole daemon. If you dont believe me on this point, just have a look at it, IMHO any daemon that responds to keyboard input is a bad thing (it thinks it had packets coming from the keyboard even when in daemon mode)
You are lucky then, but a lot of places have already got a bootserver, and most likely it will be a UNIX based machine that is not x86. So, why put in another machine when there is already one there?
If you know enough about PC, you will know there are several operating modes. The mode the PC boots in is only able to access the low 640KB of memory. By using the PXELINUX bootstrap code it is possible to boot using the full amount to memory in the system. The means you can do some nice things including boot a Linux kernel + Ramdisk over the network, as you would for a Sun. Please note that the Intel bootstraping code is very limited in this sense.
I dont recommend it anymore, I just havent had time to do a lot of updates, PXELINUX is far far better (see link below). However Intels PXE daemon is naff (IMHO)
Enhancements:
- Increase the interface buffer to hold more than three interfaces
- Fixed a segfault in when multicast was disabled
- Fixed null pointer dereference when looking at interfaces with no IP address
Download (0.055MB)
Added: 2006-07-04 License: GPL (GNU General Public License) Price:
1214 downloads
ped daemon 0.1.5
ped is a process execution daemon, comparable to cron in its basic functionality. more>>
ped is a process execution daemon, comparable to cron in its basic functionality. ped daemon monitors a given directory.
If a user or an application drops a file into this directory, ped parses the content and executes a given command.
The syntax of these files describes the functionality: "[from (unixtimestamp)] [until (unixtimestamp)] [asuser (username)] start|restart|loop (command) [(parameter)]".
ped was primary written to schedule time-consuming tasks initiated by a Web application.
< u >Following keywords are valid for config/start-files:< /u >
from < unixtimestamp >
Defines the start of validity of this file.
Optional.
If this keyword is missing, start time is not checked.
until < unixtimestamp >
Defines the end of validity of this file.
Optional.
If this keyword is missing, end time is not checked.
If the < unixtimestamp > of "until" is less than a given < unixtimestamp >
of "from", the whole file is valid, but no action will take place.
asuser < username >
< username > is the name of a systemuser (do NOT use an UID here).
Optional.
If this keyword is missing, the given user not valid or has no rights
to access a valid shell, the process will start as the same user, ped
runs under (in most cases: root).
start < command > < options >
Starts < command > once in between the duration of validity. If there
is no "from" statement, starting time is seconds after the file has
been dropped in.
After attempting to start < command > the config/start-file is deleted;
nevertheless if < command > is executable or not.
restart < command > < options >
Restarts < command > in between the duration of validity (with the
built-in delay).
If the formerly started process didnt exit, it will be killed, and
a new process will spawn.
After the end of validity, this config/start-file is deleted.
loop < command > < options >
Like "restart", "loop" tries to execute < command > every (built-in
delay) seconds.
If the formerly started process didnt exit, no action will take
place, unless the formerly started process stops; if this happens,
a new instance of < command > is started.
After the end of validity, this config/start-file is deleted.
Enhancements:
- This release features better support for GNU autotools.
- Static definitions have been moved to configurable options.
- Man pages and an init script example have been added.
- A memory allocation bug was fixed.
<<lessIf a user or an application drops a file into this directory, ped parses the content and executes a given command.
The syntax of these files describes the functionality: "[from (unixtimestamp)] [until (unixtimestamp)] [asuser (username)] start|restart|loop (command) [(parameter)]".
ped was primary written to schedule time-consuming tasks initiated by a Web application.
< u >Following keywords are valid for config/start-files:< /u >
from < unixtimestamp >
Defines the start of validity of this file.
Optional.
If this keyword is missing, start time is not checked.
until < unixtimestamp >
Defines the end of validity of this file.
Optional.
If this keyword is missing, end time is not checked.
If the < unixtimestamp > of "until" is less than a given < unixtimestamp >
of "from", the whole file is valid, but no action will take place.
asuser < username >
< username > is the name of a systemuser (do NOT use an UID here).
Optional.
If this keyword is missing, the given user not valid or has no rights
to access a valid shell, the process will start as the same user, ped
runs under (in most cases: root).
start < command > < options >
Starts < command > once in between the duration of validity. If there
is no "from" statement, starting time is seconds after the file has
been dropped in.
After attempting to start < command > the config/start-file is deleted;
nevertheless if < command > is executable or not.
restart < command > < options >
Restarts < command > in between the duration of validity (with the
built-in delay).
If the formerly started process didnt exit, it will be killed, and
a new process will spawn.
After the end of validity, this config/start-file is deleted.
loop < command > < options >
Like "restart", "loop" tries to execute < command > every (built-in
delay) seconds.
If the formerly started process didnt exit, no action will take
place, unless the formerly started process stops; if this happens,
a new instance of < command > is started.
After the end of validity, this config/start-file is deleted.
Enhancements:
- This release features better support for GNU autotools.
- Static definitions have been moved to configurable options.
- Man pages and an init script example have been added.
- A memory allocation bug was fixed.
Download (0.15MB)
Added: 2006-07-04 License: GPL (GNU General Public License) Price:
1207 downloads
Gizmo Daemon 3.3
Gizmo Daemon is the Linux Input Device Utility. more>>
Gizmo Daemon is the Linux Input Device Utility.
Ever want to make use of those keyboard keys and mouse buttons that X wont let you use? Ever want to quickly define a keyboard shortcut to do something like change or mute the volume? Ever want to use your joystick, second mouse, Griffin PowerMate, or any other random device you can think of to do fun things like control applications, switch desktops, switch tracks in XMMS / BMP, launch programs, or do pretty much anything else you can think of?
Are you a MythTV user? Got an RF or IR (LIRC) Remote? Annoyed with how frustrating it is to map keys, or is the remote super touchy? Would you like a simple easy way to configure your remote, and have it function properly at the same time? Want to have different key maps based on what application is currently being used?
Gizmo Daemon does all of that, and more! Gizmo Daemon operates on a fairly simple philosophy: let the user decide. Any and all device events are sent to the configuration scripts, and from there the user can decide what should be done with those events. A number of functions are exposed to the scripts which allows the script to interact with any of the loaded device plugins in any way desired.
Main features:
- Control any application with any device
- Utilize those special keys on your fancy keyboard, even if your X server or terminal doesnt support them! Now you can actually make the volume controls change the volume, or the media buttons control XMMS / BMP! Set the buttons to launch your favorite programs, switch virtual desktops, or run whatever application you want!
- Give per application key mappings, very handy for remote users!
- Fix touchy remotes by removing quick duplicate keystrokes
- Control system mixer volume
- Change virtual desktops (only for EWMH capable window managers)
- Launch programs
- Send keyboard and mouse events to applications
- Send device events from one device to another, or create fake device events (control a mouse cursor with a joystick, or keyboard)
- Visualization of system events such as CPU USage, and XMMS / BMP sound output on visual devices (such as the LED on the Griffin PowerMate USB Dial).
- Fancy on screen displays via XOSD. Now your workstation or MythTV box can have nice TV friendly volume displays controlled by your remote!
- And more! Anything you can think of is probably possible
Enhancements:
- Add Powermate setRotateSensitivity function
- New variable in GizmoDeviceStrings.py called
POWERMATE_ROTATE_SENSITIVITY for this!
- Add PowermateEvent ClickTime property (duration of button press)
- Add GizmodThread class for creating threads from Python
- DO NOT USE!! (HIGHLY EXPERIMENTAL!)
- Add GizmodTimer class for creating timer objects from Python
- Add script 200-Powermate-ButtonTimeout for generating button
timeout events
- New variable in GizmoDeviceStrings.py called
POWERMATE_BUTTON_TIMEOUT for this!
- Add script 201-Powermate-Beryl
- So far this detects a powermate button timeout and
unfolds the beryl cube, and lets you scroll the unfolded
cube with the dial
- Add base script GizmoScriptAltTabber so that devices have an
easy way of sending Alt-Tab events
- New variable in GizmoDeviceStrings.py called
ALT_TAB_TIMEOUT for this!
- Add remote ?00-Intercept scripts for alt-tabbing support
- This allows the default mapping to start alt-tab
and to still alt-tab passed applications (if alt-tab
actually focuses apps) if those apps happen to use
the same button that initialized the alt-tab
- Add Gizmod namespace to libGizmod
<<lessEver want to make use of those keyboard keys and mouse buttons that X wont let you use? Ever want to quickly define a keyboard shortcut to do something like change or mute the volume? Ever want to use your joystick, second mouse, Griffin PowerMate, or any other random device you can think of to do fun things like control applications, switch desktops, switch tracks in XMMS / BMP, launch programs, or do pretty much anything else you can think of?
Are you a MythTV user? Got an RF or IR (LIRC) Remote? Annoyed with how frustrating it is to map keys, or is the remote super touchy? Would you like a simple easy way to configure your remote, and have it function properly at the same time? Want to have different key maps based on what application is currently being used?
Gizmo Daemon does all of that, and more! Gizmo Daemon operates on a fairly simple philosophy: let the user decide. Any and all device events are sent to the configuration scripts, and from there the user can decide what should be done with those events. A number of functions are exposed to the scripts which allows the script to interact with any of the loaded device plugins in any way desired.
Main features:
- Control any application with any device
- Utilize those special keys on your fancy keyboard, even if your X server or terminal doesnt support them! Now you can actually make the volume controls change the volume, or the media buttons control XMMS / BMP! Set the buttons to launch your favorite programs, switch virtual desktops, or run whatever application you want!
- Give per application key mappings, very handy for remote users!
- Fix touchy remotes by removing quick duplicate keystrokes
- Control system mixer volume
- Change virtual desktops (only for EWMH capable window managers)
- Launch programs
- Send keyboard and mouse events to applications
- Send device events from one device to another, or create fake device events (control a mouse cursor with a joystick, or keyboard)
- Visualization of system events such as CPU USage, and XMMS / BMP sound output on visual devices (such as the LED on the Griffin PowerMate USB Dial).
- Fancy on screen displays via XOSD. Now your workstation or MythTV box can have nice TV friendly volume displays controlled by your remote!
- And more! Anything you can think of is probably possible
Enhancements:
- Add Powermate setRotateSensitivity function
- New variable in GizmoDeviceStrings.py called
POWERMATE_ROTATE_SENSITIVITY for this!
- Add PowermateEvent ClickTime property (duration of button press)
- Add GizmodThread class for creating threads from Python
- DO NOT USE!! (HIGHLY EXPERIMENTAL!)
- Add GizmodTimer class for creating timer objects from Python
- Add script 200-Powermate-ButtonTimeout for generating button
timeout events
- New variable in GizmoDeviceStrings.py called
POWERMATE_BUTTON_TIMEOUT for this!
- Add script 201-Powermate-Beryl
- So far this detects a powermate button timeout and
unfolds the beryl cube, and lets you scroll the unfolded
cube with the dial
- Add base script GizmoScriptAltTabber so that devices have an
easy way of sending Alt-Tab events
- New variable in GizmoDeviceStrings.py called
ALT_TAB_TIMEOUT for this!
- Add remote ?00-Intercept scripts for alt-tabbing support
- This allows the default mapping to start alt-tab
and to still alt-tab passed applications (if alt-tab
actually focuses apps) if those apps happen to use
the same button that initialized the alt-tab
- Add Gizmod namespace to libGizmod
Download (0.99MB)
Added: 2007-06-28 License: The Apache License 2.0 Price:
851 downloads
CPQ Array Daemon 1.2
CPQ Array Daemon project keeps on monitoring your controller and checks for abnormal conditions. more>>
CPQ Array Daemon project keeps on monitoring your controller and checks for abnormal conditions. By default is only reports to the syslogs, but you can make it send SNMP Traps to selected hosts.
This tool can run on a linux based intel box with a smart array controller from Compaq. It reports status changes in the disks both to the syslog and to a snmp trap host.
The default is to only log to the syslog. You can specify traphosts with the -t parameter at the commandline. Multiple traphosts are allowed. It checks for valid input, but any errors are non-fatal, in fact the traphost is just ignored..
To ensure correct opereration compile it for the same kernel that runs on the machine where you want to use this. At least make sure that the version of the SmartArray driver is the same. Strange things can happen otherwise.
Installation:
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
<<lessThis tool can run on a linux based intel box with a smart array controller from Compaq. It reports status changes in the disks both to the syslog and to a snmp trap host.
The default is to only log to the syslog. You can specify traphosts with the -t parameter at the commandline. Multiple traphosts are allowed. It checks for valid input, but any errors are non-fatal, in fact the traphost is just ignored..
To ensure correct opereration compile it for the same kernel that runs on the machine where you want to use this. At least make sure that the version of the SmartArray driver is the same. Strange things can happen otherwise.
Installation:
The simplest way to compile this package is:
1. `cd to the directory containing the packages source code and type `./configure to configure the package for your system. If youre using `csh on an old version of System V, you might need to type `sh ./configure instead to prevent `csh from trying to execute `configure itself.
Running `configure takes awhile. While running, it prints some messages telling which features it is checking for.
2. Type `make to compile the package.
3. Optionally, type `make check to run any self-tests that come with the package.
4. Type `make install to install the programs and any data files and documentation.
5. You can remove the program binaries and object files from the source code directory by typing `make clean. To also remove the files that `configure created (so you can compile the package for a different kind of computer), type `make distclean. There is also a `make maintainer-clean target, but that is intended mainly for the packages developers. If you use it, you may have to get all sorts of other programs in order to regenerate files that came with the distribution.
Download (0.092MB)
Added: 2007-06-26 License: GPL (GNU General Public License) Price:
851 downloads
LIRC Client Daemon 0.9.1
LIRC Client Daemon project is an attempt to solve certain problems in LIRC. more>>
LIRC Client Daemon project is an attempt to solve certain problems in LIRC.
The LIRC Client Daemon is a per-user daemon that sits between the LIRC daemon (from the Linux InfraRed Control project) and any other programs that use LIRC.
It ships with a replacement library for LIRCs liblirc_client, which connects to lirccd instead of lircd. This primarily helps solve the synchronization present in the standard liblirc_client, and also empowers the user with a much more flexible configuration file format.
<<lessThe LIRC Client Daemon is a per-user daemon that sits between the LIRC daemon (from the Linux InfraRed Control project) and any other programs that use LIRC.
It ships with a replacement library for LIRCs liblirc_client, which connects to lirccd instead of lircd. This primarily helps solve the synchronization present in the standard liblirc_client, and also empowers the user with a much more flexible configuration file format.
Download (0.23MB)
Added: 2007-01-18 License: GPL (GNU General Public License) Price:
1015 downloads
Audio Daemon 0.99
Audio Daemon is a perl module to daemonize various players and support a single UDP interace for different players. more>>
Audio Daemon is a perl module to daemonize various players and support a single UDP interace for different players. Currently you can set up a server for MPG123, Xmms and an icecast stream (using libshout).
Audio::Daemon is made of two parts, the client and server.
The Client (Audio::Daemon::Client) remains the same across the board no matter what server you are communicating with, with a few exceptions noted in the pods.
The Server currently can be configured to be MPG123, Xmms or an Icecast (libshout) stream. Neither the Client nor the Servers need to be run as root and I strongly advise against it.
Audio::Daemon::MPG132:
Requires Audio::Play::MPG123 an optionally Audio::Mixer for volume control. It automatically spawns mpg123 in the background so there is no need to prestart it.
Audio::Daemon::Xmms:
Requires the Xmms and MP3::Info perl module and xmms installed. Id suggest getting the latest version of the Xmms perl module. It uses the volume and random feature built into xmms and if it doesnt find an xmms running it will try to spawn its own copy. Bear in mind that
xmms MUST HAVE an X display to export to, and that xmms must be running as the same user Audio::Daemon::Xmms is.
Audio::Daemon::Shout:
This wasnt easy to do. It requires MP3::Info and libshout to be installed (http://developer.icecast.org/libshout/) as well as a functioning icecast server. The timing here is pretty critical so I recomend being careful not to be polling the server too much. Be sure to read the icecast docs as Im still confused on how I got this part to work.
<<lessAudio::Daemon is made of two parts, the client and server.
The Client (Audio::Daemon::Client) remains the same across the board no matter what server you are communicating with, with a few exceptions noted in the pods.
The Server currently can be configured to be MPG123, Xmms or an Icecast (libshout) stream. Neither the Client nor the Servers need to be run as root and I strongly advise against it.
Audio::Daemon::MPG132:
Requires Audio::Play::MPG123 an optionally Audio::Mixer for volume control. It automatically spawns mpg123 in the background so there is no need to prestart it.
Audio::Daemon::Xmms:
Requires the Xmms and MP3::Info perl module and xmms installed. Id suggest getting the latest version of the Xmms perl module. It uses the volume and random feature built into xmms and if it doesnt find an xmms running it will try to spawn its own copy. Bear in mind that
xmms MUST HAVE an X display to export to, and that xmms must be running as the same user Audio::Daemon::Xmms is.
Audio::Daemon::Shout:
This wasnt easy to do. It requires MP3::Info and libshout to be installed (http://developer.icecast.org/libshout/) as well as a functioning icecast server. The timing here is pretty critical so I recomend being careful not to be polling the server too much. Be sure to read the icecast docs as Im still confused on how I got this part to work.
Download (0.015MB)
Added: 2006-08-03 License: GPL (GNU General Public License) Price:
1178 downloads
Net-Policy 2.2
The Net-Policy project allows system administrators to configure and manage their entire network at once. more>>
The Net-Policy project allows system administrators to configure and manage their entire network at once. It is initially designed to configure firewall and IPsec connections across an entire network.
Net-policy contains the following components:
net-policy:
This is the core network manager. It is a generic SNMP-based manager and is capable of managing any information configurable via SNMP. It is currently web based with a few more interfaces (Tk, CLI, ...) planned or partially implemented. Its SNMP engine is based on the OpenSNMP and Net-SNMP toolkits. It runs on top of a PostgreSQL database.
After checking out the SVN source code or downloading the tar ball for the net-policy project, run ./np-install as root to help guide you through a complete installation using our graphical installer.
Configurable optional pieces
The net-policy manager is capable of managing the following modules. The management system above is already capable of managing
np-cerberus: A IPsec implementation for linux based on the 2.4 kernel. This code is derived from NISTs IPsec reference project. We ported the code to the 2.4 kernel and added some IPtables specific pieces and re-released it here (with their permission).
np-plutoplus: A IKE implementation which runs on top of np-cerberus. This is code is derived from NISTs IKE reference project. It has been instrumented with SNMP support using the Net-SNMP toolkit.
<<lessNet-policy contains the following components:
net-policy:
This is the core network manager. It is a generic SNMP-based manager and is capable of managing any information configurable via SNMP. It is currently web based with a few more interfaces (Tk, CLI, ...) planned or partially implemented. Its SNMP engine is based on the OpenSNMP and Net-SNMP toolkits. It runs on top of a PostgreSQL database.
After checking out the SVN source code or downloading the tar ball for the net-policy project, run ./np-install as root to help guide you through a complete installation using our graphical installer.
Configurable optional pieces
The net-policy manager is capable of managing the following modules. The management system above is already capable of managing
np-cerberus: A IPsec implementation for linux based on the 2.4 kernel. This code is derived from NISTs IPsec reference project. We ported the code to the 2.4 kernel and added some IPtables specific pieces and re-released it here (with their permission).
np-plutoplus: A IKE implementation which runs on top of np-cerberus. This is code is derived from NISTs IKE reference project. It has been instrumented with SNMP support using the Net-SNMP toolkit.
Download (0.63MB)
Added: 2006-07-04 License: GPL (GNU General Public License) Price:
1208 downloads
audit daemon 1.5.6
audit package contains the user-space utilities for creating audit rules. more>>
audit package contains the user-space utilities for creating audit rules. As well as for storing and searching the audit records generate by the audit subsystem in the Linux 2.6 kernel.
Usage:
Examples usage of utilities:
General:
Window 1:
./auditd
Window 2 (you dont have to have the daemon running to try this, but
enabled has to be 1):
./auditctl -s
./auditctl -a entry,always -S open
ls
./auditctl -d entry,always -S open
Identity tracking:
./auditctl -a exit,always -S all -F loginuid=2000
./auditctl -L 2000,"test uid"
Enhancements:
- Updates were made to system-config-audit. auditctl was updated to better handle watching of directories with older kernels.
- Memory leaks and an invalid free in auditd were fixed along with interpretations in auparse.
<<lessUsage:
Examples usage of utilities:
General:
Window 1:
./auditd
Window 2 (you dont have to have the daemon running to try this, but
enabled has to be 1):
./auditctl -s
./auditctl -a entry,always -S open
ls
./auditctl -d entry,always -S open
Identity tracking:
./auditctl -a exit,always -S all -F loginuid=2000
./auditctl -L 2000,"test uid"
Enhancements:
- Updates were made to system-config-audit. auditctl was updated to better handle watching of directories with older kernels.
- Memory leaks and an invalid free in auditd were fixed along with interpretations in auparse.
Download (0.29MB)
Added: 2007-07-26 License: GPL (GNU General Public License) Price:
824 downloads
PowerDNS daemon 2.9.21
PowerDNS daemon is an advanced high performance authoritative nameserver. more>>
PowerDNS daemon Nameserver is a advanced, modern and high performance authoritative-only nameserver.
It is written from scratch and conforms to all relevant DNS standards documents. Furthermore, PowerDNS interfaces with almost any database.
The PowerDNS Nameserver utilizes, a flexible backend architecture can access DNS information from any data source. This includes file formats, Bind zone files, relational databases or LDAP directories.
If you have specific needs for your DNS infrastructure then you can use the Backend Developers Kit to write the glue between PowerDNS and your data or logic.
There is one master database that is replicated to two slave databases. The slave databases are read-only and are updated immediately when the master database changes.
For sites that do not yet have an existing database infrastructure we recommend the MySQL database. MySQL is very easy to setup and handles replication well.
If your nameservers are located on different physical networks then you immediately take advantage of the distributed nature of DNS. Questions will be load balanced on your array of servers. If a server is down then one of the other servers is queried.
PowerDNS is by default configured to serve all information directly from a database, which results in unmatched maintainability of your DNS information.
PowerDNS has developed a complete suite of technologies surrounding Internet Naming and email. Internet Naming is at the core of all online activities and is involved in each and every transaction on the net. Email remains the killer application of the Internet.
Enhancements:
- This release fixes many issues, unifies the PowerDNS Recursor and Authoritative DNS infrastructure (reducing code size by 2,000 lines), significantly improves the "BIND" compatibility mode (making real life zone loading up to 30 times faster than the original BIND), addresses many corner cases, reworks the TCP backend for improved stability, and makes 64 bit packages available.
<<lessIt is written from scratch and conforms to all relevant DNS standards documents. Furthermore, PowerDNS interfaces with almost any database.
The PowerDNS Nameserver utilizes, a flexible backend architecture can access DNS information from any data source. This includes file formats, Bind zone files, relational databases or LDAP directories.
If you have specific needs for your DNS infrastructure then you can use the Backend Developers Kit to write the glue between PowerDNS and your data or logic.
There is one master database that is replicated to two slave databases. The slave databases are read-only and are updated immediately when the master database changes.
For sites that do not yet have an existing database infrastructure we recommend the MySQL database. MySQL is very easy to setup and handles replication well.
If your nameservers are located on different physical networks then you immediately take advantage of the distributed nature of DNS. Questions will be load balanced on your array of servers. If a server is down then one of the other servers is queried.
PowerDNS is by default configured to serve all information directly from a database, which results in unmatched maintainability of your DNS information.
PowerDNS has developed a complete suite of technologies surrounding Internet Naming and email. Internet Naming is at the core of all online activities and is involved in each and every transaction on the net. Email remains the killer application of the Internet.
Enhancements:
- This release fixes many issues, unifies the PowerDNS Recursor and Authoritative DNS infrastructure (reducing code size by 2,000 lines), significantly improves the "BIND" compatibility mode (making real life zone loading up to 30 times faster than the original BIND), addresses many corner cases, reworks the TCP backend for improved stability, and makes 64 bit packages available.
Download (2.77MB)
Added: 2007-04-21 License: GPL (GNU General Public License) Price:
916 downloads
Secleted [ 0 ] software to compare
Copyright Notice:
Software piracy is theft, Using crack, password, serial numbers, registration codes, key generators is illegal and prevent future software development. The above policy daemon 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