https://bugzilla.wikimedia.org/show_bug.cgi?id=48846
--- Comment #12 from Tim Landscheidt <[email protected]> --- (In reply to comment #11) > > > Rsyslogd doesn't seem to be enough for this, a separate service needs to > > > be > > > created > > Why? What's missing? > I forgot to mention that rsyslog was installed there as well, so feel free to > use that if you prefer. It is missing basically everything I would use as a > tool operator and it's incredibly complicated. But you can of course use it What's complicated about rsyslog? What's missing there that on the other hand a simple TCP sink has?! :-) > > > Is this running syslog or a similar service? I hope it isn't a custom C# > > > server > > > running there with no monitoring or logging of its own... > > > /me eyes petan suspiciously > > I hope it has libraries in C#, PHP, Perl, Python, C, Java, C++, Tcl, and > > whatever else people use on Tools. > It is listening on UDP and TCP ports, I don't know what libraries you need? > There is provided a very simple 1 line example in shell script which is > likely > easy to convert to any language I know. It is far simpler than rsyslog or > scribe, but nearly same powerful. Why do you think it is running with no > monitoring? As you know, there are lots of logging frameworks where you can just plug in modules for rsyslog or other remote daemons (or files or printers or ...). Your daemon implements a new protocol, so we need new plugins for them. For example, how do I configure Python's logging to log to your daemon? -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Wikibugs-l mailing list [email protected] https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
