Hi thanks Lonnie and Michael for the info.
As I don't know of any stop requirements for uniloader I was thinking of doing
the following (eventually):
- Have a queuemetrics.conf file in /mnt/kd which contains all the parameters
required for the uniloader including whether it is enabled or not
- Build a script which is included permanently in rc.elocal which reads this
config file and runs the application if enabled with the read parameters
- I will also try to monitor the application with monit which restarts it using
the above script if it crashes
How does this sound? Am I missing something?
Should I place the uniloader bin file in /usr/sbin or would I put it in
/mnt/kd/bin or somewhere else?
PS I will also be running up the unitracker which is included in the uniloader
which monitors outgoing calls as well!
Thanks so much.
Regards
Michael Knill
On 24/4/18, 10:39 pm, "Lonnie Abelbeck" <li...@lonnie.abelbeck.com> wrote:
On Apr 24, 2018, at 2:16 AM, Michael Keuter <li...@mksolutions.info> wrote:
>
>> Am 24.04.2018 um 04:13 schrieb Michael Knill
<michael.kn...@ipcsolutions.com.au>:
>>
>> 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
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Astlinux-users mailing list
Astlinux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
pay...@krisk.org.
