On 2021-09-10, i...@protonmail.com wrote:
> Is there any particular reason why this issue is being ignored?
>
> https://www.mail-archive.com/bugs@openbsd.org/msg15344.html
>
Probably just nobody who read it at the time was interested enough to work on
it,
especially given that the workaround giv
Is there any particular reason why this issue is being ignored?
https://www.mail-archive.com/bugs@openbsd.org/msg15344.html
On 2021-05-10, Roger Marsh wrote:
> After upgrading to OpenBSD 6.9 'ValueError: ZIP does not support timestamps
> before 1980' exceptions started occuring when installing python packages by:
>
> 'python3.8 setup.py install --user' where the package was built b
After upgrading to OpenBSD 6.9 'ValueError: ZIP does not support timestamps
before 1980' exceptions started occuring when installing python packages by:
'python3.8 setup.py install --user' where the package was built by:
'python3.8 setup.py sdist --formats gztar'
Tue, 26 Feb 2019 08:37:04 +0200 Mihai Popescu
> Hello,
>
> I am trying since a while to figure out the master site / mirrors
> files timestamps.
Hi Mihai,
Most probably, you need the file named BUILDINFO, see for example these:
https://ftp.openbsd.org/pub/OpenBSD/snapshots/amd
On 2019-02-26, Mihai Popescu wrote:
> Hello,
>
> I am trying since a while to figure out the master site / mirrors
> files timestamps. Here is the thing: I can see the timestamps on
> master site, ftp.openbsd.org (let's skip the transfer protocol, like
> ftp, http/https).
Hello,
I am trying since a while to figure out the master site / mirrors
files timestamps. Here is the thing: I can see the timestamps on
master site, ftp.openbsd.org (let's skip the transfer protocol, like
ftp, http/https).
Are these timestamps the original from compilation time? I mean,
On 1/21/2016 5:53 AM, Stuart Henderson wrote:
Removing timestamps will kill performance unless it's on a slow line.
It gives a good clue though - try this (on the centos box) instead:
http://stackoverflow.com/questions/8893888/dropping-of-connections-with-tcp-tw-recycle
Better reference.
blem on Server Fault [2]. It
>> turned out OpenBSD was sending two SYN packets with timestamps (which
>> were dropped by CentOS), then sending a SYN without a timestamp (which
>> was successful). Setting sysctl net.ipv4.tcp_timestamps=0 on the CentOS
>> proxy worked aro
. After far too long staring at debug logs and
> packet traces, it turned out that the proxy OS (CentOS) simply wasn't
> passing the traffic through to the proxy.
>
> I found a description of a similar problem on Server Fault [2]. It
> turned out OpenBSD was sending two SY
traces, it turned out that the proxy OS (CentOS) simply wasn't
passing the traffic through to the proxy.
I found a description of a similar problem on Server Fault [2]. It
turned out OpenBSD was sending two SYN packets with timestamps (which
were dropped by CentOS), then sending a SYN with
why the connection to port 8001 does go through while ssh fails.
Btw, is there a reason PF requires the timestamps to be so slow? I quickly
skimmed through rfc1323, and didn't see that it was mandated that it be as
slow as PF requires it to be. One part of the RFC says "the maximum
acceptab
I'm running snort on OpenBSD 4.0 amd64. I've tried 2.4.5 among the
packages, and built 2.6.1.4 from the source (are there any special
configure options I should use?). Also I've tried many combinations of
rules: registered user, community and bleeding-edge rules. The same
result.
For example, when
On Tue, Oct 03, 2006 at 08:40:38PM +0200, Karel Kulhavy wrote:
> Is it possible to turn on some kind of timestamps or sequence numbers in
> dmesg?
> When I ocassionally get an error message (uncorrectable error on CD), I would
> like to know if I got one recently or not. Difficult to
> Is it possible to turn on some kind of timestamps or sequence numbers in
> dmesg?
No.
> When I ocassionally get an error message (uncorrectable error on CD), I would
> like to know if I got one recently or not. Difficult to distinguish 1000 and
> 1001 messages of this type in
Is it possible to turn on some kind of timestamps or sequence numbers in dmesg?
When I ocassionally get an error message (uncorrectable error on CD), I would
like to know if I got one recently or not. Difficult to distinguish 1000 and
1001 messages of this type in dmesg otherwise.
CL<
16 matches
Mail list logo