I have a cronjob that periodically runs openserctl to gather stats out of openser. I've noticed that in my fifo directory, there are anywhere from 1.5 ~ 3k openser_receiver files laying around.
Is there something screwy with mi_fifo in v1.2.2-tls that's preventing it from cleaning up after itself?
--Chris
Actually, I've found my problem, looks like openserctl leaves these behind when openser isn't running. Killing openserctl leaves the fifo behind.
--Chris
On Wed, 7 Nov 2007, Chris Heiser wrote:
I have a cronjob that periodically runs openserctl to gather stats out of openser. I've noticed that in my fifo directory, there are anywhere from 1.5 ~ 3k openser_receiver files laying around.
Is there something screwy with mi_fifo in v1.2.2-tls that's preventing it from cleaning up after itself?
--Chris
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
Hi Chris.
yes, you got it right - the reply fifo file is managed (created and deleted) by the client part and not by openser (mi_fifo module). So, the client needs to take care and remove it.
regards, bogdan
Chris Heiser wrote:
Actually, I've found my problem, looks like openserctl leaves these behind when openser isn't running. Killing openserctl leaves the fifo behind.
--Chris
On Wed, 7 Nov 2007, Chris Heiser wrote:
I have a cronjob that periodically runs openserctl to gather stats out of openser. I've noticed that in my fifo directory, there are anywhere from 1.5 ~ 3k openser_receiver files laying around.
Is there something screwy with mi_fifo in v1.2.2-tls that's preventing it from cleaning up after itself?
--Chris
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users
Users mailing list Users@lists.openser.org http://lists.openser.org/cgi-bin/mailman/listinfo/users