db2index, db2ldif, ldif2db should set non 0 exit status if buffer size limit reached.

[389-ds-bot]

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48744

• Created at 2016-02-24 06:26:08 by firstyear (@Firstyear)
• Closed at 2018-06-06 22:45:47 as worksforme
• Assigned to mreynolds (@mreynolds389)

---

At the moment, if entries are skiped due to the fifo.bsize being exceeded our tools still return an exit status of 0.

With the new dynamic allocation it should be rare, if ever that an import / index task fails due to buffer size allocations.

In the case it does happen, a skipped entry is a bad situation. A skipped entry during indexing, means the entry can't be searched for. A skipped entry in an import means the entry no longer exists.

As a result, our tasks in the case of an entry being skipped, should set a non-0 return code.

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2016-05-13 02:16:20

Per triage, push the target milestone to 1.3.6.

[389-ds-bot]

Comment from nhosoi (@nhosoi) at 2017-02-11 22:59:47

Metadata Update from @nhosoi:

• Issue assigned to nhosoi
• Issue set to the milestone: 1.3.6.0

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2017-05-08 22:22:01

Metadata Update from @mreynolds389:

• Issue close_status updated to: None
• Issue set to the milestone: 1.3.7 backlog (was: 1.3.6.0)

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2017-07-19 21:33:10

Metadata Update from @mreynolds389:

• Issue assigned to mreynolds389 (was: nhosoi)

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2017-07-20 00:51:43

I think we can close this as I eliminated the fault. the fife buffer dynamically expands during the operation rather than returning an error.

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2018-06-06 22:45:49

Metadata Update from @mreynolds389:

• Custom field reviewstatus adjusted to None
• Issue close_status updated to: worksforme
• Issue status updated to: Closed (was: Open)