On 07/02/2014 12:49 PM, Petr Viktorin wrote:
> On 07/02/2014 08:14 AM, Jan Cholasta wrote:
>> On 1.7.2014 16:45, Tomas Babej wrote:
>>> Hi,
>>>
>>> The replication related attributes nsds5replicalastupdatestart and
>>> nsds5replicalastupdateend have special behaviour implemented in 389,
>>> as foll
On 07/02/2014 08:14 AM, Jan Cholasta wrote:
> On 1.7.2014 16:45, Tomas Babej wrote:
>> Hi,
>>
>> The replication related attributes nsds5replicalastupdatestart and
>> nsds5replicalastupdateend have special behaviour implemented in 389,
>> as follows:
>>
>> In case they are explicitly requested for
On 07/02/2014 08:14 AM, Jan Cholasta wrote:
On 1.7.2014 16:45, Tomas Babej wrote:
Hi,
The replication related attributes nsds5replicalastupdatestart and
nsds5replicalastupdateend have special behaviour implemented in 389,
as follows:
In case they are explicitly requested for and not set, 0 is
On 1.7.2014 16:45, Tomas Babej wrote:
Hi,
The replication related attributes nsds5replicalastupdatestart and
nsds5replicalastupdateend have special behaviour implemented in 389,
as follows:
In case they are explicitly requested for and not set, 0 is returned.
However, 0 is not a valid value fo
Hi,
The replication related attributes nsds5replicalastupdatestart and
nsds5replicalastupdateend have special behaviour implemented in 389,
as follows:
In case they are explicitly requested for and not set, 0 is returned.
However, 0 is not a valid value for LDAP Generalized time. Thus
we need to
