On Apr 25 10:27, Dale R. Worley wrote: > > From: Jesper Dahl Nyerup <nyerup@xxxxxxx> > > > > 1. Adding a daemon next to script(1) and scriptreplay(1), eg. > > scriptcollect(1), to be in the receiving end of the traffic, optionally > > handling the timing functionality, and finally storing data in the same > > manner script(1) would. > > You might want to consider using syslog(3) for this. Or conversely, > if syslog won't work in your environment, that might indicate > improvements that are needed in syslog. We considered that, but kind of gave up on the idea. Syslog is inherently newline delimited, where as the per-update payloads from script(1) are pretty much the opposite - one payload will often contain multiple newlines, others will consist of a single character. Thus, (de)serializing to and from syslog will probably be more of a hassle than using it will be a benifit. J. -- Jesper Dahl Nyerup Systems Engineer One.com, nyerup@xxxxxxx
Attachment:
signature.asc
Description: Digital signature
