conf file
Sponsored Links
Sponsored Links
Secleted [ 0 ] software to compare
Results 1 - 15 of about 668
App::Conf::File 0.965
App::Conf::File is a Perl module to load and access configuration data. more>>
App::Conf::File is a Perl module to load and access configuration data.
SYNOPSIS
use App::Conf;
$config = App::Conf->new();
$config = App::Conf->new(configFile => $file);
print $config->dump(), "n"; # use Data::Dumper to spit out the Perl representation
# accessors
$property_value = $config->get($property_name);
$branch = $config->get_branch($branch_name); # get hashref of properties
# on-demand loading helper methods (private methods)
$config->overlay($config2); # merge the two config structures using overlay rules
$config->overlay($config1, $config2); # merge $config2 onto $config1
$config->graft($branch_name, $config2); # graft new config structure onto branch
# By convention, the configurations for each App-Context service will be located
# two levels under the hash ref as shown.
$config->{Conf} # config settings for all Conf services
$config->{Conf}{default} # config settings for the default Conf service
$config->{Security} # config settings for all Security services
$config->{Security}{default} # config settings for the default Security service
$config->{Template}{tt} # config settings for the Template service named "tt"
# The default driver (if "configClass" not supplied) reads in a Perl
# data structure from the file. Alternate drivers can read a Storable,
# unvalidated XML, DTD-validated XML, RDF-validated XML, or any other
# file format or data source anyone cares to write a driver for.
$conf = {
Standard => {
Log-Dispatch => {
logdir => /var/p5ee,
}
},
Authen => {
passwd => /etc/passwd,
seed => 303292,
},
};
# A comparable unvalidating XML file would look like this.
< conf>
< Standard>
< Log-Dispatch logdir="/var/p5ee"/>
< /Standard>
< Authen passwd="/etc/passwd" seed="303292"/>
< /conf>
# A comparable ini file (.ini) would look like this.
[Standard.Log-Dispatch]
logdir = /var/p5ee
[Authen]
passwd = /etc/passwd
seed = 303292
# A comparable Java properties-like file would look like this.
Standard.Log-Dispatch.logdir = /var/p5ee
Authen.passwd = /etc/passwd
Authen.seed = 303292
<<lessSYNOPSIS
use App::Conf;
$config = App::Conf->new();
$config = App::Conf->new(configFile => $file);
print $config->dump(), "n"; # use Data::Dumper to spit out the Perl representation
# accessors
$property_value = $config->get($property_name);
$branch = $config->get_branch($branch_name); # get hashref of properties
# on-demand loading helper methods (private methods)
$config->overlay($config2); # merge the two config structures using overlay rules
$config->overlay($config1, $config2); # merge $config2 onto $config1
$config->graft($branch_name, $config2); # graft new config structure onto branch
# By convention, the configurations for each App-Context service will be located
# two levels under the hash ref as shown.
$config->{Conf} # config settings for all Conf services
$config->{Conf}{default} # config settings for the default Conf service
$config->{Security} # config settings for all Security services
$config->{Security}{default} # config settings for the default Security service
$config->{Template}{tt} # config settings for the Template service named "tt"
# The default driver (if "configClass" not supplied) reads in a Perl
# data structure from the file. Alternate drivers can read a Storable,
# unvalidated XML, DTD-validated XML, RDF-validated XML, or any other
# file format or data source anyone cares to write a driver for.
$conf = {
Standard => {
Log-Dispatch => {
logdir => /var/p5ee,
}
},
Authen => {
passwd => /etc/passwd,
seed => 303292,
},
};
# A comparable unvalidating XML file would look like this.
< conf>
< Standard>
< Log-Dispatch logdir="/var/p5ee"/>
< /Standard>
< Authen passwd="/etc/passwd" seed="303292"/>
< /conf>
# A comparable ini file (.ini) would look like this.
[Standard.Log-Dispatch]
logdir = /var/p5ee
[Authen]
passwd = /etc/passwd
seed = 303292
# A comparable Java properties-like file would look like this.
Standard.Log-Dispatch.logdir = /var/p5ee
Authen.passwd = /etc/passwd
Authen.seed = 303292
Download (0.12MB)
Added: 2007-06-21 License: Perl Artistic License Price:
856 downloads
xconfig 2.1.0
xconfig is a tool to configure XF86Config and xorg.conf from the command line. more>>
xconfig projetc is a software to configure XF86Config and xorg.conf from the command line.
xconfig is licensed under GPLv2.
<<lessxconfig is licensed under GPLv2.
Download (0.035MB)
Added: 2006-06-26 License: GPL (GNU General Public License) Price:
1218 downloads
XML::Conf 0.04
XML::Conf is a simple configuration module based on XML. more>>
XML::Conf is a simple configuration module based on XML.
SYNOPSIS
Here follows some examples as the tests are done.
use XML::Conf;
my $c = XML::Conf->new($filename);
$w = $c->FIRSTKEY();
$v = $c->NEXTKEY();
$c->EXISTS($v);
$c->DELETE($v);
$c->CLEAR();
This is the description of the class, currently it only containg only the descriptions of the private and public methods and attributes.
<<lessSYNOPSIS
Here follows some examples as the tests are done.
use XML::Conf;
my $c = XML::Conf->new($filename);
$w = $c->FIRSTKEY();
$v = $c->NEXTKEY();
$c->EXISTS($v);
$c->DELETE($v);
$c->CLEAR();
This is the description of the class, currently it only containg only the descriptions of the private and public methods and attributes.
Download (0.006MB)
Added: 2006-09-08 License: Perl Artistic License Price:
1141 downloads
gmodconfig 0.6
gmodconfig aims to provide a simple way for end-users to download, install, configure and update Linux kernel modules. more>>
gmodconfig aims to provide a simple way for end-users to download, install, configure and update Linux kernel modules, in the language of their choosing, through an easy-to-use graphic interface.
gmodconfig is a Gnome application which allows Linux users to:
Main features:
- configure kernel modules parameters, in their native language (if such translations exist),
- check for new versions of kernel modules, as well as download, build and install those
- access kernel modules informations (license, authors, link to website)
Its mainly aimed at inexperienced Linux users, however even long time Linux users might find it useful!
A user might have to set or modify kernel modules parameters in order to get a device driver to work properly on his/her system. One way to assign values to kernel modules parameters is to edit the /etc/modules.conf file. Another way is to load the kernel modules manually on the command line and pass them parameter values at that time. Neither of which is convenient or doable by non-experienced users.
Non-English speakers might find configuring kernel modules parameters even more difficult since informations on parameters returned by modinfo are only available in English.
Another obstacle is that the set of valid parameters values is not always apparent in modinfos output. For example an "on/off" type of parameter will be documented as being an integer, since boolean is not a supported type. Or an integer parameter whose valid values are 0, 1 and 2 might be documented as integer instead of a [0,2] array. This might make it difficult to users to figure out which values can be assigned to a parameter.
Checking for updates, download, build and install a new version of a Linux kernel module is not an easy task for newbie Linux users. There ought to be an easy and automated way to do all this.
gmodconfig solves these problems by reading accurate parameter types, parameter descriptions translations, and extra informations such as a link to the module authors website from XML files, that are released along with gmodconfig. Using this data as well as modinfos output, gmodconfig is able to dynamically build a user-friendly graphic interface which presents the list of parameters that each kernel modules supports.
Boolean parameters can be toggled on and off with a check box. Array parameters, that is, parameters whose valid values fall between a "min" and a "max" values are represented by a pulldown list. Other types of parameters are simple text entry fields.
Users can navigate through the available modules or search a module by name, change parameters settings at will, and will be able (in a future release) to "give it a try" by (re)loading modules, all from the graphic interface. Unsaved modifications can be cancelled at any time, and can also be written out to the /etc/modules.conf configuration file.
Users have the ability to check for new releases of a module if the module author is keeping an XSA file up-to-date on the Net. The gmodconfigedit tool helps module authors create and update those XSA files.
Finally, gmodconfig supports downloading and installing DKMS packages (work in progress).
<<lessgmodconfig is a Gnome application which allows Linux users to:
Main features:
- configure kernel modules parameters, in their native language (if such translations exist),
- check for new versions of kernel modules, as well as download, build and install those
- access kernel modules informations (license, authors, link to website)
Its mainly aimed at inexperienced Linux users, however even long time Linux users might find it useful!
A user might have to set or modify kernel modules parameters in order to get a device driver to work properly on his/her system. One way to assign values to kernel modules parameters is to edit the /etc/modules.conf file. Another way is to load the kernel modules manually on the command line and pass them parameter values at that time. Neither of which is convenient or doable by non-experienced users.
Non-English speakers might find configuring kernel modules parameters even more difficult since informations on parameters returned by modinfo are only available in English.
Another obstacle is that the set of valid parameters values is not always apparent in modinfos output. For example an "on/off" type of parameter will be documented as being an integer, since boolean is not a supported type. Or an integer parameter whose valid values are 0, 1 and 2 might be documented as integer instead of a [0,2] array. This might make it difficult to users to figure out which values can be assigned to a parameter.
Checking for updates, download, build and install a new version of a Linux kernel module is not an easy task for newbie Linux users. There ought to be an easy and automated way to do all this.
gmodconfig solves these problems by reading accurate parameter types, parameter descriptions translations, and extra informations such as a link to the module authors website from XML files, that are released along with gmodconfig. Using this data as well as modinfos output, gmodconfig is able to dynamically build a user-friendly graphic interface which presents the list of parameters that each kernel modules supports.
Boolean parameters can be toggled on and off with a check box. Array parameters, that is, parameters whose valid values fall between a "min" and a "max" values are represented by a pulldown list. Other types of parameters are simple text entry fields.
Users can navigate through the available modules or search a module by name, change parameters settings at will, and will be able (in a future release) to "give it a try" by (re)loading modules, all from the graphic interface. Unsaved modifications can be cancelled at any time, and can also be written out to the /etc/modules.conf configuration file.
Users have the ability to check for new releases of a module if the module author is keeping an XSA file up-to-date on the Net. The gmodconfigedit tool helps module authors create and update those XSA files.
Finally, gmodconfig supports downloading and installing DKMS packages (work in progress).
Download (0.30MB)
Added: 2005-08-12 License: GPL (GNU General Public License) Price:
1533 downloads
Config::Model 0.612
Config::Model provides a framework to help in validating the semantic content of configuration data. more>>
Config::Model provides a framework to help in validating the semantic content of configuration data.
Config::Model can also be used to provide a semantic check of options of a complex program like mplayer or transcode.
How does this work ?
Using this project, a typical configuration validation tool will be made of 3 parts :
- The user interface
- The validation engine which is in charge of validating all the configuration information provided by the user.
- The storage facility that store the configuration information
Dont we already have some configuration validation tools ?
Youre probably thinking of tools like webmin. Yes, these tools exist and work fine, but they have their set of drawbacks.
Usually, the validation of configuration data is done with a script which performs semantic validation and often ends up being quite complex (e.g. 2500 lines for Debians xserver-xorg.config script which handles xorg.conf file).
In most cases, the configuration model is expressed in instructions (whatever programming language is used) and interspersed with a lot of processing to handle the actual configuration data.
Whats the advantage of this project ?
The Config::Model projects provide a way to get a validation engine where the configuration model is completely separated from the actual processing instruction.
The configuration model is expressed in a declarative form (i.e. a Perl data structure) which is always easier to maintain than a lot of code.
The declaration specifies:
- the structure of the configuration data (which can be queried by generic user interfaces)
- the properties of each element (boundaries, check, integer or string, enum like type ...)
- the default values of parameters (if any)
- mandatory parameters
- the targeted audience (intermediate, advance, master)
- on-line help (for ach parameter or value of parameter)
- the level of expertise of each parameter (to hide expert parameters from newbie eyes)
So, in the end:
- maintenance and evolution of the configuration content is easier
- user will see a *common* interface for *all* programs using this project.
- user will not see advanced parameters
- upgrade of configuration data is easier and sanity check is performed
- audit of configuration is possible to check what was modified by the user compat
Enhancements:
- This release provides some bugfixes and some new features.
- It has the ability to preserve the order of the keys of a hash element (ordered hash).
- It has the ability to dump and read configuration data as a Perl data structure.
<<lessConfig::Model can also be used to provide a semantic check of options of a complex program like mplayer or transcode.
How does this work ?
Using this project, a typical configuration validation tool will be made of 3 parts :
- The user interface
- The validation engine which is in charge of validating all the configuration information provided by the user.
- The storage facility that store the configuration information
Dont we already have some configuration validation tools ?
Youre probably thinking of tools like webmin. Yes, these tools exist and work fine, but they have their set of drawbacks.
Usually, the validation of configuration data is done with a script which performs semantic validation and often ends up being quite complex (e.g. 2500 lines for Debians xserver-xorg.config script which handles xorg.conf file).
In most cases, the configuration model is expressed in instructions (whatever programming language is used) and interspersed with a lot of processing to handle the actual configuration data.
Whats the advantage of this project ?
The Config::Model projects provide a way to get a validation engine where the configuration model is completely separated from the actual processing instruction.
The configuration model is expressed in a declarative form (i.e. a Perl data structure) which is always easier to maintain than a lot of code.
The declaration specifies:
- the structure of the configuration data (which can be queried by generic user interfaces)
- the properties of each element (boundaries, check, integer or string, enum like type ...)
- the default values of parameters (if any)
- mandatory parameters
- the targeted audience (intermediate, advance, master)
- on-line help (for ach parameter or value of parameter)
- the level of expertise of each parameter (to hide expert parameters from newbie eyes)
So, in the end:
- maintenance and evolution of the configuration content is easier
- user will see a *common* interface for *all* programs using this project.
- user will not see advanced parameters
- upgrade of configuration data is easier and sanity check is performed
- audit of configuration is possible to check what was modified by the user compat
Enhancements:
- This release provides some bugfixes and some new features.
- It has the ability to preserve the order of the keys of a hash element (ordered hash).
- It has the ability to dump and read configuration data as a Perl data structure.
Download (0.086MB)
Added: 2007-07-28 License: LGPL (GNU Lesser General Public License) Price:
818 downloads
GPPPoE-Conf 0.3
GPPPoE-Conf provides a tool for configuring PPPoE and Speedtouch ADSL modems. more>>
GPPPoE-Conf provides a tool for configuring PPPoE and Speedtouch ADSL modems.
GPPPoE-Conf is a graphical application made with GTK 2 to create PPPoE accounts used by pppd. It also contains a script for configurating Speedtouch ADSL modems. This program was formerly known as "Speedtouch Installer".
The support for Speedtouch modules is make through speedtouch-pppoe script located in src/
Enhancements:
- Changed contents dir function to glib one
- Better work on the account file and in the pppoe options (from rp-pppoe script)
- Gateway option (avoids having to set the MTU on all the hosts on the LAN by changing the MSS)
- Inteligent LCP/pppoe timeout relation
- Synchronous encapsulation for optimized performance (on by default)
<<lessGPPPoE-Conf is a graphical application made with GTK 2 to create PPPoE accounts used by pppd. It also contains a script for configurating Speedtouch ADSL modems. This program was formerly known as "Speedtouch Installer".
The support for Speedtouch modules is make through speedtouch-pppoe script located in src/
Enhancements:
- Changed contents dir function to glib one
- Better work on the account file and in the pppoe options (from rp-pppoe script)
- Gateway option (avoids having to set the MTU on all the hosts on the LAN by changing the MSS)
- Inteligent LCP/pppoe timeout relation
- Synchronous encapsulation for optimized performance (on by default)
Download (0.11MB)
Added: 2007-02-28 License: GPL (GNU General Public License) Price:
972 downloads
gShieldConf 0.40
gShieldConf is a small program to edit the gShield configuration files. more>>
gShield is an aggressive, modular, ipchains-based firewall script. gShieldConf is a small program to edit the configuration files for it. It is written using the gtk toolkit. It is released under the GNU GPL.
Please note, gShield must be installed prior to running gshieldconf. The program will load (and save) the gShield configuration file(s). It uses the contents of the file to determine the settings for the user interface. Anything defined in the user interface but not in the conf file can be changed, but the changes will not be saved after that.
Main features:
- Simple and easy to see the firewall configuration at a glance.
- Preserves unknown variables.
- Preserves comments and formatting of conf files
- Easy to extend when the conf file is changed.
Version restrictions:
- No way to activate the changes that have been made (ie, run gShield.rc).
- The conf files must be installed before running gshieldconf. In other words you cannot use gshieldconf to create a new script.
- No revert/undo operation. It is actually rather easy to support a single level of undo. I may do this at some point.
- Doesnt actually check to see if there have been any changes before saving the config files out.
- The Firewall Root directory must exist, it will not be creat
Enhancements:
- Removed Save As and Load menu items/code. I have done this because it was an ill conceived feature and doesnt make sense anymore.
- Made it compile and work with both libxml1 and libxml2.
- Removed last vestiges of hard coded file paths (specifically the paths to the gShield configuration files).
- Seperated the program from the controls.xml file. This was done to better be able to maintain the controls.xml file and to support multiple versions of gShield.
- Added a new UI control type, the combo box. This is to support the tri-state fields in gShield2.6 and up.
- The structure of controls.xml has changed a bit. Mostly added a new node type, Configfiles to specify the locations of the files to be loaded.
<<lessPlease note, gShield must be installed prior to running gshieldconf. The program will load (and save) the gShield configuration file(s). It uses the contents of the file to determine the settings for the user interface. Anything defined in the user interface but not in the conf file can be changed, but the changes will not be saved after that.
Main features:
- Simple and easy to see the firewall configuration at a glance.
- Preserves unknown variables.
- Preserves comments and formatting of conf files
- Easy to extend when the conf file is changed.
Version restrictions:
- No way to activate the changes that have been made (ie, run gShield.rc).
- The conf files must be installed before running gshieldconf. In other words you cannot use gshieldconf to create a new script.
- No revert/undo operation. It is actually rather easy to support a single level of undo. I may do this at some point.
- Doesnt actually check to see if there have been any changes before saving the config files out.
- The Firewall Root directory must exist, it will not be creat
Enhancements:
- Removed Save As and Load menu items/code. I have done this because it was an ill conceived feature and doesnt make sense anymore.
- Made it compile and work with both libxml1 and libxml2.
- Removed last vestiges of hard coded file paths (specifically the paths to the gShield configuration files).
- Seperated the program from the controls.xml file. This was done to better be able to maintain the controls.xml file and to support multiple versions of gShield.
- Added a new UI control type, the combo box. This is to support the tri-state fields in gShield2.6 and up.
- The structure of controls.xml has changed a bit. Mostly added a new node type, Configfiles to specify the locations of the files to be loaded.
Download (0.12MB)
Added: 2006-07-10 License: GPL (GNU General Public License) Price:
1202 downloads
yavipin-conf 0.0.1
yavipin-conf is a multiple client / server configuration utility for yavipin a la vtun. more>>
This utility is meant to ease the configuration of yavipin on both clients and servers. It foll.ows the same configuration scheme as vtun, so people migrating from vtun will not find any difficulties writing up yavipin confs.
Yavipind is a secure tunnel aka 2 peers securely forwarding packets toward each other. It forwards any kind of packet (IPv4, IPv6 or other) sent over the virtual point-to-point device (e.g. tun0). It fully runs in linux userspace.
<<lessYavipind is a secure tunnel aka 2 peers securely forwarding packets toward each other. It forwards any kind of packet (IPv4, IPv6 or other) sent over the virtual point-to-point device (e.g. tun0). It fully runs in linux userspace.
Download (0.003MB)
Added: 2005-04-19 License: LGPL (GNU Lesser General Public License) Price:
1648 downloads
CGI::Ex::Conf 2.06
CGI::Ex::Conf is a Perl module with Conf Reader/Writer for many different data format types. more>>
CGI::Ex::Conf is a Perl module with Conf Reader/Writer for many different data format types.
SYNOPSIS
use CGI::Ex::Conf qw(conf_read conf_write);
my $hash = conf_read("/tmp/foo.yaml");
conf_write("/tmp/foo.yaml", {key1 => $val1, key2 => $val2});
### OOP interface
my $cob = CGI::Ex::Conf->new;
my $full_path_to_file = "/tmp/foo.val"; # supports ini, sto, val, pl, xml
my $hash = $cob->read($file);
local $cob->{default_ext} = conf; # default anyway
my @paths = qw(/tmp, /home/pauls);
local $cob->{paths} = @paths;
my $hash = $cob->read(My::NameSpace);
# will look in /tmp/My/NameSpace.conf and /home/pauls/My/NameSpace.conf
my $hash = $cob->read(My::NameSpace, {paths => [/tmp]});
# will look in /tmp/My/NameSpace.conf
local $cob->{directive} = MERGE;
my $hash = $cob->read(FooSpace);
# OR #
my $hash = $cob->read(FooSpace, {directive => MERGE});
# will return merged hashes from /tmp/FooSpace.conf and /home/pauls/FooSpace.conf
# immutable keys are preserved from originating files
local $cob->{directive} = FIRST;
my $hash = $cob->read(FooSpace);
# will return values from first found file in the path.
local $cob->{directive} = LAST; # default behavior
my $hash = $cob->read(FooSpace);
# will return values from last found file in the path.
### manipulate $hash
$cob->write(FooSpace); # will write it out the changes
There are half a million Conf readers out there. Why not add one more. Actually, this module provides a wrapper around the many file formats and the config modules that can handle them. It does not introduce any formats of its own.
This module also provides a preload ability which is useful in conjunction with mod_perl.
<<lessSYNOPSIS
use CGI::Ex::Conf qw(conf_read conf_write);
my $hash = conf_read("/tmp/foo.yaml");
conf_write("/tmp/foo.yaml", {key1 => $val1, key2 => $val2});
### OOP interface
my $cob = CGI::Ex::Conf->new;
my $full_path_to_file = "/tmp/foo.val"; # supports ini, sto, val, pl, xml
my $hash = $cob->read($file);
local $cob->{default_ext} = conf; # default anyway
my @paths = qw(/tmp, /home/pauls);
local $cob->{paths} = @paths;
my $hash = $cob->read(My::NameSpace);
# will look in /tmp/My/NameSpace.conf and /home/pauls/My/NameSpace.conf
my $hash = $cob->read(My::NameSpace, {paths => [/tmp]});
# will look in /tmp/My/NameSpace.conf
local $cob->{directive} = MERGE;
my $hash = $cob->read(FooSpace);
# OR #
my $hash = $cob->read(FooSpace, {directive => MERGE});
# will return merged hashes from /tmp/FooSpace.conf and /home/pauls/FooSpace.conf
# immutable keys are preserved from originating files
local $cob->{directive} = FIRST;
my $hash = $cob->read(FooSpace);
# will return values from first found file in the path.
local $cob->{directive} = LAST; # default behavior
my $hash = $cob->read(FooSpace);
# will return values from last found file in the path.
### manipulate $hash
$cob->write(FooSpace); # will write it out the changes
There are half a million Conf readers out there. Why not add one more. Actually, this module provides a wrapper around the many file formats and the config modules that can handle them. It does not introduce any formats of its own.
This module also provides a preload ability which is useful in conjunction with mod_perl.
Download (0.21MB)
Added: 2006-10-07 License: Perl Artistic License Price:
1113 downloads
BindConfig 20010828
BindConfig is a tool to reduce the error prone work of maintaining BINDs zone files. more>>
BindConfig is a tool to reduce the error prone work of maintaining BINDs zone files. More precisely, BindConfig is the name of a Python module which can read BINDs zone files and named.conf files, and can modify and save BINDs zone files.
The zone files written by the module will be as concise as possible, since you as an admin are more likely to spot errors in a file which only has the information necessary. The zone files are written to conform to BINDs expectations and with BINDs style guide. There will be an ORIGIN directive and a TTL directive at the top of the zone. All hostnames will be relative to the toplevel ORIGIN, except for absolute hostnames outside of the zone.
BindConfig comes with an interactive shell for editing your zone files.
Invoke the shell with the name of the zone you want to edit. It will parse your systems named.conf file for the location of the zone, and parse that file in turn. When the shell exits, it will save the zone file.
edit-zone dragonsdawn.net
edit-zone:
Copyright 2001 Gordon Messmer
This is free software with ABSOLUTELY NO WARRANTY.
For details type warranty.
Parsing file: /etc/named.conf
Done
Parsing zone: dragonsdawn.net
Done
>
If all goes well, (no missing files), youll be in the edit-zone shell. Type help for a list of available commands. You can print the zone, list records using wildcards, delete records using wildcards, add records or read commands from a file. You can also pipe commands to the shell:
cat zone-commands | edit-zone dragonsdawn.net
echo add CNAME for www bind-config | edit-zone dragonsdawn.net
<<lessThe zone files written by the module will be as concise as possible, since you as an admin are more likely to spot errors in a file which only has the information necessary. The zone files are written to conform to BINDs expectations and with BINDs style guide. There will be an ORIGIN directive and a TTL directive at the top of the zone. All hostnames will be relative to the toplevel ORIGIN, except for absolute hostnames outside of the zone.
BindConfig comes with an interactive shell for editing your zone files.
Invoke the shell with the name of the zone you want to edit. It will parse your systems named.conf file for the location of the zone, and parse that file in turn. When the shell exits, it will save the zone file.
edit-zone dragonsdawn.net
edit-zone:
Copyright 2001 Gordon Messmer
This is free software with ABSOLUTELY NO WARRANTY.
For details type warranty.
Parsing file: /etc/named.conf
Done
Parsing zone: dragonsdawn.net
Done
>
If all goes well, (no missing files), youll be in the edit-zone shell. Type help for a list of available commands. You can print the zone, list records using wildcards, delete records using wildcards, add records or read commands from a file. You can also pipe commands to the shell:
cat zone-commands | edit-zone dragonsdawn.net
echo add CNAME for www bind-config | edit-zone dragonsdawn.net
Download (0.008MB)
Added: 2006-07-05 License: GPL (GNU General Public License) Price:
1207 downloads
dtRdr::Config 0.0.11
dtRdr::Config is a Perl module with Factory class for configuration system. more>>
dtRdr::Config is a Perl module with Factory class for configuration system.
Factory Methods
factory_read_config
Constructor function (see new)
my $obj = factory_read_config($file);
new
$conf = dtRdr::Config->new($file);
get_library_info
my @libraries = $conf->get_library_info;
<<lessFactory Methods
factory_read_config
Constructor function (see new)
my $obj = factory_read_config($file);
new
$conf = dtRdr::Config->new($file);
get_library_info
my @libraries = $conf->get_library_info;
Download (2.8MB)
Added: 2007-03-14 License: Perl Artistic License Price:
955 downloads
Chango 1.0
Chango is a system for cacheing MP3 files from multidisc cdrom drives. more>>
Chango is a system for cacheing MP3 files from multidisc cdrom drives. Since you cant actually mount different discs in the same physical device simultaneously, this software will cache the files you need off to a predetermined cache, so that all of the needed files will be available simultaneously.
This is how to configure it for your system;
Edit the drives.conf file in accordance to how your machine is set up. The included .conf file shows two drives, each holding a max of 4 discs.
/dev/cdrom0:/mnt/cdrom0:4
/dev/cdrom1:/mnt/cdrom1:4
I setup symlinks in /dev from /dev/cdrom0 to /dev/hdc and a second one from /dev/cdrom1 to /dev/hdd. Make sure these are read/execute by the user who will be running the software. I am using a RedHat distro, so all mounted devices will end up in /mnt. so, my /etc/fstab shows the following:
/dev/cdrom0 /mnt/cdrom0 iso9660 noauto,owner,ro 0 0
/dev/cdrom1 /mnt/cdrom1 iso9660 noauto,owner,ro 0 0
So, by looking at both files, you should see that there is a corrolation between the two.
At this point, you should be able to mount /mnt/cdrom0 as whatever user will be running the script. As well, you should be able to change disks using eject -c 2 /dev/cdrom0 to swap disks.
Run the scandrives.pl script. perl scandrives.pl This will scan the CDs in the drives, and create the database files based on the mp3s. It should show you the directories it is working through as its working. If it notices that the cd is the same as the one it had already scanned, it will skip it. (This is so that if you change just one disc, you can re-run the app, and it will only do the full work on the new or changed discs.)
<<lessThis is how to configure it for your system;
Edit the drives.conf file in accordance to how your machine is set up. The included .conf file shows two drives, each holding a max of 4 discs.
/dev/cdrom0:/mnt/cdrom0:4
/dev/cdrom1:/mnt/cdrom1:4
I setup symlinks in /dev from /dev/cdrom0 to /dev/hdc and a second one from /dev/cdrom1 to /dev/hdd. Make sure these are read/execute by the user who will be running the software. I am using a RedHat distro, so all mounted devices will end up in /mnt. so, my /etc/fstab shows the following:
/dev/cdrom0 /mnt/cdrom0 iso9660 noauto,owner,ro 0 0
/dev/cdrom1 /mnt/cdrom1 iso9660 noauto,owner,ro 0 0
So, by looking at both files, you should see that there is a corrolation between the two.
At this point, you should be able to mount /mnt/cdrom0 as whatever user will be running the script. As well, you should be able to change disks using eject -c 2 /dev/cdrom0 to swap disks.
Run the scandrives.pl script. perl scandrives.pl This will scan the CDs in the drives, and create the database files based on the mp3s. It should show you the directories it is working through as its working. If it notices that the cd is the same as the one it had already scanned, it will skip it. (This is so that if you change just one disc, you can re-run the app, and it will only do the full work on the new or changed discs.)
Download (0.004MB)
Added: 2006-07-19 License: GPL (GNU General Public License) Price:
1192 downloads
MonAMI 0.9
MonAMI is a friendly monitoring daemon. more>>
MonAMI aims to be a standard place for monitoring services availability and performance, talking to many different monitoring systems whilst remaining easy to configure.
MonAMI project has a plugin structure, making it easy to add new things to monitor, or integrate with new monitoring systems.
MonAMI uses a plugin architecture to allow it to be extended by developing new targets. Information is provided by plugins and delivered to different destination by targets.
MonAMI-core mediates the flow of information, collecting data from plugins when the data is needed and sending it to the correct destination.
Enhancements:
- Two new monitoring plugins for clusters: torque and maui.
- Big improvement to the Ganglia plugin: it now supports dynamic dmax values, a gmond.conf file parser, and is careful not to overload gmond.
- ksysguard is more conservative, only allowing local connections by default, fluidsynth handles disconnects better, nut has better parsing of error messages and handles disconnects better, and nagios allows the user to specify localhosts host name.
<<lessMonAMI project has a plugin structure, making it easy to add new things to monitor, or integrate with new monitoring systems.
MonAMI uses a plugin architecture to allow it to be extended by developing new targets. Information is provided by plugins and delivered to different destination by targets.
MonAMI-core mediates the flow of information, collecting data from plugins when the data is needed and sending it to the correct destination.
Enhancements:
- Two new monitoring plugins for clusters: torque and maui.
- Big improvement to the Ganglia plugin: it now supports dynamic dmax values, a gmond.conf file parser, and is careful not to overload gmond.
- ksysguard is more conservative, only allowing local connections by default, fluidsynth handles disconnects better, nut has better parsing of error messages and handles disconnects better, and nagios allows the user to specify localhosts host name.
Download (0.20MB)
Added: 2007-08-15 License: BSD License Price:
802 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
Mckoi SQL Database 1.0.3
Mckoi SQL Database is a Java relational database management system. more>>
Mckoi SQL Database is a full featured SQL-92 relational database management system written in Java.
The software can operate as either a dedicated multi-client, multi-threaded database server, or can be used as an embedded database inside a Java application.
The engine is designed to be easy to use and maintain and versatile for sophisticated database development tasks. The software provides a JDBC 2.0 driver.
To use Mckoi SQL Database, you will need a JavaTM runtime environment version 1.2 or greater. Sun provides Java runtimes for Win32, Solaris and Linux from their website at http://www.javasoft.com/j2se/. IBM also provides various Java runtimes for a number of platforms at http://www.ibm.com/java/jdk/download/.
When Java has been installed on your system, unpack the mckoi distribution file to a directory in your file system. Then you are ready to create a database and develop your database application.
Creating A Database
Before you can begin development of your database application, you will need to create and configure a blank database. The database configuration file describes all of the configurable properties of the database (details of the database configuration file are covered in the next section). The software ships with a default configuration that looks for a database at path ./data in your filesystem.
To create a database using the default configuration with an admin username of admin_user and password aupass00, go to a prompt, change to the Mckoi Database distribution directory and type:
java -jar mckoidb.jar -create "admin_user" "aupass00"
We do not advise using either this username or password in a production system. The user created here has full control over every aspect of the database so choose a username / password carefully.
When the command has completed, a sub-directory called data will have been generated. This directory is used to store data from the database. A sub-directory called log is also generated which stores debugging and query log information.
Database Configuration
When you run the mckoidb.jar package, it looks for a file named db.conf in the current directory. This file contains a number of variables that determine where the database looks for information, as well as other user-definable properties. The configuration file can be renamed and copied to a different location. If you change the configuration file location, you must supply the location when you run the database;
java -jar mckoidb.jar -conf [location of conf file] .....
You can edit the configuration file with a text editor. The default configuration file that ships with the software contains extensive comments on what each variable does.
<<lessThe software can operate as either a dedicated multi-client, multi-threaded database server, or can be used as an embedded database inside a Java application.
The engine is designed to be easy to use and maintain and versatile for sophisticated database development tasks. The software provides a JDBC 2.0 driver.
To use Mckoi SQL Database, you will need a JavaTM runtime environment version 1.2 or greater. Sun provides Java runtimes for Win32, Solaris and Linux from their website at http://www.javasoft.com/j2se/. IBM also provides various Java runtimes for a number of platforms at http://www.ibm.com/java/jdk/download/.
When Java has been installed on your system, unpack the mckoi distribution file to a directory in your file system. Then you are ready to create a database and develop your database application.
Creating A Database
Before you can begin development of your database application, you will need to create and configure a blank database. The database configuration file describes all of the configurable properties of the database (details of the database configuration file are covered in the next section). The software ships with a default configuration that looks for a database at path ./data in your filesystem.
To create a database using the default configuration with an admin username of admin_user and password aupass00, go to a prompt, change to the Mckoi Database distribution directory and type:
java -jar mckoidb.jar -create "admin_user" "aupass00"
We do not advise using either this username or password in a production system. The user created here has full control over every aspect of the database so choose a username / password carefully.
When the command has completed, a sub-directory called data will have been generated. This directory is used to store data from the database. A sub-directory called log is also generated which stores debugging and query log information.
Database Configuration
When you run the mckoidb.jar package, it looks for a file named db.conf in the current directory. This file contains a number of variables that determine where the database looks for information, as well as other user-definable properties. The configuration file can be renamed and copied to a different location. If you change the configuration file location, you must supply the location when you run the database;
java -jar mckoidb.jar -conf [location of conf file] .....
You can edit the configuration file with a text editor. The default configuration file that ships with the software contains extensive comments on what each variable does.
Download (2.1MB)
Added: 2005-04-21 License: GPL (GNU General Public License) Price:
1649 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 conf file 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
