mini_buildd.schroot module¶
Note
schroot: Verbosely logs commands (“Running command …”) explicitly via syslog (journalctl)
schroot seems to verbosely log any executed root-user command via syslog (user/notice). This will clutter journalctl’s (standard) log output via unit:
journalctl --unit mini-buildd.service --follow
As a workaround, specifying the (syslog compatibility) identifier like so helps to unclutter:
journalctl --identifier mini-buildd --follow
- class mini_buildd.schroot.Session(name, namespace='chroot')¶
Bases:
object
- close()¶
Close session (including retries on failure)
Attention
schroot: ‘target is busy’ on session close (stale schroot sessions)
Occasionally, a schroot session can’t be closed properly, leaving stale sessions around. Presumably, external programs (like ‘desktop mount scanners’) can cause this.
This internal close does try hard to avoid this – however, if disaster strikes anyway,
mini-buildd-cruft
may help to remove these stale sessions manually (i.e., asmini-buildd
user from the shell).
- call(_call, user='root')¶
- run(_call, user='root')¶
- info()¶
- update_file(file_path, content)¶
Write content to file
- set_debconf(key, value)¶
Set arbitrary debconf value