Re: newsyslog timestamp

Tue, 14 Mar 2017 00:16:01 +0100 Alexander Bluhm > On Mon, Mar 13, 2017 at 04:31:35PM -0600, Todd C. Miller wrote: > > How about we just eliminate the "logfile turned over" message > > entirely? It's kind of bogus for newsyslog to be writing to the > > log files directly.

[PATCH] socppc discontinued in 61.html

I am not sure what happened to the patch tj@ committed but it is not there for 61.html. Perhaps it was clobbered by another commit or was this not left in because socppc was essentially retired after 5.8 since there was no 5.9 or 6.0 release? For reference:

Re: newsyslog timestamp

On Mon, Mar 13, 2017 at 04:31:35PM -0600, Todd C. Miller wrote: > How about we just eliminate the "logfile turned over" message > entirely? It's kind of bogus for newsyslog to be writing to the > log files directly. I don't think that message provides any useful > info. Perhaps

Re: newsyslog timestamp

> From: "Todd C. Miller" > Date: Mon, 13 Mar 2017 16:31:35 -0600 > > How about we just eliminate the "logfile turned over" message > entirely? It's kind of bogus for newsyslog to be writing to the > log files directly. I don't think that message provides any useful >

Re: newsyslog timestamp

How about we just eliminate the "logfile turned over" message entirely? It's kind of bogus for newsyslog to be writing to the log files directly. I don't think that message provides any useful info. - todd

newsyslog timestamp

Hi, syslogd(8) -Z generates log files in ISO format and UTC. newsyslog(8) still uses BSD syslog timstamps. This looks a bit ugly when you combine them this way. Mar 12 01:00:01 t430s newsyslog[32158]: logfile turned over 2017-03-12T00:00:01.547Z t430s syslogd: restart I think it is overkill

Re: mg(1): keep current buffer if switch-to-buffer is aborted

ok benno@ Florian Obser(flor...@openbsd.org) on 2017.03.11 20:00:21 +: > For some reason I find myself quite often in the situation that I want > to C-x b to a different buffer but on entering the buffer name I > decide against it and C-g abort it. > > mg(1) then switches me to *scratch*.

Re: httpd: expand HTTP Host

Hi! Sure. Should I create new patch? Rivo On 13/03/2017, 20:38, "Florian Obser" wrote: On Mon, Mar 13, 2017 at 06:22:50PM +, Rivo Nurges wrote: > Hi! > > Host header is mandatory for HTTP 1.1 requests and httpd will return > 400 Bad request

Re: httpd: expand HTTP Host

On Mon, Mar 13, 2017 at 06:22:50PM +, Rivo Nurges wrote: > Hi! > > Host header is mandatory for HTTP 1.1 requests and httpd will return > 400 Bad request without it. With HTTP 1.0 requests I get 301 to the > IP the httpd is running on. > right, so the if (desc->http_host ==

Re: httpd: expand HTTP Host

Hi! Host header is mandatory for HTTP 1.1 requests and httpd will return 400 Bad request without it. With HTTP 1.0 requests I get 301 to the IP the httpd is running on. Connected to 10.XXX Escape character is '^]'. GET / HTTP/1.0\r\n\r\n HTTP/1.0 301 Moved Permanently Date: Mon, 13 Mar 2017

Re: httpd: expand HTTP Host

On Sat, Mar 11, 2017 at 06:11:53PM +, Rivo Nurges wrote: > Hi! > > Following will add possibility to expand $HTTP_HOST to the HTTP > Host header in "block return". > > In my setup I have relayd on port 443 and httpd on 80. This patch > allows me to redirect http(httpd) to https(relayd)

Re: pf: time since uptime instead of wall clock?

On 13 March 2017 at 15:09, Patrick Wildt wrote: > On Mon, Mar 13, 2017 at 02:33:02PM +0100, Mike Belopuhov wrote: >> On Tue, Mar 07, 2017 at 10:36 +0100, Patrick Wildt wrote: >> > On Tue, Mar 07, 2017 at 10:17:16AM +0100, Patrick Wildt wrote: >> > > Hi, >> > > >> > > currently

Re: pf: time since uptime instead of wall clock?

On Mon, Mar 13, 2017 at 02:33:02PM +0100, Mike Belopuhov wrote: > On Tue, Mar 07, 2017 at 10:36 +0100, Patrick Wildt wrote: > > On Tue, Mar 07, 2017 at 10:17:16AM +0100, Patrick Wildt wrote: > > > Hi, > > > > > > currently the pf status struct contains the time since pf was enabled as > > > seen

Re: pf: time since uptime instead of wall clock?

On Tue, Mar 07, 2017 at 10:36 +0100, Patrick Wildt wrote: > On Tue, Mar 07, 2017 at 10:17:16AM +0100, Patrick Wildt wrote: > > Hi, > > > > currently the pf status struct contains the time since pf was enabled as > > seen on the wall clock. This means when time drifts, or is set to some > >