Re: [systemd-devel] Prosody Failed on start

2017-08-11 Thread Tomasz Torcz
On Sat, Aug 12, 2017 at 01:08:08AM +0530, Sabir Mohammed wrote: > Hi, > > I am installed prosody successfully and it worked without any problem at > first. After that I reboot the server and again started prosody. But at > this time, it shows failed message. > > > * prosody.service - LSB:

[systemd-devel] Prosody Failed on start

2017-08-11 Thread Sabir Mohammed
Hi, I am installed prosody successfully and it worked without any problem at first. After that I reboot the server and again started prosody. But at this time, it shows failed message. [root@server ~]# service prosody restart Restarting prosody (via systemctl): Job for prosody.service failed

Re: [systemd-devel] Outputting STDOUT and STDERR to current $SSH_TTY

2017-08-11 Thread vcaputo
This is not recommended. Forwarding is currently implemented synchronously in journald, and can have a very substantial negative impact on journald performance in general as a result. BTW: are we not averse to top-posting on systemd-devel? Regards, Vito Caputo On Fri, Aug 11, 2017 at

Re: [systemd-devel] Outputting STDOUT and STDERR to current $SSH_TTY

2017-08-11 Thread Mantas Mikulėnas
Doing that directly makes little sense. The terminal will eventually go away, and your service will start getting write errors for stdout. Instead it would be better if systemctl could spawn `journalctl --follow --unit=`... I remember it used to have a follow option for status. On Fri, Aug 11,