Hello
On Wed, Sep 7, 2011 at 7:11 PM, Albert Strasheim wrote:
> Finally my question: is it possible for my custom shell to connect
> stderr of bar to stdout-syslog-bridge? Is this feasible, or was
> stdout-syslog-bridge designed to interact with systemd only?
Okay, wow, that was easy:
printf "s
Hello all
We have the following situation:
We have a service that is exposed through OpenSSH.
The unit looks like this:
[Unit]
Description=bar Server
[Service]
ExecStart=-@/usr/sbin/sshd bar -ddd -i -f /etc/ssh/sshd_config_bar
StandardInput=socket
StandardOutput=socket
StandardError=syslog
[I
On Wed, 07.09.11 16:15, Michael Olbrich ([email protected]) wrote:
> Hi,
>
> Im running sshd with sshd.socket/[email protected] from
> http://0pointer.de/public/systemd-units/. With systemd 35 this doesn't work
> any more. The ssh client just hangs. The commit that breaks things is
> "de6c78f
Lennart Poettering poettering.net> writes:
> > I was wondering if there is some kind of guideline about whether
> > packaged .service files in Fedora, etc. should specify Restart=,
> > RestartSec=, etc.
[...]
> There's currently no policy on this, but I generally do believe it would
> make a lot o
Hi,
Im running sshd with sshd.socket/[email protected] from
http://0pointer.de/public/systemd-units/. With systemd 35 this doesn't work
any more. The ssh client just hangs. The commit that breaks things is
"de6c78f service: change default stdout/stderr to syslog". I can work
around this by adding "Sta
