Jerry Vonau

Systemclt has '--no-block Do not wait until operation finished' while https://docs.ansible.com/ansible/2.10/collections/ansible/builtin/systemd_module.html 'no-block no|yes Do not synchronously wait for the requested operation to finish. Enqueued job will continue without Ansible blocking...

Could show up during an install, I just hit this using runrole. If I recall correctly it's actually a race condition caused by postgresql.service unit file layout and ansible not...

You could close if you want, 'no_block: yes' should be employed anywhere the underling service might takes awhile to shutdown to avoid a noted race condition.

> > You could close if you want, 'no_block: yes' should be employed anywhere the underling service might takes awhile to shutdown to avoid a noted race condition. > >...

Trying to future proof the installs where the user has explicitly turned off iiab-admin and prevent a TK like issue where some mystery code is blocking a desktop from loading.

> > a TK like issue where some mystery code is blocking a desktop from loading. > > Is there a link to that issue, explaining the situation a bit?...

Don't think polluting the filesystem, potentially breaking future OS changes with a check for a non-existent user is the best course of action when iiab-admin was specifically asked not to...

Hum... judging by the appearance of kalite after the network stanza in iiab.ini suggests that kalite was added post-install for some reason, depending on the path that was chosen for...

The 2 kalite functions should be abstracted into other scrips that could be called from within 'iiab' or by the admin-console as needed.

Is there still a 'bug' here or have the docs been cleaned up enough?