Which directive is added to the xudad.conf file when scheduling automatic CRL generation?

Nina C.Dec 13, 2025

The answer is A, crltimer. When you need xudad.conf to handle automatic CRL generation on a schedule, crltimer is the directive that actually tells the service when to kick off that process, kind of like setting a recurring alarm for it. The other options sound plausible if you are just guessing from the names, but crl_update, crlgenerate, and crlauto are not valid directives in that config file for this purpose. Once I saw that crltimer ties directly to the timer-based scheduling mechanism the daemon uses, it clicked for me, because the name itself tells you it is a timer for CRL work, not just a one-time trigger or a generic update flag.

Luis F.Dec 18, 2025

I actually went with C first because "crlgenerate" just sounds like what you'd put in a config file for generating something, but then I looked closer at the docs and saw that the directive uses a timer-based approach to schedule the automation, so "crltimer" is the one that makes sense for xudad.conf. Once I saw it was about scheduling rather than just triggering generation, A clicked right away.

Fatima Z.Dec 3, 2025

Okay so I am going D and here is my lock-it-in reasoning: think of it as AUTO = Automatic, and "crlauto" literally spells out what it does, CRL plus AUTO, meaning the config file is telling the daemon to automatically handle CRL generation on a schedule. The other options like crltimer and crlgenerate are too narrow, one sounds like it just sets a clock and the other sounds like a one-shot manual trigger, neither screams "schedule this and forget it." My hook for this is the phrase "Cars Run Laps AUTOmatically," which maps to CRL AUTO, and whenever I see a question about scheduling CRL tasks in a conf file I picture that car just looping the track with zero human input. D is the directive that belongs in xudad.conf when you want the system to take the wheel on CRL updates without you babysitting it.