somethingsomewhere.net

Lister les vms machine actives depuis votre Host

commande : vmrun

GENERAL COMMANDS PARAMETERS DESCRIPTION
---------------- ---------- -----------
list List all running VMs

upgradevm Path to vmx file Upgrade VM file format, virtual hw

installtools Path to vmx file Install Tools in Guest

register Path to vmx file Register a VM

unregister Path to vmx file Unregister a VM

listRegisteredVM List registered VMs

clone Path to vmx file Create a copy of the VM
Path to destination vmx file
full|linked
[Snapshot name]

Examples:

Starting a virtual machine with Workstation on a Windows host
vmrun -T ws start "c:\my VMs\myVM.vmx"

Stopping a virtual machine with Server on a linux host
vmrun -T server -h https://myHost.com/sdk -u hostUser -p hostPassword stop "[storage1] vm/myVM.vmx"

Running a program in a virtual machine with Workstation on a Windows host with Windows guest
vmrun -T ws -gu guestUser -gp guestPassword runProgramInGuest "c:\my VMs\myVM.vmx" "c:\Program Files\myProgram.exe"

Running a program in a virtual machine with Server on a linux host with linux guest
vmrun -T server -h https://myHost.com/sdk -u hostUser -p hostPassword -gu guestUser -gp guestPassword runProgramInGuest "[storage1] vm/myVM.vmx" /usr/bin/X11/xclock -display :0

Creating a snapshot of a virtual machine with Workstation on a Windows host
vmrun -T ws snapshot "c:\my VMs\myVM.vmx" mySnapshot

Reverting to a snapshot with Workstation on a Windows host
vmrun -T ws revertToSnapshot "c:\my VMs\myVM.vmx" mySnapshot

Deleting a snapshot with Workstation on a Windows host
vmrun -T ws deleteSnapshot "c:\my VMs\myVM.vmx" mySnapshot

Erreur invalid network name avec IIS

La machine ayant IIS a changé d'adresse IP, depuis impossible de demarrer votre Default Site web.
une erreur intervient lors de la tentative.

popup: "The format of the specified network name is invalid"

Verifier les adresses depuis la clef de base de registre:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Pa rameters\ListenOnlyList

127.0.0.1
192.168.x.x

- Modifiez la seconde IP qui doit correspondre l'adresse de la machine.
- Lancez une session dos, puis redemarrer IIS:
- net stop http /y
- net start w3svc

Une fois IIS de redemarré, re-tentez de demarrer votre site web

apt-get source pour Gutsy (ubuntu 7.10)

Modifiez le le fichier : /etc/apt/source.list

deb http://old-releases.ubuntu.com/ubuntu gutsy main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu gutsy main restricted universe multiverse

deb http://old-releases.ubuntu.com/ubuntu gutsy-updates main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu gutsy-updates main restricted universe multiverse

deb http://old-releases.ubuntu.com/ubuntu gutsy-security main restricted universe multiverse
deb-src http://old-releases.ubuntu.com/ubuntu gutsy-security main restricted universe multiverse

Limiter la vistesse de téléchargement avec wget

wget --limit-rate=20k http://downloadexemple.fr/file.tar.gz

Quelle ma Linux distribution?

cat /etc/issue

Novell SuSE
cat/etc/SuSE-release
Red Hat
cat /etc/redhat-release, /etc/redhat_version

Fedora
cat /etc/fedora-release

Slackware
cat /etc/slackware-release, /etc/slackware-version

Debian
cat /etc/debian_release, /etc/debian_version,

Mandrake
cat /etc/mandrake-release

Yellow dog
cat /etc/yellowdog-release

Sun JDS
cat /etc/sun-release

Solaris/Sparc
cat /etc/release

Gentoo
cat /etc/gentoo-release

----------------

Envoyer un fichier en FTP via un script

Ci joint le script :

#debut
#!/bin/sh

# Parametres: host FTP Server
# user FTP Username
# passwd FTP Password
# file File to send/put
############################################################################

# Variables
HOST=$1
USER=$2
PASSWD=$3
FILE=$4
TONAME=$5

# Connect to FTP HOST and Send File
ftp -n $HOST < quote USER $USER
quote PASS $PASSWD
dir
ascii
put $FILE $TONAME
dir
quit
END_SCRIPT
exit 0

####fin

la commande sera :
./ftpscript
exemple:

./ftpscript 192.168.1.xx joe motdepasse /var/log/messages /upload/messages.txt

Désactiver le firewall sous Redhat Enterprise

