-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 El 2014-08-05 a las 15:50 +0200, Bernhard Voelker escribió:
On 08/05/2014 03:37 PM, Carlos E. R. wrote:
El 2014-08-05 a las 15:33 +0200, Carlos E. R. escribió:
It is getting signal 15. Trapping it works! :-)
waiting (9)... waiting (12)... Terminated Got signal 15 in nm-mine-hook waiting (15)... waiting (18)... waiting (21)... Going to sync time: 5 Aug 15:28:22 sntp[30794]: Started sntp 2014-08-05 15:28:22.835483 (-0100) -0.115987 +/- 0.059280 secs 2014-08-05 15:28:23.108107 (-0100) -0.026680 +/- 0.045334 secs 2014-08-05 15:28:23.431295 (-0100) +0.009879 +/- 0.029022 secs Time synchronized with 0.pool.ntp.org Time should be synced now.
Cool, thanks for the update.
Have to update again. The code I have now is: echo "waiting..." ; sleep 5 echo "Going to sync time:" $LOGGER -t $TAG -p $FACILIDAD "Going to sync time now." /usr/sbin/rcntp ntptimeset $LOGGER -t $TAG -p $FACILIDAD "Time should be synced now." echo "Time should be synced now." And the log I got a minute ago was this: 2014-08-06T18:08:21,470279636+0200 - Going up Got enp0s29f7u1, IPv4.0 (host and GW): '192.168.42.154/24 192.168.42.129', IPv4.1: '' Cambiando la IP en /etc/hosts a 192.168.42.154 - Samsung android usb tether. waiting... Going to sync time: 6 Aug 18:08:26 sntp[24268]: Started sntp Got and ignored signal SIGTERM in nm-mine-hook Time should be synced now. I read it that the script survived the kill attempt, but sntp did not. I guess I have to wait at least 15 seconds, so that netowork manager tries to kill its children, and only then I can call ntp in safety. - -- Cheers Carlos E. R. (from 13.1 x86_64 "Bottle" (Minas Tirith)) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iF4EAREIAAYFAlPiVRAACgkQja8UbcUWM1zPCwD9EbEql/lSO3ral1fYS43Zg9oJ 5SqcAbqsm4i/hf4wBBMA/1tA5I2EryiwT34qUI7ozASWetN306mZIWAAGL7IAc6h =qMob -----END PGP SIGNATURE-----