Epoptes

Make socat timeout configurable in /etc/default/epoptes-client

Bug #1517574 reported by Laércio de Sousa
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Epoptes
Expired
Undecided
Unassigned

Bug Description

Now that a socat timeout was introduced in revision 458, I would like to propose a little suggestion: make it configurable in /etc/default/epoptes-client. Some users may want to give it a greater or smaller value, depending on their network characteristics.

See original description
Laércio de Sousa (lbssousa)
description: updated
Revision history for this message
Alkis Georgopoulos (alkisg) wrote :

Hi Laércio, in which case is this needed?
Maybe we can find a timeout that will work fine in all networks?

20 was selected because 10 is the ping timeout of the epoptes service.

Alkis Georgopoulos (alkisg)
Changed in epoptes:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Epoptes because there has been no activity for 60 days.]

Changed in epoptes:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.