proxmox-mirrors/pve-installer
1
0
Fork 0
mirror of https://git.proxmox.com/git/pve-installer synced 2025-04-28 12:51:31 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity
22de6e5f9f
pve-installer/proxmox-tui-installer
History
Christoph Heiss 22de6e5f9f tui: install_progress: write low-level non-JSON messages to separate file 
The low-level installer prints quite a few messages during the install
to its stdout which are not JSON-formatted and thus parseable.

Thus catch them early and write them to `/tmp/install-low-level.log`, to
avoid polluting the log tty at /dev/tty2 with mostly useless parse
errors.

Signed-off-by: Christoph Heiss <c.heiss@proxmox.com>
2024-02-27 16:43:42 +01:00
..
src tui: install_progress: write low-level non-JSON messages to separate file 2024-02-27 16:43:42 +01:00
Cargo.toml tui-installer: add dependency for new common crate 2023-11-02 20:04:24 +01:00
README.md tui: add README describing some debugging specifics 2023-06-14 10:39:56 +02:00

README.md

proxmox-tui-installer

Testing/debugging

stderr redirection

If something needs to be printed for debugging (e.g. using eprintln!() or dbg!()), output redirection can be used. Open a second terminal and get the file name of the terminal using the tty command:

$ tty
/dev/pts/6

Now, simply run the installer using:

$ cargo run 2>/dev/pts/6

All stderr output will then show up in the other terminal.

Specific terminal size

To test the installer with a specific output size, the stty command can be used. For example, to set it to a standard 80x25 terminal:

$ stty columns 80 rows 25