Crank runs give warnings about missing PDTs

[Eric Swenson]

When you run the crank on a newly-coldbooted system, you get the following warnings:

pdt_copy: Entry not found. Operator.pdt
pdt_copy: Entry not found. HFED.pdt
pdt_copy: Entry not found. Terminals.pdt
compute_bill: Entry not found. Operator.pdt
compute_bill: Entry not found. HFED.pdt
compute_bill: Entry not found. Terminals.pdt
update_pdts_from_reqfile: Entry not found. Operator.pdt
update_pdts_from_reqfile: Entry not found. HFED.pdt
update_pdts_from_reqfile: Entry not found. Terminals.pdt

These are not fatal, and probably even reasonable. It probably makes sense to NOT install the Operator, HFED, and Terminals projects automatically. However, if we agree that this is true, it might be nice to update the crank to not provide these warnings (or not).

This ticket is here so that we can decide.

[Eric Swenson]

The reason why these warnings are issued is because >t>acct_start_up.ec registers these three projects in the SAT (>sc1>sat), and provides PMFs for these projects, but intentionally does not convert and install the PDTs. These projects define accounts PersonIds and anonymous logins that may introduce security issues (known passwords or password-less logins) and it was probably felt that human administrator intervention should be required before installing these PDTs.

It may be that we should just leave this alone -- perhaps documenting the crank warnings, explaining why they occur, and telling the user what to do about it (either delete the projects from the SAT or convert and install the PDTs after checking the accounts created therein to make sure they are acceptable.