18.07.2013 Views

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.1 Administration Guide - Glossary of Technical ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Additional <strong>Sidewinder</strong> <strong>G2</strong> operating characteristics<br />

For example, should someone try to attack a <strong>Sidewinder</strong> <strong>G2</strong> service<br />

(such as sendmail), causing the component to crash, the daemond<br />

process will detect the failure, immediately restart the failed<br />

component, and create a critical event audit entry (allowing the<br />

administrator to be notified and respond to the attack).<br />

daemond starts during the <strong>Sidewinder</strong> <strong>G2</strong> boot process. On start up, it<br />

reads the /etc/sidewinder/daemond.conf file to determine its<br />

configuration options. As a <strong>Sidewinder</strong> <strong>G2</strong> administrator, there are<br />

two daemond options you should be aware <strong>of</strong>: default memory size<br />

and failure mode.<br />

About the default memory size option<br />

If no memory size is specified for a service in the /etc/server.conf or<br />

/etc/sidewinder/nss.common.conf files, the default memory size option<br />

specifies the size (in MB) that daemond will give each <strong>of</strong> the services it<br />

starts. The default size is 128 MB. If there is no value present in the<br />

daemond configuration file, it will use the default value from<br />

/etc/login.conf.<br />

About the failure (safe) mode option<br />

By default, daemond will run in its normal mode (that is, failure mode<br />

is not configured and daemond will run in its normal, operational<br />

mode). This means that daemond will attempt to start all enabled<br />

components in the /etc/server.conf and<br />

/etc/sidewinder/nss.common.conf files. When failure mode is enabled<br />

in the /etc/sidewinder/daemond.conf file, and a failure event has<br />

occurred, daemond will start in failure mode (also called safe mode).<br />

This means that daemond will only start the components that are<br />

enabled for failure mode in the /etc/server.conf and<br />

/etc/sidewinder/nss.common.conf files. Components that are NOT<br />

enabled for failure mode will not be started.<br />

Introduction 1-13

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!