4 Commits

Include renames

Author	SHA1	Message	Date
jochen	02a1c5f753	Refuse to take over a system account as one that never becomes root ... The controller cannot read a machine's user database, so a name it is given for the agents' account (hq ADR 0266) may be a service's own; taking it over would hand agents that service's files. Refuse it, touching nothing.	2026-10-09 10:07:52 +02:00
jochen	a018ebd1ca	Pass -- before every unit, and give a unit back only when it is exactly as the mesh held it ... Third review of mesh-catalog #147. A unit's name can now come from a setting (a template's instance), so every systemctl call that names a unit passes `--` before it, and a name can never be read as an option. On removal, a unit is started or enabled again only when it is exactly the stopped and disabled the mesh held it to. A masked unit, or one somebody started or enabled since, is left as it is, and the report says why. A restore that fails (the start refused, or the unit not running after it) puts back what this attempt changed and is reported as waiting, so no apply is made fatal by it and the next one tries again. The tests' fake service managers read systemctl's arguments in the shape they were written for (oldShape); internal/system's own test holds the `--`.	2026-10-09 01:54:26 +02:00
jochen	f2eda240ec	Cite hq issue 228: 225 was taken on main while this branch was open	2026-10-04 10:30:57 +02:00
jochen	5d5dccdd55	A login the mesh set is given back, and undeclaring one no longer stops the apply (hq issue 225) ... A user had no removal, so an undeclared one failed as an orphan and aborted every apply after. Removal now keeps the account, gives back the shell recorded when the mesh first changed it if it is still the mesh's and still usable, and says why otherwise (hq ADR 0176 §2). A shell is refused before it is set unless it is executable and listed in /etc/shells, since usermod succeeds on a missing one.	2026-10-04 03:57:34 +02:00