Jon LaBadie <[email protected]> (Di 11 Jul 2017 15:27:47 CEST):
> > No, it just redirects the STDERR (if there is any) to
> > the journal, and not to the client.  Or needs amandad to send (stderr) 
> > output to the client?
> > 
> Without investigation I assumed the log/debug files were written
> via stderr.  Probably they are opened separately.

I suppose, they are opened by the daemon, becase xinetd doesn't have
this functionality.

> > Hm. If the environement file is already named "amanda", I do not see
> > a reason to replicate "amanda" in the variable name. But I do not mind
> > either.
> 
> When you put it that way there probably is none.
> I was thinking of possible future needs for more
> "services" variables plus child processes inheriting
> an environment containg "SERVICES".

If a child depends on such an unspecific name as SERVICES, I cannot help
:)

> BTW the dash after ENVIRONMENT_FILE= is a typo?
> Or some systemd syntax.

No, in is just a "conditional", if the file does not exist, it is not
treated as an error (as it would be without the dash).


And, the Amanda Version I use (3.3.9) doesn't work with

    ListenStream=10080

As the socket is an "combined" ipv4/ipv6 socket and probaby the client
doesn't use the proper function calls to get the peer address.

    ListenStream=0.0.0.0:10080

solved this for me. One should investigate it a bit more probably.

-- 
Heiko

Attachment: signature.asc
Description: PGP signature

Reply via email to