Arreter le Service:
# service iptables stop

Mettre a jour la config:
# chkconfig iptables off

Reduire la taille de fichiers JPG depuis un dossier

Installation de ImageMagick
sudo apt-get install imagemagick
Puis utiliser convert:

Code:

convert -resize 50% -quality 80 input.jpg output.jpg

Redimension la photo de 50% puis la qualité

Code:

find . -iname "*.jpg" | xargs -l -i convert -quality 75 {} /tmp/output/{}

Ajuste la Qualité de la photo

Afin d'appliquer les deux combinaisons :

find . -iname "*.jpg" | xargs -l -i convert -resize 800x600 -quality 75 {} /tmp/output/{}
ou encore:

for i in *.JPG; do convert -resize 800x600! -quality 75 "$i" web/"$i"; done

example de Scripts:
#!/bin/bash

# SET PICTURE'S PATH
path=/home/user/Photos/

# set variable date
NOW=$(date +"%d-%m-%y")

# condition
if [ -d $path/$NOW ] ; then

# does exist
cd $path/$NOW

# creating the folder for lower def
mkdir web

for i in *.JPG; do convert -resize 800x600! -quality 75 "$i" web/"$i"; done
echo 'created sub-folder called web and generated jpg'

else
# does not exist
echo 'folder is not present'

fi

Demarrer hellanzb en Service

Ci joint le bon script :

#!/bin/sh
# Authors: Ivo Trompert
#
#
# /etc/init.d/hellanzb
#
### BEGIN INIT INFO
# Provides: hellanzb
# Required-Start: $local_fs $remote_fs $network
# X-UnitedLinux-Should-Start:
# Required-Stop: $local_fs $remote_fs $network
# X-UnitedLinux-Should-Stop:
# Default-Start: 3 5
# Default-Stop: 0 1 2 6
# Short-Description: Hellanzb
# Description: Start the hellanzb daemon
### END INIT INFO

case "$1" in
start)
echo "Starting hellanzb"
su -c 'python /usr/local/bin/hellanzb.py -D -c /usr/local/etc/hellanzb.conf' || echo "Failed!" ;;
stop)
echo "hellanzb shutdown"
su -c 'python /usr/local/bin/hellanzb.py -D -c /usr/local/etc/hellanzb.conf shutdown' || echo "Failed!" ;;
status)
su -c 'python /usr/local/bin/hellanzb.py -D -c /usr/local/etc/hellanzb.conf status' || echo "Failed!" ;;
esac

Demarrer un Serveur Domino en service sous Linux

Un script bien utile pour une machine Serveur Domino sous Linux

Certaines variables et chemins sont a adapter.

/etc/init.d/domino
(chmod +x /etc/init.d/domino)

#!/bin/sh
#
# domino Start/stop the Lotus Domino server
#
# chkconfig: 345 01 95
# description: This script is used to start and stop the domino \
# server as a background process. It will send \
# the serverID password from a file to the server.\
# Communication with the server has to be done through \
# console, Notes Administrator or webadmin.\
#
# Usage: /etc/rc.d/init.d/domino start|stop|restart|condrestart
#
# process name: server, ...
#
# Version 1.1, by LB, 2205-01-07

# Change the USER, GROUP, DATA_DIR and BIN_DIR for your server
DOMINO_USER="notes"
DOMINO_GROUP="notes"
DOMINO_DATA_DIR="/var/local/notesdata"
DOMINO_BIN_DIR="/opt/lotus/bin"
LOCKFILE="/var/lock/subsys/domino"

export ODBCINI="/etc/odbc.ini"

# We need a file to put the serverID password in.
# Make sure the owner is the Domino owner and the file
# permissions are set to 400

SERVER_PASSWD_FILE="/var/local/notesdata/.domino.pwd"

# See if the user that runs this script is root

if [ `id -u` != 0 ]; then
echo "This script must be run by root only"
exit 1
fi

