922928bbec
In presence of gnss-monitor ptp-instance monitoring a device (/dev/ttyACM0),
gpspipe@.service connects to gpsd daemon and provides NMEA output in
/dev/ttyACM0.pty file. When gpsd.service daemon restarted, gpspipe@.service
exits with success return-code and not restarted, causing the output
file unavailable.
This commit fixes the issue by restarting the gpspipe@.service always,
whether the return-code be success or failure.
Test Plan:
PASS: Deploy gnss-monitor ptp-instance with device /dev/ttyACM0
- /dev/ttyACM0.pty file is accessible
- systemctl restart gpsd.service
/dev/ttyACM0.pty file accessible.
gpspipe@-dev-ttyACM0.service is running (get restarted)
PASS: stop gpsd.service, gpspipe service automatically restarts
gpsd.service too, and /dev/ttyACM0.pty file accessible
PASS: stop gpsd.socket, gpspipe service keep restarting, until
gpsd.socket started again.
PASS: Test same as above for two devices, after following:
system ptp-instance-parameter-delete gnss0 'devices=/dev/ttyACM0'
system ptp-instance-parameter-add gnss0 'devices=/dev/ttyACM0 /dev/ttyACM1'
system ptp-instance-apply
Closes-bug: 2126965
Change-Id: I445f99e548b96b0bbee4d35dfa31e2c4e3c768ca
Signed-off-by: Tara Nath Subedi <tara.subedi@windriver.com>
stx-puppet
The starlingx/stx-puppet repository handles the Puppet service1.
The Puppet service runs during bootstrap, and at every reboot, to provide a consistent configuration across the StarlingX system nodes.
This repository is not intended to be developed standalone, but rather as part of the StarlingX Source System, which is defined by the StarlingX manifest2.