Do I not know how to conscontrol(8)?

[sgharms]

I'm baffled by this utility and I can't tell if it's a bug or if I've not learned to read a man page.

By itself, the utility reports:
Configured: ttyv0
Available: ttyv0, gdb
Muting: on

I'd like to send console output to ttyv3. But I can't seem to do this with conscontrol(8).

The add | delete option seem to be the right call.

"high level console which is represented by /dev/console...[is] used by programs like syslogd(8)....[ set | set console commmands]...the virtual console."

OK, so `conscontrol set ttyv3` would seem to be valid...but that gets a "No such file or directory." To be fair, `...unset ttyv0` also reports no such file or directory.

In previous forum posts where this has come up, the set syntax seems like it should have worked like I report. I'm built against 15.0-CURRENT.

In any case, 1) have i misunderstood the interface and/or 2) is there some external condition that suggests why this isn't working?


Aside: This is all driven by a desire to direct console output to not ttyv0 although I think a reasonable userland solution for that is to update `/etc/syslog.conf` to send all messages that were going to /dev/console to a file (a slightly longer list of notification conditions than the commented-out line in the file suggests).

 

[T-Daemon]

OK, so `conscontrol set ttyv3` would seem to be valid...but that gets a "No such file or directory."

Apparently conscontrol expects a absolute path to the console device: conscontrol set /dev/ttyv3

I'd like to send console output to ttyv3.
...
This is all driven by a desire to direct console output to not ttyv0 although I think a reasonable userland solution for that is to update `/etc/syslog.conf` to send all messages that were going to /dev/console to a file

why not send all console messages to ttyv3 via /etc/syslog.conf?

- *.err;kern.warning;auth.notice;mail.crit                /dev/console
+ *.err;kern.warning;auth.notice;mail.crit                /dev/ttyv3

Perhaps add more facilities to the line, which eventually print their messages on ttyv0.

I would be interested how helloSystem has resolved the issue exactly. Hiding messages behind a splash screen (or redirect them), make it available on user request. Maybe I've have a look at it.

 

[sgharms]

Apparently conscontrol expects a absolute path to the console device: conscontrol set /dev/ttyv3

I read your post and then I was living in a state of fear "Did I..just..not..think...to try that?"

But I get: "conscontrol: could not set /dev/ttyv3 as virtual console: Device busy"

Flipping to Alt+f4 i see the login console confirming "FreeBSD/amd64 (hostname) (ttyv3)".

While debugging, t I decided to look at all vts and I noticed un-linebroken console content on ttyv4. I scrolled history in my root tty and yeah, at some point I had set (conscontrol set /dev/ttyv4). It's no-line broken, but it's there. Baffling.

So i tried to set it again: conscontrol set /dev/ttyv4 works?! It's the same entry in /etc/ttys ?!

why not send all console messages to ttyv3 via /etc/syslog.conf?

This is what I wound up adopting, preferring a userland versus kernel system solution. Setting the full default list of notifications for a file versus
/dev/console is a userland-supported, easy, neat solution. Also put a FreeBSD laptop in a less-technically-minded person's hands with that change in place (and my quieted down RC chattiness) and you have a not-scary laptop.

I would be interested how helloSystem has resolved the issue exactly. Hiding messages behind a splash screen (or redirect them), make it available on user request. Maybe I've have a look at it.

ISO/overlays/boot/boot/loader.mute.d/loader.conf at experimental · helloSystem/ISO

helloSystem Live and installation ISO. Contribute to helloSystem/ISO development by creating an account on GitHub.

github.com

I think that's the interesting bit