On Fri, Jan 02, 2015 at 02:11:34AM +0200, Kaspars Bankovskis wrote:
> On Thu, Jan 01, 2015 at 10:28:44PM +0001, Jason McIntyre wrote:
> > it's not exactly that we updated wc knowing that it was not posix
> > conformant. i think the general explanation is that the current
> > implementation of obsd
can someone test this?
it allocates storage for the volume change details rather than cast
arguments to a single global task.
adds some safety while there if audio0 is a hotplug device.
ok?
Index: audio.c
===
RCS file: /cvs/src/sys
Is there any way todo the equivalent of:
server "an.example.com"
listen on 192.168.2.99
listen on 2001.fefe.1.1::99
??
It appears that the code in parse.y explicitly forbids this
and the data structures for a server don't *seem*
to have more than one slot for an address.
Is there anothe
On Thu, 1 Jan 2015 13:47:59 -0700, Andrew Fresh wrote:
> I had seen complaints but was unable to reproduce the problem myself.
> Nathanael Rensen sent me an email out of the blue with both the likely
> culprit as well as a patch to fix. A few days after receiving this
> patch, another person ema
On Thu, Jan 01, 2015 at 10:28:44PM +0001, Jason McIntyre wrote:
> it's not exactly that we updated wc knowing that it was not posix
> conformant. i think the general explanation is that the current
> implementation of obsd treats characters and bytes the same, but they
> might not on other systems,
On Thu, Jan 01, 2015 at 03:17:48PM +0200, Kaspars Bankovskis wrote:
> Correct me if I'm wrong, but it seems to me that the manual for wc(1)
> has been updated to be compliant with the standard but implementation
> not. -m and -c both set dochar=1 and I can't see any difference in
> further executio
I had seen complaints but was unable to reproduce the problem myself.
Nathanael Rensen sent me an email out of the blue with both the likely
culprit as well as a patch to fix. A few days after receiving this
patch, another person emailed me to ask if I knew why the parallel make
failed. I forwar
Hi,
When syslogd is sending via TCP, there a file descriptor leak and
a use after free if it receives a SIGHUP. Call bufferevent_free()
to deactivate the callbacks and close the TCP socket.
ok?
bluhm
Index: usr.sbin/syslogd/syslogd.c
On Thu, Jan 01, 2015 at 06:15:22PM +, Florian Obser wrote:
> No, we should drop the log altogether.
>
> Note that section 6.2.7 of RFC2461 or the newer RFC 4861 have nothing
> to say about router advertisments comming in on non-advertising
> interfaces.
It says:
The logging of errors SHOUL
OK with me. Thanks.
On Thu, Jan 1, 2015 at 12:15 PM, Florian Obser wrote:
> (moved to tech@)
>
> On Thu, Jan 01, 2015 at 11:51:32AM -0600, Aaron Riekenberg wrote:
> > I found some other reports of the same problem with rtadvd logging
> > excessive messages about router advertisements on the ext
(moved to tech@)
On Thu, Jan 01, 2015 at 11:51:32AM -0600, Aaron Riekenberg wrote:
> I found some other reports of the same problem with rtadvd logging
> excessive messages about router advertisements on the external
> non-advertising interface.
>
> From OpenBSD 5.2:
> http://openbsd.7691.n7.nabb
Hi,
Use SIMPLEQ for syslogd filed list instead of manual list operations.
ok?
bluhm
Index: usr.sbin/syslogd/syslogd.c
===
RCS file: /data/mirror/openbsd/cvs/src/usr.sbin/syslogd/syslogd.c,v
retrieving revision 1.137
diff -u -p -r1.
On Fri, 12 Dec 2014 13:45:02 -0600
joshua stein wrote:
> https://news.ycombinator.com/item?id=639976
Thanks for the interesting read!
It just makes it even clearer that this is a
serious issue to consider in your security
markups.
--
FRIGN
Hello and happy new year.
So this is a quite a small diff which, hopefully, will make lib fuse
slightly better. Indeed, it might exist two small potential memory leaks,
first the memory allocated after parsing command line when it succeeds, the
other the very first option argument in the list. Hop
Correct me if I'm wrong, but it seems to me that the manual for wc(1)
has been updated to be compliant with the standard but implementation
not. -m and -c both set dochar=1 and I can't see any difference in
further execution. They're not "mutually exclusive" either (opposed to
manual) as it's the s
Hi,
Sunil Nimmagadda wrote on Tue, Dec 23, 2014 at 03:57:53PM +0100:
> tls_accept_socket function missing in tls_init(3) manpage.
Since nobody took pity on this patch, i have put it in.
SSL hackers, feel free to improve the wording if needed.
Yours,
Ingo
> Index: tls_init.3
> =
16 matches
Mail list logo