Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+SIP\s+Persistence\s+Engine\s+\/\s+schedulers\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[lvs\-users\]\s+SIP\s+Persistence\s+Engine\s+\/\s+schedulers\s*$/: 2 ]

Total 2 documents matching your query.

1. Re: [lvs-users] SIP Persistence Engine / schedulers (score: 1): Author: Simon Horman <horms@xxxxxxxxxxxx>; Date: Wed, 9 Jul 2014 10:06:48 +0200; I am not aware of a current solution to that problem. _______________________________________________ Please read the documentation before posting - it's available at: http://www.linuxvirtualserver.o; /html/lvs-users/2014-07/msg00009.html (9,649 bytes)
2. [lvs-users] SIP Persistence Engine / schedulers (score: 1): Author: Michael Klebanow <michaelkleb123@xxxxxxxxx>; Date: Tue, 8 Jul 2014 11:14:06 -0400; It has been documented a few years ago, that the SIP Persistence Engine was designed to work with one-packet scheduling. The system I'm working with has VERY few clients (something like 3 or 4), with; /html/lvs-users/2014-07/msg00006.html (8,601 bytes)

Current List: 1 - 2
Page: [1]