Andrew Clayton

Hopefully this will clear things up... When running with `--no-daemon`, `stdout` goes to the console (tty unit is running on) and `stderr` goes to the unit log. E.g ```sh $...

With `--no-daemon`, `stdout` goes to the console, `stderr` goes to the unit log. When running under systemd, because there is then no direct console systemd will get `stdout` > Would...

On Fri, 24 May 2024 10:08:00 -0700 MagnusOxlund ***@***.***> wrote: > That's not what I'm seeing. You won't by default and with the current systemd unit file. > [Service] >...

> Personally, I'm trying to direct both stdout and stderr to Unit's systemd journal to streamline log management. Have you tried this configuration... In `/etc/systemd/system/unit.service` ``` [Service] Type=forking Environment="UNITD_OPTIONS=--log /var/log/unit/unit.log...

_Without_ `--no-daemon` with a unit application config of ```json "stdout": "/dev/stdout", "stderr": "/dev/stderr" ``` Where does stdout/stderr go?

I think we can close this for now...

Hi @gdufrene The normal way we handle support for different versions of language stack in the language modules is via a bunch of #ifdefs... see src/nxt_php_sapi.c and src/python for examples....

> Hello, > > 3 components as you describe seems me a good idea. Your approach with current codebase in a javax package, my branch in a Jakarta package will...

HI, Sounds like you're making good progress! > Both are defined as maven project to help with dependencies, versions, compilation. I know it could add a requirement for building the...

> > Will we still be able to target different version of java? As I know we do build various versions of the java language module for different versions of...