Systemd is pretty good at this.
Get FAI to install a unit file to run your thing, and add a unit option
like ConditionPathExists=/foo/bar or ConditionPathExists=!/foo/bar
Then make your thing touch or delete a flag file [ /foo/bar ] if
successfully run.
There you have it, a service/script that onl
Well, it's not really to the point. Maybe my example was bad but there
are lots of other reasons one might want to run a script after the
install is finished. Actually, the reason this came up is that I want
the linux cli screen reader to run on the first boot and then get
disabled. But I just
You can configure the nfsroot with your ldap configs so you can have them
available during fai. I used this (at another UW department) for rescue
consoles to support natural logins from admins.
As far as the sudo config, why not just copy a sudoers (.d) snippet down
that references the user during
Hi John,
if you are using LDAP - why not permitting a LDAP group (which already
exists during install) and then configure sudo via LDAP?
Thats how I solved it for my soho environment.
See: https://www.sudo.ws/man/1.8.17/sudoers.ldap.man.html
Kind Regards
Martin
On Wed, Jan 9, 2019, 22:06 John
