On Wed, 14 Jan 2015 18:38, jdd <jdd@...> wrote:
Le 14/01/2015 18:16, Roger Oberholtzer a écrit :
jdd: gpsd IS the application. It runs all the time providing time to NTP so that the system can be a stratum 1 time source. It is not started by an application. It should always be running.
then you need only to start gpsd? why not use boot.local?
I had problem, long time ago with I don't remember what application stating too fast. at the moment boot.local was starting too early in the process.
I simply added a wait in the script, as this computer was almost never stopped I could wait a minute.
writing a stystemd unit may be more elegant, there are many tutorials on the web, but is it necessary?
https://wiki.archlinux.org/index.php/systemd#Writing_unit_files
Hmm, is ntp started still via a sysV init file (/etc/init.d/ntp) ? If yes, build a gpsd init file, and add it to the Init-Info-Block [code] # Required-Start: [...some other stuff...] gpsd [/code] a group of following calls to systemctl: systemctl daemon-reload systemctl disable ntp systemctl enable gpsd systemctl enable ntp (to get systemd up to speed about the new 'requirement') followed by: systemctl restart ntp this should pull up gpsd and then start ntp. If ntp already uses a systemd - service file (/usr/lib/systemd/system/ntp.service) add a line with the needed info into this file: [code] Requires=gpsd [/code] or a line with "Wants=gpsd" please read "man 5 systemd.unit" carefully about what to prefer. Afterwards its the same 4 systemctl calls from above to make the change known and to be able to restart ntp successfully afterwards. make sure that the init file of gpsd checks that a valid config exists. Just my 2 ct. - Yamaban. -- Nothing good was ever easy to get, only easy to loose.