start() {
# First, check if the password file exists,
# and if not, exit with an errorcode
if [ ! -f $SERVER_PASSWD_FILE ] ; then
echo "Error: no password file."
exit 1
fi

# Set permission to 400 (read-only-owner)
# and ownership to $DOMINO_USER. These next lines are
# not necessary if the ownership was set correctly the first time.

chmod 400 $SERVER_PASSWD_FILE
chown $DOMINO_USER.$DOMINO_GROUP $SERVER_PASSWD_FILE

# Check we're not already running

if [ -f $LOCKFILE ] ; then
echo "Domino server apparently already running."
exit 1
fi

# Two ways to run the server (comment one of them out)
# 1. With the output of the console redirected to /var/log/domino.log
# Be sure to change the logrotate daemon.
# 2. With the output of the console redirected to /dev/null

echo -n "Starting domino server..."

# Version with logfile
su - ${DOMINO_USER} -c "cd ${DOMINO_DATA_DIR};\
cat ${SERVER_PASSWD_FILE} | ${DOMINO_BIN_DIR}/server" \
>> /var/log/domino 2>&1 &
RETVAL=$?
if [ "$RETVAL" = "0" ] ; then
touch $LOCKFILE > /dev/null 2>&1
fi
# Version without logfile
# su - ${DOMINO_USER} -c "cd ${DOMINO_DATA_DIR};\
# cat ${SERVER_PASSWD_FILE} |\
# ${DOMINO_BIN_DIR}/server" > /dev/null 2>&1 &

echo "done."
}

stop() {
echo -n "Stopping Domino server. "
su - ${DOMINO_USER} -c "cd ${DOMINO_DATA_DIR}; ${DOMINO_BIN_DIR}/server -q"
RETVAL=$?
# RETVAL is 38 on normal shutdown - what does *that* mean?
# Users should test this on their own systems . . .
if [ $RETVAL -lt 50 ] ; then
rm $LOCKFILE
fi
}

restart() {
stop
start
}

# See how we were called.

case $1 in
start)
start
;;
stop)
stop
;;
restart)
stop
start
;;
condrestart)
[ -f $LOCKFILE ] && restart
;;
*)
echo "Usage: domino {start|stop|restart|condrestart}"
exit 1
;;
esac
# End of the domino script
exit 0

Exemple SCP

Cette commande vous permet de copier des fichiers d'une machine a une autre via SSH.

# scp source destination

Copier un fichier 'file1.txt' d'une machine locale sur une machine distante dans le dossier /tmp:

scp file1.txt user@host:/tmp

Copier le meme fichier depuis la machine distante vers votre machine locale:

scp user@host:/path/file1.txt ./

-----

Copier un dossier complet sur une machine distante(send):

scp -r 'dossier' user@host:/path/dossier/

-----

Copier/rapatrier un dossier complet en local depuis une machine distante (get):

scp -r user@host:/path/'dossier' ./'dissierlocal'/

Activer Telnet acces root sur Solaris

Avant tout, avant de l'activer veuillez a ne pas solliciter ce type d'acces sur un server en production!!
La Security est plus que mauvaise!!!

Afin d'autoriser l'acces a root via telnet:
Editez le fichier suivant:
/etc/default/login puis rajouter/ commenter la ligne suivante:

# If CONSOLE is set, root can only login on that device.
# Comment this line out to allow remote login by root.
#
# CONSOLE=/dev/console

Ldap Search

Exemple:

