On Tue, 22.01.13 18:25, Scott Shambarger (scott-syst...@shambarger.net) wrote:
>
> (oops, forgot to reply-all :)
>
> On 2013-01-22 17:14, Lennart Poettering wrote:
> >On Tue, 22.01.13 16:55, Scott Shambarger
> >(scott-syst...@shambarger.net) wrote:
> >>Agreed, however I'd like to suggest another
(oops, forgot to reply-all :)
On 2013-01-22 17:14, Lennart Poettering wrote:
On Tue, 22.01.13 16:55, Scott Shambarger
(scott-syst...@shambarger.net) wrote:
Agreed, however I'd like to suggest another possibility. Perhaps
journalctl could add an option to output to a syslog socket (say
here /ru
On Tue, 22.01.13 15:02, Scott Shambarger (scott-syst...@shambarger.net) wrote:
> I'm running Fedora 17 with rsyslog, but since I also need to also
> receive logs via UDP, I've updated rsyslog.service to include
> After=network.target (so the private network binding works).
>
> However, syslogs cr
On Tue, Jan 22, 2013 at 10:02 PM, Scott Shambarger
wrote:
> I'm running Fedora 17 with rsyslog, but since I also need to also receive
> logs via UDP, I've updated rsyslog.service to include After=network.target
> (so the private network binding works).
>
> However, syslogs created before network.t
I'm running Fedora 17 with rsyslog, but since I also need to also
receive logs via UDP, I've updated rsyslog.service to include
After=network.target (so the private network binding works).
However, syslogs created before network.target aren't forwarded to
rsyslog when it's started (rsyslog is
