On Tue, Jul 11, 2017 at 10:40:36AM +0200, Heiko Schlittermann wrote: > Jon LaBadie <[email protected]> (Di 11 Jul 2017 07:56:28 CEST): > > > > > > | StandardInput=socket > > > > > | StandardError=journal > > > > Does this prevent writing to amanda's normal log/debug files? > > 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.
> > > Maybe this could be done via an env file /etc/default/amanda having > > > SERVICES="amdump amindexd amindxtaped…" > > > > > > and then extending the .service unit: > > > > > > EnvironmentFile=-/etc/default/amanda > > > ExecStart=/usr/lib/amanda/amandad -auth=bsdtcp $SERVICES > > > > I was not aware of this capability. I think I'd pick a more specific > > variable name, like AMANDAD_SERVICES. > > 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". BTW the dash after ENVIRONMENT_FILE= is a typo? Or some systemd syntax. jl -- Jon H. LaBadie [email protected] 11226 South Shore Rd. (703) 787-0688 (H) Reston, VA 20190 (703) 935-6720 (C)
