From: Lonnie A. <li...@lo...> - 2018-04-24 12:39:24
|
On Apr 24, 2018, at 2:16 AM, Michael Keuter <li...@mk...> wrote: > >> Am 24.04.2018 um 04:13 schrieb Michael Knill <mic...@ip...>: >> >> Hi All >> >> I am now currently testing QueueMetrics V17 with the uniloader application and it does appear to be working. >> More testing is required but I was just wondering where I should be putting this file, how to start it on bootup and how to restart it if it crashes. >> >> The command to load is recommended as (and I used): >> nohup nice ./uniloader -s /var/log/asterisk/queue_log upload --uri "mysql:tcp([qmserver ip address]:3306)/queuemetrics?allowOldPasswords=1" --login [loginname] --pass [password]e --token P001 >> /var/log/uniloader.log & >> >> Thanks. I will let you know how I go. > > I would put the above command into its own script (e.g. in /mnt/kd/bin/) and then start it from "/mnt/kd/rc.local", which runs at the end of the boot process. > Maybe you can track it then from Monit. > > If you need to do something on reboot/shutdown, you could use "/mnt/kd/rc.local.stop" as well. Totally agree with Michael. Model your /mnt/kd/bin/ script after a simple /etc/init.d/ script like /etc/init.d/acpid and call it as Michael suggests from /mnt/kd/rc.local and /mnt/kd/rc.local.stop. Lonnie |