Michael Butler wrote
in :
im> It appears that SVN r309925 and onward no longer opens a network
im> socket unless the command-line explicitly contains "-b :syslog" :-(
im>
im> This also stops one syslog daemon forwarding to another (which is why
im> I noticed).
im>
im> Was this an intentional be
On Fri, Dec 16, 2016 at 03:19:09PM -0800, John Baldwin wrote:
>
> So the hack in pause() is probably not as necessary now. In particular, I
> think we only need it for thread0, not for other threads. The patch below
> worked for me with SPEW's config:
>
> Index: kern_synch.c
> =
Hi,
I am trying to rewrite userland programs (especially daemons) to
support userland DTrace probes to make it possible to trace the
behavior by using dtrace(1). The purpose is to provide a consistent
interface to enable/collect debug log and show internal states. A
lot of daemons define th
Hi,
I'd love to see a unified-ish logging API for FreeBSD applications. I
always end up reusing some C code I have here that I based on some
Squid style logging API in ages past. I could always polish it up and
put it up for review.
I'm not a big fan of requiring dtrace to use it though. On a lot
Hello,
> You can try to compile a new syslogd, run it, and then attach
> dtrace(1) to the syslogd process by "dtrace -q -CI./
> -s ./syslogd_trace.d -p `pgrep syslogd`" in the same directory.
one thing that comes to mind is the lack of a way to actually fire these
probes without running plent
Hello,
> I'd love to see a unified-ish logging API for FreeBSD applications. I
> always end up reusing some C code I have here that I based on some
> Squid style logging API in ages past. I could always polish it up and
> put it up for review.
>
> I'm not a big fan of requiring dtrace to use it th
Hello,
> To be clear: my proposal is to replace only debug logging (i.e. for
> developers), not the other logging in general, as the subject line
> says. Although I agree that DTrace is not lightweight, I think
> impact of just adding tracing probes is small.
>
> -- Hiroki
I believe this wo
On 19 December 2016 at 16:04, Jordan Hubbard wrote:
>
> On Dec 19, 2016, at 12:27 PM, Adrian Chadd wrote:
>
> So although I like the sentiment, I don't think using dtrace for
> program logging is the right answer. I like what apple did to wrap
> the program logging stuff so people didn't just wr
On 12/19/16 12:12, Hiroki Sato wrote:
Michael Butler wrote
in :
im> It appears that SVN r309925 and onward no longer opens a network
im> socket unless the command-line explicitly contains "-b :syslog" :-(
im>
im> This also stops one syslog daemon forwarding to another (which is why
im> I noti
> On Dec 19, 2016, at 12:27 PM, Adrian Chadd wrote:
>
> So although I like the sentiment, I don't think using dtrace for
> program logging is the right answer. I like what apple did to wrap
> the program logging stuff so people didn't just write their own
> libraries (hi!) and so there's a unif
Adrian Chadd wrote
in :
ad> On 19 December 2016 at 16:04, Jordan Hubbard
wrote:
ad> >
ad> > On Dec 19, 2016, at 12:27 PM, Adrian Chadd wrote:
ad> >
ad> > So although I like the sentiment, I don't think using dtrace for
ad> > program logging is the right answer. I like what apple did to wrap
Michael Butler wrote
in :
im> On 12/19/16 12:12, Hiroki Sato wrote:
im> > Michael Butler wrote
im> > in :
im> >
im> > im> It appears that SVN r309925 and onward no longer opens a network
im> > im> socket unless the command-line explicitly contains "-b :syslog"
im> > :-(
im> > im>
im> > im> T
*mumble* damnit jordan this requires libdispatch *mumble*
-a
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
13 matches
Mail list logo
