Hi Dave, That sounds like a good plan. Does anyone know if it's possible to get tcpborphserver to put it's logs into syslog so they end up on the remote syslog recorder?
Glenn On Wed, Mar 27, 2013 at 12:53 PM, David MacMahon <[email protected]> wrote: > Hi, Glenn, > > I don't know about getting tcpborphserver to log messages. For logging in > general, I recommend running syslog on the ROACH (1 or 2) configured to send > its messages to a "logserver" host on on your network. With some syslog > configuration setup on the receive side (e.g. on "logserver") you can get > each remote host's messages to show up in a host specific log file. > > Dave > > On Mar 27, 2013, at 8:29 AM, G Jones wrote: > >> Hi, >> We're experiencing some intermittent failures where it appears the >> FPGA is spontaneously deprogramming on the ROACH II. We'd like to try >> to track this down by turning on logging in tcpborphserver3. Has >> anyone done this for a network mounted ROACH II? Should we mount an >> extra directory as r+w to store the logs? Looking for advice on best >> practices or at least something that works. >> >> Thanks, >> Glenn >> >
