63739c5c25
Mender is a service explicitly written for systemd and so it doesn't fork on background, doesn't redirect outputs and doesn't create a pid file by itself. To make the service running correctly is therefore necessary to use the -m switch of start-stop-daemon to create the pid file and -b option to send the process to background. Logging is preserved because the service will log anyway on syslog. Signed-off-by: Angelo Compagnucci <angelo@amarulasolutions.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> |
||
|---|---|---|
| .. | ||
| artifact_info | ||
| Config.in | ||
| device_type | ||
| mender.conf | ||
| mender.hash | ||
| mender.mk | ||
| mender.service | ||
| readme.txt | ||
| S42mender | ||
| server.crt | ||
=== Notes on using Mender on Buildroot ====================================== Default configurations files ---------------------------- Buildroot comes with a default artifact_info and device_type configuration files in /etc/mender. They contain default values, and thus they should be overridden on a production system. The simplest way to do it is to change these files in an overlay or in a post build script. Configuring mender with certificates ------------------------------------ Mender uses TLS to communicate with the management server, and if you use a CA-signed certificate on the server, you should select the ca-certificates package otherwise it doesn't work.