Hi Ken,

I found that brutality worked best: “kill -9 xxxx” where xxxx is the PID of EzStream. Being gentle with it got me nowhere – so a larger hammer was required J

It takes a few moments for the app to restart, but it always does.

David

From: Ken [mailto:ke2n@cs.com]
Sent: 05 October 2013 19:20
To: 'David Osborn'; app_rpt-users@ohnosec.org
Subject: RE: [App_rpt-users] streaming restart

Ok – not sure if I am really killing it

It acts like the energizer bunny

[root@atom2 ~]# pidof ezstream

2666

[root@atom2 ~]# kill 2666

[root@atom2 ~]# pidof ezstream

2666

[root@atom2 ~]# killall ezstream

[root@atom2 ~]# pidof ezstream

2666

[root@atom2 ~]#

Next time I detect that the plug has been pulled, I will try this. Thanks. If it does the trick I may just put this in crontab and do it every so often.

73

Ken

From: David Osborn [mailto:david.osborn@manx.net]
Sent: Saturday, October 05, 2013 1:01 PM
To: app_rpt-users@ohnosec.org
Cc: ke2n@cs.com
Subject: re: [App_rpt-users] streaming restart

Hi Ken,

I occasionally have issues with EZStream taking-up 100% CPU time – I just kill it and it gets re-started by the app_rpt outstream command. No need to re-boot.

Try that and see how you fare.

David