Re: debugging pppoe
On Monday 11 June 2007 22:54, Michael P. Soulier wrote: > On 04/06/07 Nikos Vassiliadis said: > > ppp does not write much on the console. And that is probably a > > decision made by the authors, since it is meant to be run mostly > > interactively. You can see its logs in /var/log/ppp.log > > Indeed. I turned up the logging and I had to turn it down before it > filled /var. :) > > If I could get it to log like that to the console, then I could > supervise it with runit, logging via svlogd. I am not familiar with these programs, but keep in mind that these methods may not be the best choice. FreeBSD and BSDs in general are very nicely integrated. The solution might (or not) be in the base system. > I guess there's no way to > force that log level to stdout? You guessed wrong:) From ppp(8): It is also possible to log directly to the screen. The syntax is the same except that the word ``local'' should immediately follow ``set log''. The default is ``set log local'' (i.e., only the un-maskable warning, error and alert output). Something else of possible interest is that ppp, can serve its console over a socket making remote debugging possible. HTH, Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: debugging pppoe
On Monday 11 June 2007 21:54, Michael P. Soulier wrote: > On 04/06/07 Nikos Vassiliadis said: > > ppp does not write much on the console. And that is probably a decision > > made by the authors, since it is meant to be run mostly interactively. > > You can see its logs in /var/log/ppp.log > > Indeed. I turned up the logging and I had to turn it down before it filled > /var. :) > > If I could get it to log like that to the console, then I could supervise > it with runit, logging via svlogd. I guess there's no way to force that log > level to stdout? It looks as though set log local ... does what you want: check the manpage for ppp. Jonathan ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: debugging pppoe
On 04/06/07 Nikos Vassiliadis said: > ppp does not write much on the console. And that is probably a decision > made by the authors, since it is meant to be run mostly interactively. > You can see its logs in /var/log/ppp.log Indeed. I turned up the logging and I had to turn it down before it filled /var. :) If I could get it to log like that to the console, then I could supervise it with runit, logging via svlogd. I guess there's no way to force that log level to stdout? Thanks, Mike -- Michael P. Soulier <[EMAIL PROTECTED]> "Any intelligent fool can make things bigger and more complex... It takes a touch of genius - and a lot of courage to move in the opposite direction." --Albert Einstein pgpHNcGUfFG5F.pgp Description: PGP signature
Re: debugging pppoe
On Tuesday 29 May 2007 20:38, Michael P. Soulier wrote: > I've turned logging up to All for ppp, for my DSL connection, and I've > been disappointed to find that when it can't connect, ppp offers no > help whatsoever as to why. > > I'm going to try rp-pppoe from ports, since on Linux it's actually > quite helpful in full debug, but I'm surprised at how little BSD's ppp > tells me when logging is turned right up. > > Any other suggestions? ppp does not write much on the console. And that is probably a decision made by the authors, since it is meant to be run mostly interactively. You can see its logs in /var/log/ppp.log HTH, Nikos ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"