Domino Start Script V3.2.0

Daniel Nashed  4 November 2018 07:38:18

There wasn't a new release of my Linux/Unix Start Script for a year.
I still have many download requests but there is not much feedback or feature requests.

Most of the new functionality added is coming from my own requirements (for example to simplify operations) Or direct customer requests.
I am always trying to understand the underlying requirement and add it in a flexible way, that many admins can benefit from it.

The new version I am working on simplifies configuration with systemd. You don't have to change the rc_domino file any more.
And it comes with a simple installation script that will copy the files for you and sets the right permissions.

Sadly systemd does not allow to use variables in the way I would need it, to read configuration from a config file.
So the install script will only work for default configurations where you use the notes user and group with a single partition.
I wanted to avoid a complex configuration script that replaces variables in the start script files.

Beside that I also added a couple of commands that make your life easier. You can now list or edit all files involved including the systemd service file.

And you can also show the log of the server. That's one command that was missing for me.
Before I already added lastlog where you can show the last n log lines and redirect that for example to a grep command.
Now you can do whatever you like with the log by specifying an additional parameter behind log (without a parameter vi is used).

And last but not least I added another way to schedule compact operations.
You can now configure a one time compact for example after a maintenance boot.

See detailed feature list below for more information.
If you have other ideas and requirements that should be in the standard, let me know.

I am currently testing the new version and will update the start script page soon.


-- Daniel


V3.2.0

New Features
------------

New command 'log' -- displays the start script output log.
This command can be used with additional options like specifying the command to open the log (e.g. 'log more').
See log command description for details.

New command 'systemdcfg' to edit the systemd configuration file

New command 'compactnextstart' which allows you to configure a one time compact at next startup.
For example after an OS patch day. The new command allows you to enable/disable/display the settings.
Check the command documentation for details.

New config variables DOMINO_DOMLOG_DB_DAYS, DOMINO_DOMLOG_DB_BACKUP_DIR which can move domlog.nsf to a backup directory.
This works like the log.nsf backup/rename introduced earlier.

New config variable DOMINO_UMASK.
And also allow to set the umask when starting the server via DOMINO_UMASK.

Show the umask used in the startup log of the server (along with environment and ulimits etc).

Separate, simple script 'install_script' that will allow you to install the start script for default configurations.


Changes
-------

Start script is now prepared for systemd without changing rc_domino script (adding the service name).

Enable the configuration for systemd in the rc_domino script by default and check if systemd is used on the platform.
This allows to install it on servers with systemd or init.d without changing the rc_domino script.

Changing deployment from zip to tar format. So you can unpack the files directly on the target machine.
This also means you can run the install_script without changing the permissions.

Changed the default location for the Domino PID file for systemd from /local/notesdata/domino.pid to /tmp/domino.pid.
This allows you to change the data directory location without changing the pid file name in domino.service and config.
But this means for multiple partitions you have to change the name for each of the services.

I tried to dynamically read parameters from the config file in domino.service.
There is an EnvironmentFile= statement in systemd services to read configuration files.
But using variables does only work for parameters passed to a an ExecStart/ExecStop command but not for the name of
those scripts invoked. Also it is not directly sourcing the parameters but reading them directly.
So there seems to be no way to read the config of domino.service from the config file.
And I had to "hardcode" the filenames.

• Comments [12]