Hi TurnKey team,

I am seeing behavior with `inithooks` / `confconsole` on a TurnKey LXC container under Proxmox and wanted to confirm whether this is expected.

## Environment

- TurnKey appliance running in a Proxmox LXC container
- Debian 13 / trixie base
- Package versions observed:

confconsole 2.2.3
inithooks 2.3.4

Problem

Confconsole autostart appears to be disabled, but Confconsole still gets activated by inithooks.

The relevant config looks like this:

/etc/confconsole/confconsole.conf:

# autostart on login - one of true|once|false
#autostart once

And:

/etc/default/inithooks:

RUN_FIRSTBOOT=false
REDIRECT_OUTPUT=false

There is no confconsole.service unit enabled or running:

systemctl list-unit-files '*confconsole*'
UNIT FILE STATE PRESET

0 unit files listed.

However, when inithooks runs, it still starts Confconsole directly:

/usr/lib/inithooks/run:

Inithook run completed, now starting confconsole
confconsole --usage
On inithooks 2.3.4, the systemd unit also appears to take over tty1:
Description=Run boot scripts and start confconsole on tty1
Conflicts=getty@tty1.service container-getty@1.service
ExecStart=/usr/lib/inithooks/run
TTYPath=/dev/tty1

In a Proxmox LXC console this seems to reset/disconnect the console session when the package is configured or when the hook flow runs.

Logs / evidence

Redacted example:

root@[REDACTED_HOST]:~# systemctl list-unit-files '*confconsole*'
UNIT FILE STATE PRESET
0 unit files listed.

root@[REDACTED_HOST]:~# dpkg-query -W -f='${Package} ${Version}\n' inithooks confconsole
confconsole 2.2.3
inithooks 2.3.4

root@[REDACTED_HOST]:~# grep -RIn "confconsole --usage" /usr/lib/inithooks/run
/usr/lib/inithooks/run:138:    confconsole --usage

Question

Is it expected that disabling Confconsole autostart does not affect the inithooks final confconsole --usage launch?

In other words, is the Confconsole Auto Start setting intended to control only login shell autostart, while inithooks is always expected to launch Confconsole on tty1 when REDIRECT_OUTPUT=false?

I wanted to check whether this behavior is intentional, especially because in a Proxmox LXC console the inithooks.service tty/getty handling appears to cause the console to disconnect/reset.