Jake Hageman

I'm not quite following. The initiate should only happen if the polling directory isn't busy: https://github.com/nasa/CF/blob/80538827ad62f4a12c91259c98001cfbadd47a87/fsw/src/cf_cfdp.c#L1584-L1596 And busy is only set to zero when the directory has been closed and...

Tried to recreate using the main branch and I see a successful close for every open. Any chance there's something else using up the FDs?

@dmknutsen @chillfig - we may need this for a project, consider reopening? At minimum it'd be good to be able to trace to an open issue for our documentation.

@astrogeco could this get assigned and closed out? Would be good to get an answer here and add to user's guide or design material.

From code inspection of 3.X: 1) Directory gets opened 1) Directory entries are read one-by-one and up to `CF_NUM_TRANSACTIONS_PER_PLAYBACK` files in the directory get queued 1) Based on priority, whatever...

And confirmed w/ a class 1 transfer of everything in /cf on channel 0: ./cmdUtil -ELE -C3 -A0xB3 --uint8=0 --uint8=1 --uint8=0 --uint8=0 --uint32=0 --string=64:/cf --string=64:bleh Followed by a bunch of...

We will need to include all the cFE related elements for open source verification so how about a structure like: - cfe - verification_tests - ctf - json

I wonder if there are more generic names for these, since linking directly to the tool may be over-constrictive. Really it's the database dfn and requirements verification tests, no? If...

That said, we've also got the eds descriptions in cfe/modules/core_api/eds... maybe instead of having multiple "database" files, we just provide the recipe for conversion? The problem I see is when...

Could be leveraged for #128