Mastering SOA: Exposing Services Through Rich User Interfaces
In this new installment to the "Mastering SOA" series, learn best practices for rich interface development in an SOA, based on the experiences of Collect America.
Hi,
I just started working on a script. After my research, i found a command which can help me:
AIM: To build a script which starts the services (Services 1) on server 1 automatically whenever its down. And it has a dependency on other service (Service 2) on Server 2.
So my script has to... (4 Replies)
Hi Al,
In course of understanding networking in Solaris, I have these doubts on Interfaces. Please clarify me. I have done fair research in this site and others but could not be clarified.
1. In the "ifconfig -a" command, I see many interfaces and their configurations. But I see many... (1 Reply)
Hi everybody, I'm running soalris 10, and I would like to know if it posible to boot on single user mode(init s), and then set up (may be manually or not) all the networks services, did someone try this before??
Tks (4 Replies)
here is the picture:
a website on server1 & a "username" logged in that site.
The same username has a shell(nologin)/ftp/samba/mail(qmail) acount on server2.
i have s form on server1 that can pass the username & its NEW password to a sript that should change all passwords on server2.
the... (5 Replies)
dsbl.conf(5) File Formats Manual dsbl.conf(5)NAME
dsbl.conf - configuration file for all DSBL testers
SYNOPSIS
vi /usr/local/etc/dsbl.conf
vi ~/.dsblrc
DESCRIPTION
dsbl.conf and .dsblrc both control the functioning of the DSBL test programs and DSBL server programs. ~/.dsblrc is read if it exists,
otherwise dsbl.conf in $PREFIX/etc is read. (PREFIX is set at compile time and is /usr/local by default.
These files are in the format:
variable_name="value"
variable_name2="value2"
Test program variables:
sender_user
If you were sending tests as test@example.com, you would set sender_user to "test".
sender_domain
If you were sending tests as test@example.com, you would set sender_domain to "example.com".
cookie_host
Host to retrieve testing cookies from (cookie.dsbl.org for the DSBL).
cookie_user
Username to provide to the cookie server to retrieve a cookie. To test anonymously, set this to "".
cookie_pass
Password to provide to the cookie server to retrieve a cookie. To test anonymously, set this to "".
target_user
If the listing address is listme@dsbl.org, you would set target_user to "listme".
target_domain
If the listing address is listme@dsbl.org, you would set target_domain to "dsbl.org".
statedir
The directory to store the current state (last test date) of IPs. Must be writable by spamtrap(1).
checklist
The list to check against before testing hosts. If you are an untrusted tester, this should be unconfirmed.dsbl.org, otherwise it
should be list.dsbl.org.
excluded_ip
Each excluded_ip entry is checked against the beginning of an IP before testing. You should list IPs that are local to you and
therefor shouldn't be tested.
http_port
An array of configuration variables to specify which ports HTTP proxies should be tested for on.
socks_port
An array of configuration variables to specify which ports SOCKS 4 and 5 proxies should be tested for on.
message
The actual message to send when relay testing.
parallel
A positive integer representing the number of test processes to run simultaneously.
verbosity
The amount of information to log to standard output. The options are:
0 No logging
1 Log IP addresses as they are tested
10 Debugging level; log everything
Server program variables:
mysql_host
The hostname to use to connect to the MySQL server.
mysql_user
The username to use to connect to the MySQL server.
mysql_pass
The password to use to connect to the MySQL server.
mysql_db
The name of the DSBL-compliant database on the MySQL server.
tempdir
The temporary directory in which to store zones while they are being built. This must be on the same filesystem as zonedir.
zonedir
The directory in which to store the zones once they are built. This must be on the same filesystem as tempdir.
unconfirmed_zone
The fully qualified domain name of the unconfirmed zone.
confirmed_zone
The fully qualified domain name of the confirmed (trusted) singlehop zone.
multihop_zone
The fully qualified domain name of the confirmed (trusted) multihop zone.
unconfirmed_nameserver
The nameserver of the unconfirmed zone that will be provided in SOA record.
confirmed_nameserver
The nameserver of the confirmed (trusted) singlehop zone that will be provided in the SOA record.
multihop_nameserver
The nameserver of the confirmed (trusted) multihop zone that will be provided in the SOA record.
zone_contact
The contact email address to be provided in the SOA records of both zones. This should have a period (.) instead of an at sign (@).
zone_message
The TXT message to provide for each IP in the zones. This should end in the dollar sign character ($) which is replaced by the IP
in question.
listenip
The IP address, in dotted quad notation, for the SMTP server to listen on.
clientsperip
The maximum number of clients per source IP address that will be accepted by the SMTP server. Additional clients from this IP
address will be turned away with a temporary error. This is used to prevent attacks from tying up the entire server.
idletimeout
The time, in seconds, before an idle SMTP session is terminated. This is used to keep server resources available for other connec-
tions.
AUTHOR
Ian Gulliver <ian@penguinhosting.net>
2002-04-03 dsbl.conf(5)
