Sample scripts and configuration files for systemd, Upstart and OpenRC can be found in the contrib/init folder.
contrib/init/starwelsd.service: systemd service unit configuration contrib/init/starwelsd.openrc: OpenRC compatible SysV style init script contrib/init/starwelsd.openrcconf: OpenRC conf.d file contrib/init/starwelsd.conf: Upstart service configuration file contrib/init/starwelsd.init: CentOS compatible SysV style init script
All three Linux startup configurations assume the existence of a “starwels” user and group. They must be created before attempting to use these scripts. The OS X configuration assumes starwelsd will be set up for the current user.
At a bare minimum, starwelsd requires that the rpcpassword setting be set when running as a daemon. If the configuration file does not exist or this setting is not set, starwelsd will shutdown promptly after startup.
This password does not have to be remembered or typed as it is mostly used as a fixed token that starwelsd and client programs read from the configuration file, however it is recommended that a strong and secure password be used as this password is security critical to securing the wallet should the wallet be enabled.
If starwelsd is run with the “-server” flag (set by default), and no rpcpassword is set, it will use a special cookie file for authentication. The cookie is generated with random content when the daemon starts, and deleted when it exits. Read access to this file controls who can access it through RPC.
By default the cookie is stored in the data directory, but it’s location can be overridden with the option ‘-rpccookiefile’.
This allows for running starwelsd without having to do any manual configuration.
wallet accept relative paths which are interpreted as
relative to the data directory.
wallet only supports relative paths.
For an example configuration file that describes the configuration settings,
All three configurations assume several paths that might need to be adjusted.
/var/run/starwelsd/starwelsd.pid (OpenRC and Upstart) or
The configuration file, PID directory (if applicable) and data directory should all be owned by the starwels user and group. It is advised for security reasons to make the configuration file and data directory only readable by the starwels user and group. Access to starwels-cli and other starwelsd rpc clients can then be controlled by group membership.
3b) Mac OS X
Installing this .service file consists of just copying it to
/usr/lib/systemd/system directory, followed by the command
systemctl daemon-reload in order to update running systemd configuration.
To test, run
systemctl start starwelsd and to enable for system startup run
systemctl enable starwelsd
Rename starwelsd.openrc to starwelsd and drop it in /etc/init.d. Double
check ownership and permissions and make it executable. Test it with
/etc/init.d/starwelsd start and configure it to run on startup with
rc-update add starwelsd
4c) Upstart (for Debian/Ubuntu based distributions)
Drop starwelsd.conf in /etc/init. Test by running
service starwelsd start
it will automatically start on reboot.
NOTE: This script is incompatible with CentOS 5 and Amazon Linux 2014 as they use old versions of Upstart and do not supply the start-stop-daemon utility.
Copy starwelsd.init to /etc/init.d/starwelsd. Test by running
service starwelsd start.
Using this script, you can adjust the path and flags to the starwelsd program by setting the STARWELSD and FLAGS environment variables in the file /etc/sysconfig/starwelsd. You can also use the DAEMONOPTS environment variable here.
4e) Mac OS X
Copy org.starwels.starwelsd.plist into ~/Library/LaunchAgents. Load the launch agent by
launchctl load ~/Library/LaunchAgents/org.starwels.starwelsd.plist.
This Launch Agent will cause starwelsd to start whenever the user logs in.
NOTE: This approach is intended for those wanting to run starwelsd as the current user. You will need to modify org.starwels.starwelsd.plist if you intend to use it as a Launch Daemon with a dedicated starwels user.
Auto respawning is currently only configured for Upstart and systemd. Reasonable defaults have been chosen but YMMV.