ldapsearch -x -h -D '' -w '' -b '''(|mail=**)(proxyAddress=**))' dn proxyAddresses mail

Search options:
-a deref one of never (default), always, search, or find
-A retrieve attribute names only (no values)
-b basedn base dn for search
-E [!][=] search extensions (! indicates criticality)
[!]domainScope (domain scope)
[!]mv= (matched values filter)
[!]pr=[/prompt|noprompt] (paged results/prompt)
[!]subentries[=true|false] (subentries)
[!]sync=ro[/] (LDAP Sync refreshOnly)
rp[/][/] (LDAP Sync refreshAndPersist)
-F prefix URL prefix for files (default: file:///tmp/)
-l limit time limit (in seconds, or "none" or "max") for search
-L print responses in LDIFv1 format
-LL print responses in LDIF format without comments
-LLL print responses in LDIF format without comments
and version
-s scope one of base, one, sub or children (search scope)
-S attr sort the results by attribute `attr'
-t write binary values to files in temporary directory
-tt write all values to files in temporary directory
-T path write files to directory specified by path (default: /tmp)
-u include User Friendly entry names in the output
-z limit size limit (in entries, or "none" or "max") for search
Common options:
-c continuous operation mode (do not stop on errors)
-C chase referrals (anonymously)
-d level set LDAP debugging level to `level'
-D binddn bind DN
-e [!][=] general extensions (! indicates criticality)
[!]assert= (an RFC 2254 Filter)
[!]authzid= ("dn:" or "u:")
[!]manageDSAit
[!]noop
ppolicy
[!]postread[=] (a comma-separated attribute list)
[!]preread[=] (a comma-separated attribute list)
abandon, cancel (SIGINT sends abandon/cancel; not really controls)
-f file read operations from `file'
-h host LDAP server
-H URI LDAP Uniform Resource Indentifier(s)
-I use SASL Interactive mode
-k use Kerberos authentication
-K like -k, but do only step 1 of the Kerberos bind
-M enable Manage DSA IT control (-MM to make critical)
-n show what would be done but don't actually do it
-O props SASL security properties
-p port port on LDAP server
-P version protocol version (default: 3)
-Q use SASL Quiet mode
-R realm SASL realm
-U authcid SASL authentication identity
-v run in verbose mode (diagnostics to standard output)
-V print version info (-VV only)
-w passwd bind password (for simple authentication)
-W prompt for bind password
-x Simple authentication
-X authzid SASL authorization identity ("dn:" or "u:")
-y file Read password from file
-Y mech SASL mechanism
-Z Start TLS request (-ZZ to require successful response)

Argument pour la command apt-get sous Ubuntu

liste des option disponibles:

update - Retrieve new lists of packages
upgrade - Perform an upgrade
install - Install new packages (pkg is libc6 not libc6.deb)
remove - Remove packages
purge - Remove and purge packages
source - Download source archives
build-dep - Configure build-dependencies for source packages
dist-upgrade - Distribution upgrade, see apt-get(8)
dselect-upgrade - Follow dselect selections
clean - Erase downloaded archive files
autoclean - Erase old downloaded archive files
check - Verify that there are no broken dependencies

Plusieures Instances Yahoo Messenger sous Windows

Il vous deja arrivé de vouloir vous logger avec deux ID Yahoo Différents sur la meme Machine,
alors il vous suffit de rajouter une clef dans la base de registre :

1. Cliquez sur Demarrer > Exécuter and tapez 'regedit' puis entrer (OUverture de la base de registre)
2. Naviguer dans HKEY_CURRENT_USER\Software\Yahoo\Pager\Test
3. Cliquez droit afin de créer une nouvelle clef en DWORD, appelez la 'Plural'
4. UNe fois crée, double cliquez sur celle ci afin de changer la valeure a '1'

Maintenant, vous pouvez ouvrir plusieures session Yahoo, en utilisant des ID différents.

Shell Script pour verifier la presence d'un processus -> action

[more]

#/usr/bin
# Verifie si mon porcess est en memoire
if ps -ef | grep -q [M]on_process
then
echo "$(date) - mon process est deja en memoire" >> /tmp/mon_process.log
exit
else
# lancer mon process si pas present en memoire
echo "$(date) - mon processus demarre" >> /tmp/mon_process.log
ma commande (/opt/...)
fi

Optimization d'un Server Domino 6/8.x

Configuring server tasks

Each task increases the server's load and can adversely affect its performance. Minimizing the number of server tasks that are run by the server, the frequency at which they run, and the time in which they run will enable you to increase the performance of the server. For example, these are the server task entries in notes.ini:

ServerTasks=Update,Replica,Router,AMgr,AdminP,CalConn,Sched
ServerTasksAt1=Catalog,Design
ServerTasksAt2=UpdAll
ServerTasksAt3=Object Info -Full
ServerTasksAt5=Statlog

Each of these variables control the schedule for automatic server and database maintenance tasks. The first SeverTasks line denotes the services that are run when Domino starts while the other lines denote the scheduled server tasks. The time is entered in a 24-hour format, where 0 is 12:00 a.m. and 23 is 11:00 p.m. In the example above, Catalog and Design tasks would initiate at 1:00 a.m., and the Statlog task would initiate at 5:00 a.m.

You can significantly improve performance by removing tasks that are not appropriate to the server. Consider the following suggestions to increase performance related to Lotus Domino server tasks.

* These tasks should be turned off when they are not in use:

Scheduling: Turn off this task if you are not using the server for scheduling and calendaring.

AMgr: Turn off this task if you are not using the server to run scheduled agents. Remember, this function is not required for WebQuery Agents.

Collector, Reporter: Turn off this task if you are not using the server to automatically track server statistics on a regular basis. You can collect them on demand.
* Remove the Replicator (Replica) and Router tasks.

Both of these tasks can be removed if they are not being used on the server, because each of these tasks take up a fair amount of server resources when loaded. For example, if you have only one Lotus Domino server in your organization that is used for both applications and mail routing, you might not need the Replicator task, because you do not have any other servers from which to replicate (and because clients will be replicating from the Lotus Domino server, not vice versa).
* Carefully choose the times when server tasks are run.

Daily server tasks should not be run when other server tasks are running or at times when there are a lot of users using the Lotus Domino server. This allows the maximum amount of server resources to be available for each server task that is currently executing and for user sessions. Examples of such server tasks are Design, Catalog, Statlog, and customized Notes API programs that need to be run only once a day.

The entries in ServerTasks have the following uses:

ADMINP: The major Domino scheduler job running batch-like updates
AMGR: Domino Agent Manager; takes care of predefined agents
CALCONN: Connects the Domino calendar to other types of calendars
EVENT: Domino Event Handler
REPLICA: Domino database Replicator task
REPORT: Domino Report Generator (adding data to STATREP.NSF)
ROUTER: Domino Mail Routing task
SCHED: Domino Scheduler task
SERVER: The main Domino Server task
UPDATE: Updates the database indexes and views

Tip: A very obvious but important lesson about server tasks and functions is that if your organizational requirements have no need for a particular function, do not run it on your server!

Domino database indexing: controlling the Update task

The Update task is designed to run in the background and is intended to improve response time and performance by ensuring that when a user opens a database view, the user does not have to wait for it to be indexed.

Note: Do not remove the Update task from a server. If you do so, the Public Address Book will not be updated.

To improve view-indexing performance, you can run multiple Update tasks if your server has adequate CPU power. Doing this can affect server performance and is recommended primarily for multiprocessor machines. On a server with multiple processors, enable a maximum of one Update task per processor

This is done within the notes.ini file by adding the line:

Updaters = [number of processors]

Network performance (compression)

Network compression is an important performance feature offered in Lotus Notes/Domino 6. When you enable network compression, data is automatically compressed before it is sent over the network. This improves network performance, especially over slower line speeds.

Notes/Domino 6 network compression offers a number of immediate benefits. For example, by reducing the amount of data being transmitted, you can improve the performance of your routing and replicating hub servers, especially if they are currently laboring under heavy workloads. In addition, you can enable it by default, so all your users can take advantage of this functionality without having to select it themselves. Because network compression is a standard, out-of-the-box feature, it does not require any additional code, which helps simplify administration and requires fewer CPU resources to run.

Note the following statistics about the benefits of network compression:

* A 35-52% reduction in data transferred from the server to client
* A 26% reduction in data transferred from server to server

Modify the TCPIP line in the notes.ini file to enable network compression. The last parameter denotes compression:

TCPIP = TCP,0,15,0,,12320

Setting maximum mail threads for local delivery

The MailMaxDeliveryThreads setting determines the maximum number of threads the router can create to perform local mail delivery. The default number is 1. Increasing this value can improve message throughput for local deliveries. The ideal number usually falls in the range of 3 to 25, depending on the number of local deliveries on your Lotus Domino mail server.

MailMaxDeliveryThreads = [number]

Setting maximum mail transfer threads

The MailMaxThreads setting determines the maximum number of concurrent processes that the mail router can create to perform it's mail transfers efficiently. The default setting is one thread per server port.

MailMaxThreads = [number]

Disabling per-user message caching by the IMAP task

This setting disables per-user message caching by the IMAP task. It can improve the capacity of a server by reducing memory consumption. However, response time for some user operations might be slower. If this setting is omitted, IMAP per-user message caching will be enabled.

To disable per-user message caching by the IMAP task, set the following value to 1:

NoMsgCache = [0 or 1]

Using Lotus Domino 6.5 database format

Databases that you create in Lotus Domino 6.5 perform considerably better than databases created in previous releases: Database operations require less I/O and fewer CPU resources, view rebuilding and updating is quicker, and memory and disk space allocation is improved.

Because of these performance improvements, limiting the size of the databases to improve database performance is less important than in past releases. The maximum database size for Lotus Domino 6.5 format databases is 64 GB.

Defining the number of databases cached simultaneously

If your server has sufficient memory, you can improve the performance of the server by increasing the number of databases that Lotus Domino can cache in memory at one time. To do so, use the NSF_DbCache_Maxentries statement in the NOTES.INI file. The default value is 25 or the NSF_Buffer_Pool_Size divided by 300 KB, whichever value is greater. The maximum number of databases that can be cached in memory is approximately 10,000. For short intervals, Lotus Domino will store up to 1.5 times the number entered for this variable.

Monitor the Database.DbCache.Hits statistic on your server. This indicates the number of times a database open request was satisfied by finding the database in cache. A high value indicates database cache is working effectively. If the ratio of Database.DbCache.Hits to InitialDbOpen is low, you might consider increasing NSF_DbCache_Maxentries.

To set the number of databases that a server can hold in its database cache at one time, set the NOTES.INI value as follows:

NSF_DbCache_Maxentries = [number]

In special circumstances, you might also want to disable the database caching. The database cache is enabled by default. To disable database caching, enter the following syntax on the Domino console:

Dbcache disable

The database cache keeps databases open. Use this command to disable the database cache when you need exclusive access to a file that might be in the database cache. For example, to run an application such as a virus checker or backup software, disable the cache. To re-enable the database cache, restart the server.

Optimizing database index update

In general, the fewer view indexes that the Indexer server task must update, the fewer server resources are used by this task. You can use the NOTES.INI variable Default_Index_Lifetime_Days to minimize the amount of effort required by the Indexer task when updating view indexes. The Default_Index_Lifetime_Days variable controls how long a view index is kept in a database before it is deleted due to non-use:

Default_Index_Lifetime_Days = [number of days]

Full-text indexes

Disable the updating of full-text indexes on a server if you do not have any full-text indexed databases on your server (and do not intend to have any). The NOTES.INI variable Update_No_Fulltext can be used to disable all full-text index updating on the server. You might want to use this variable to disable the updating of full-text indexes if, for example, you do not want users to create full-text indexes on their mail files on a mail server in order to save disk space on that server and to save the Indexer task the time and resources of updating these full-text indexes. This is a very good setting for mail and replication hub servers, which in most circumstances do not have any user connections. The full-text index variable is:

Update_No_Fulltext = [0 or 1]

Setting this value to 0 causes full-text indexes to be updated each time the Update task (a server command task) is executed, and setting the value to 1 disables all full-text indexing.

Maximum sessions

When a new user attempts to log on, if the current number of sessions is greater than the value of Server_MaxSessions (in the NOTES.INI file), the Lotus Domino server closes the least recently used session. In order for a session to be considered for closing, it must have been inactive for at least one minute. For example, if this parameter is set to 100, and the 101st person tries to access the Lotus Domino server, the Lotus Domino server drops the least-used session from the server in favor of this new session.

Note: Reducing the Server_MaxSessions value to a specific number will not prevent the server from allowing more than that number of concurrent active users on the server, but will drop the sessions soon after they become inactive. This frees up resources. Conversely, Domino will not close any session that has been idle for less than one minute regardless of the demand on the server.

Controlling minimum mail poll time

You can control the minimum allowable time in which Lotus Notes clients can poll for new mail. It is possible that your Lotus Domino server resources are being overtaxed by being constantly bombarded by requests for new mail from the Notes client machines if users have changed their default new mail notification check time from 15 minutes to a smaller number such as 2 or 5.

You can control the minimum frequency of these requests from the server by using the MinNewMailPoll NOTES.INI variable. This variable determines the minimum allowable checking time from clients regardless of the value specified on the client machines. No default is set during server setup. The syntax of this variable is as follows:

MinNewMailPoll = [minutes]

Setting up multiple replication tasks

You can improve server replication performance by running multiple replicator tasks simultaneously. By default, only one replicator task is executed. With a single replicator task running, if you want to replicate with multiple servers at the same time, the first replication must complete before the next one can start. Set the number of replicators by adding the following entry in the NOTES.INI file, where the value is the number of replicators:

Replicators = [number]

All other factors aside, it is recommend that you set the number of replicator tasks equal to the number of spoke servers with which the hub replicates. However, you should not exceed 20 replicators to avoid putting too much load on the server. If the server you intended to replicate is not a hub server, the recommended number of replicators should equal the number of processors on the server.

http://www.redbooks.ibm.com/abstracts/t ... .html?Open

Erreur :"Please edit your shell's DISPLAY environment variable..." launching Domino local server setup on Unix or Linux

Lors d'un démarrage d'un Serveur Domino, ce typ e de message apparait:

Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified
Please edit your shell's DISPLAY environment variable to reflect an unlocked terminal that you would like to launch the Domino Setup Program on.

Afin de résoudre ce souci, les étape a suivre:

1. Ouvrez une session Terminal

2. Loggez vous en root

3. Ajouter le compte 'Domino' dans ACL du X Server

# xhost +local:username

Exemple:

# xhost +local:notes

Ci joint le type réponse une fois la commande effectuée:

non-network local connections being added to access control list

4. Re-démarrez le Server avec le compte Domino:
ex:
$/local/notes/opt/Lotus/bin/server

basculer / bouger des fichiers contenant une valeur depuis et vers un autre dossier (/tmp/)

for i in `grep -irl "value" *`; do mv $i ./tmp/;done;

Arguments (switches) Notes.ini sous Domino Serveur (6.5.x / 8.x)

J'ai volontairement laissé les informations suivantes en Anglais afin que celles ci soient comprises
de tous. :)

Mail and router variables
There are a number of new variables designed to handle new mail and router functionality in Domino 6, including SMTP mail.

MailCompactHour=
This variable specifies the time at which the router should perform mailbox compaction. The time is based on a 24-hour clock. For example, MailCompactHour=20 will initiate compaction at or around 8 PM.

RouterEnableMailByDest=
This variable generates verbose mail routing statistics per destination. If you set RouterEnableMailByDest=1, the router maintains statistics for each mail routing destination, which include the last successful/unsuccessful transfer time, total number of messages routed, and the total number of failures. These statistics may be useful when attempting to troubleshoot routing-related problems.

SMTPExpandDNSBLStats=
This variable, when set to 1, causes the SMTP server to generate host-specific DNS Blacklist Filter statistics, which indicate the total number of hits per DNSBL site, per connecting host's IP address. If you set SMTPExpandDNSBLStats=0 (or omit it from Notes.ini), the SMTP task maintains statistics that track the total number of connecting hosts that were found on the combined DNSBL of all sites as well as how many were found on the DNSBL of each configured site.

SMTPNoVersionInRcvdHdr=
This variable prevents Domino server product information from being disclosed in SMTP Received headers.

Console logging variables
In Notes/Domino 6, we've added the ability to allow console logging to be dynamically started or stopped. To help you work with this feature, we've included the following Notes.ini variables.

Console_Log_Enabled=
This variable specifies whether or not to enable logging to the Console Log file (console.log, by default). Console_Log_Enabled=1 causes the router to maintain statistics for each mail routing destination, which include the last successful/unsuccessful transfer time, total number of messages routed, and the total number of failures. A setting of 0 results in no destination-based statistics generated by the router.

Console_Loglevel=
This variable controls the level of information displayed on the status bar when you trace a connection. The following values are possible:
0 - No information is displayed.
1 - Only errors are displayed.
2 - Summary progress information is displayed.
3 - Detailed progress information is displayed.
4 - Full trace information is displayed.

Console_Log_Max_Kbytes=
This variable specifies the maximum size for the Console Log file. If the Console_Log_Max_Kbytes setting is not present or is set to 0, then the file size is unlimited. When the maximum file size is reached, new logging output starts to overwrite existing logging output at the beginning of the file.

Debug_Outfile=
This variable specifies the file name for the Console Log file.

LogFile_Dir=
This variable specifies the directory for the Console Log file.

HTTP-related variables
The following variables give you more control over how the Domino HTTP service (also known as the Domino Web server) runs.

HTTPEnableConnectorHeaders=
This variable enables the Domino HTTP service to process special headers that are added to requests by a WebSphere 4.0.3 plug-in installed on a foreign Web server. When the plug-in relays an HTTP request to the Domino back-end server, the plug-in adds headers that include information about the front-end server's configuration and user authentication status. HTTPEnableConnectorHeaders=1 instructs the Domino HTTP task to process the special headers; a setting of 0 results in these headers not being processed.

HTTPLogUnauthorized=
This variable, when set to 1, instructs the HTTP service to log Error 401 instances to the server console. These instances are generated in two cases: A user attempts to access a resource but is not authorized for it or a user has failed to authenticate. If HTTPLogUnauthorized=0, Error 401 instances are not logged to the server console (although they are logged to the Web Server logs, regardless of whether this variable is enabled or disabled).

HTTP_Pwd_Change_Cache_Hours=
This variable caches Change Password requests, which allows both the new password and the old password to work on the HTTP service for the specified number of hours.

Java-related variables
Domino 6 Notes.ini variables include a group of settings that affect how Java programs run on your server. Here are some of these Java-related variables:

JavaEnableJIT=
This variable enables or disables the default Java Just-in-Time compiler (JIT), if one is provided. JavaEnableJIT=1 allows normal loading of the default JIT; 0 disables the JIT.

JavaJITName=
This variable enables the specified JIT. Use the JavaJITName setting to load a JIT other than the default JIT (if one exists).

JavaMaxHeapSize=
This variable specifies the maximum size the Java heap can reach. You can specify the number of bytes directly or use the suffix MB to indicate megabytes. For example, specifying 64 MB is the same as specifying 67108864.

JavaMinHeapSize=
This variable specifies the initial size of the Java heap at Java Virtual Machine (JVM) startup. As with JavaMaxHealSize, you can specify the number of bytes directly or use the suffix MB to indicate megabytes.

JavaNoAsyncGC=
This variable prevents or allows the JVM from running the garbage collection (GC) mechanism in a separate background thread. Specify JavaNoAsyncGC=1 to prevent the GC from running in the background. (This can help you debug internal JVM problems.)

JavaNoClassGC=
This variable, when set to 1, prevents the GC mechanism of classes, which protects static fields.

JavaStackSize=
This variable specifies the size of each Java thread's execution stack.

JavaUserClasses=
This variable allows code-sharing across agents and applets.The value is a list of directories, JAR files, or ZIP files that are added to the Java Virtual Machine's internal classpath so that classes can be found via the system loader (rather than via attachments to the agent or applet). Use a semicolon to separate list items for Win32 and OS/2 systems, and use a colon to separate list items for UNIX systems. For example, a valid list for Win32 is:

c:classes;d:appxyzstuff.jar

JavaVerbose=
This variable enables or disables the verbose setting of the JVM, which causes the JVM to issue many messages while it runs. Specify JavaVerbose=1 to enable verbose JVM, which can help troubleshoot runtime problems.

JavaVerboseGC=
This variable enables or disables the verbose setting of the GC mechanism in JVM, which causes the JVM to issue many messages about memory usage as GC runs. JavaVerboseGC=1 enables this setting, which can help you troubleshoot problems.

LDAP schema daemon variables
When you run the LDAP service on your Domino server, it spawns a schema daemon that runs periodically. This daemon ensures that each LDAP service running in the domain uses the same up-to-date and consistent schema. The daemon runs when the LDAP service first starts, and then every 15 minutes afterward by default. The following four variables let you determine how the LDAP schema daemon runs.

LDAPDebug=Value
Enables extra logging for the LDAP task in Domino, with a binary debug routine, Use in conjunction with Debug_Outfile.

1 = Show Query Information
2 = Show Result Information
3 = 1 & 2
4 = Authentification Information
5 = 1 & 4
6 = 2 & 4
7 = All of the above
8 = Even more verbose information (no details known)
9 - 15 = Summaries of the above

Schema_Daemon_Breaktime=
This variable specifies how often (in seconds) the daemon checks to see if it should shut down because its parent LDAP task is shutting down.

Schema_Daemon_Idletime=
This variable specifies how long (in minutes) the daemon remains idle after it has completed its tasks. After the daemon has been idle for the specified interval, it begins its tasks again.

Schema_Daemon_Reloadtime=
This variable specifies how often (in hours) the daemon adds schema elements for new or changed Domino Directory forms and fields to its in-memory schema.

Schema_Daemon_Resynctime=
This variable specifies how often (in hours) the daemon updates the schema published in the Domino LDAP Schema database with a newer in-memory schema.

In addition, you can disable the LDAP service itself by setting DisableLDAPOnAdmin=1. This prevents the LDAP service from running on the administration server of a domaon's Domino Directory.

Other variables of interest
This section presents a sample of other Domino 6 variables you may encounter.

Debug_SSO_Trace_Level=
This variable obtains detailed debugging information for protocols that support single sign-on, such as HTTP and DIIOP. Debug_SSO_Trace_Level=1 prints debugging information as tokens are generated and verified, as well as configuration details. Debug_SSO_Trace_Level=2 prints detailed memory dumps as tokens are generated and verified, in addition to the preceding information.

DominoR5IntlURLDecoding=
This variable enables or disables the decoding of international URL strings using a proprietary encoding scheme. By default, Domino 6 encodes URLs according to the IRI (International Resource Identifiers) standard and does not decode URL strings encoded by Domino 5. DominoR5IntlURLDecoding=1 enables Domino 5 international URL decoding; a setting of 0 disables it.

Enable_ACL_Files=
This variable enables or disables ACL file checking on a server. ACL files are an option for protecting server directories and contain the names of users authorized to access those directories. For non-xSP configurations, this variable is set to 0 (disabled) by default. For xSP configurations, it is set to 1 (enabled).

FT_Max_Search_Results=
Specifies the maximum number of results that can be retrieved at one time on a database without an index. The value can be any number up to 2,147,483,647.

***somethingsomewhere.net***