Re: VMM sh: time sleep 30 takes 56 seconds
On Thu, Oct 18, 2018 at 10:34:20PM -0300, Daniel Bolgheroni wrote: > On Wed, Oct 17, 2018 at 08:42:46PM +, Mike Larkin wrote: > > A 1000Hz host helps here. I get 10.32s real time on sleep 10 with that > > setting. > > > > Note that qemu behaves the same way on OpenBSD. > > OK, the output is still slow when on serial, but things improved Is the console baudrate 9600 or 115200? > with 1000 Hz. I was going to ask why 1000 Hz isn't the default > then, but got the response. I'll leave here for reference: > > https://openbsd.amsterdam/clock.html > > Thank you. > > # for i in $(jot 10); do > > time sleep 30; > > done > 0m33.67s real 0m00.00s user 0m00.00s system > 0m33.96s real 0m00.00s user 0m00.00s system > 0m33.92s real 0m00.00s user 0m00.00s system > 0m33.62s real 0m00.00s user 0m00.00s system > 0m33.66s real 0m00.00s user 0m00.00s system > 0m33.64s real 0m00.00s user 0m00.00s system > 0m33.61s real 0m00.00s user 0m00.00s system > 0m33.85s real 0m00.00s user 0m00.00s system > 0m33.97s real 0m00.00s user 0m00.00s system > 0m33.74s real 0m00.00s user 0m00.00s system > # > > -- > db >
Re: VMM sh: time sleep 30 takes 56 seconds
On Wed, Oct 17, 2018 at 08:42:46PM +, Mike Larkin wrote: > A 1000Hz host helps here. I get 10.32s real time on sleep 10 with that > setting. > > Note that qemu behaves the same way on OpenBSD. OK, the output is still slow when on serial, but things improved with 1000 Hz. I was going to ask why 1000 Hz isn't the default then, but got the response. I'll leave here for reference: https://openbsd.amsterdam/clock.html Thank you. # for i in $(jot 10); do > time sleep 30; > done 0m33.67s real 0m00.00s user 0m00.00s system 0m33.96s real 0m00.00s user 0m00.00s system 0m33.92s real 0m00.00s user 0m00.00s system 0m33.62s real 0m00.00s user 0m00.00s system 0m33.66s real 0m00.00s user 0m00.00s system 0m33.64s real 0m00.00s user 0m00.00s system 0m33.61s real 0m00.00s user 0m00.00s system 0m33.85s real 0m00.00s user 0m00.00s system 0m33.97s real 0m00.00s user 0m00.00s system 0m33.74s real 0m00.00s user 0m00.00s system # -- db
iked(8) bad-ip-version 7 (encap) error after 6.4 upgrade
I am preparing a bug report but just wanted to flag an issue that I discovered after a 6.3 to 6.4 uplift of an iked(8) endpoint. We overlay vxlan(4) on top of iked(8) to provide seamless connectivity to site offices. I have uplifted our test endpoint to 6.4 and discovered that traffic had tanked, basically 99% of packets were being dropped. Investigations showed it isn't an iked(8) issue as the P-t-P traffic is moving as expected and not throwing the error. As soon as you send traffic over the unicast vxlan tunnel, that is when you see the error. Here is a capture from enc0 on the endpoint: 09:14:42.281342 (authentic,confidential): SPI 0xa093378e: ipcomp 192.168.1.1 > 192.168.1.2 cpi 0x0BCE flags 0 next 4 09:14:42.281396 (authentic,confidential): SPI 0x0bce: 192.168.1.1.4789 > 192.168.1.2.4789: vxlan 35: 10.1.1.1 > 10.1.1.2: icmp: echo request [tos 0x10] (encap) 09:14:42.281430 (unprotected): SPI 0x1a63: 192.168.1.2.4789 > 192.168.1.1.4789: vxlan 35: 10.1.1.2 > 10.1.1.1: icmp: echo reply [tos 0x10] (encap) 09:14:42.281631 (authentic,confidential): SPI 0x03096f78: bad-ip-version 7 (encap) Any configuration advice would be appreciated if it isn't a bug. FYI the main termination device is still 6.3#10 Cheers. Jason.
Re: _writes_to_HOME directories in /
On 2018-10-18, Janne Johansson wrote: > Den tors 18 okt. 2018 kl 19:55 skrev schwack : >> >> Was prepping for 6.4 upgrade and noticed a bunch of *_writes_to_HOME >> directories in my root file systyem. (as shown below) >> All created on Sept 16th. Not sure what I might have been doing on the >> system that day. > > "building ports" most likely. And more specifically "building ports as root", please don't do that.
Re: _writes_to_HOME directories in /
Den tors 18 okt. 2018 kl 19:55 skrev schwack : > > Was prepping for 6.4 upgrade and noticed a bunch of *_writes_to_HOME > directories in my root file systyem. (as shown below) > All created on Sept 16th. Not sure what I might have been doing on the system > that day. "building ports" most likely. > Any thoughts on what these directories are, how they got there, and if safe > to delete? > yes. Googling for openbsd writes_to_home points to bsd.port.mk, and the env PORTHOME for which the manpage of bsd.port.mk says: PORTHOME Setting of env variable HOME for most shell invocations. Default will trip ports that try to write into $HOME while building. -- May the most significant bit of your life be positive.
Re: _writes_to_HOME directories in /
On Oct 18, 2018 11:53 AM, schwack wrote: > > Was prepping for 6.4 upgrade and noticed a bunch of *_writes_to_HOME > directories in my root file systyem. (as shown below) > > All created on Sept 16th. Not sure what I might have been doing on the system > that day. > > Any thoughts on what these directories are, how they got there, and if safe > to delete? > > > schwack@skippy:/$ls -al > total 110652 > drwxr-xr-x 27 root wheel 1024 Oct 18 12:47 . > drwxr-xr-x 27 root wheel 1024 Oct 18 12:47 .. > -rw-r--r-- 1 root wheel 578 Apr 1 2017 .cshrc > -rw-r--r-- 1 root wheel 468 Apr 1 2017 .profile > drwxr-xr-x 2 root wheel 512 Mar 24 2018 altroot > drwxr-xr-x 2 root wheel 512 Sep 16 2017 > at-spi2-core-2.22.1_writes_to_HOME > drwxr-xr-x 2 root wheel 512 Sep 16 2017 atk-2.22.0_writes_to_HOME > drwxr-xr-x 2 root wheel 1024 Mar 24 2018 bin > -rw-r--r-- 1 root wheel 82784 Apr 2 2018 boot > -rwx-- 1 root wheel 12169910 Oct 18 12:44 bsd > -rwx-- 1 root wheel 12163202 Sep 3 07:54 bsd.booted > -rwx-- 1 root wheel 10984685 Sep 4 2017 bsd.mp > -rw-r--r-- 1 root wheel 8777021 Oct 11 16:02 bsd.rd > drwxr-xr-x 2 root wheel 512 Sep 16 2017 colord-1.3.3_writes_to_HOME > drwxr-xr-x 3 root wheel 19456 Oct 18 12:44 dev > drwxr-xr-x 27 root wheel 2048 May 27 21:14 etc > drwxr-xr-x 2 root wheel 512 Sep 16 2017 > gdk-pixbuf-2.36.6_writes_to_HOME > drwxr-xr-x 3 root wheel 512 Sep 16 2017 > gobject-introspection-1.50.0_writes_to_HOME > drwxr-xr-x 2 root wheel 512 Sep 16 2017 > gsettings-desktop-schemas-3.22.0_writes_to_HOME > drwxr-xr-x 3 root wheel 512 Sep 16 2017 gtk+-2.24.31_writes_to_HOME > drwxr-xr-x 3 root wheel 512 Sep 16 2017 gtk+-3.22.11_writes_to_HOME > drwxr-xr-x 2 root wheel 512 Sep 16 2017 > harfbuzz-1.4.5_writes_to_HOME > drwxr-xr-x 3 root wheel 512 Mar 24 2018 home > drwxr-xr-x 2 root wheel 512 Sep 16 2017 > json-glib-1.2.8_writes_to_HOME > drwxr-xr-x 2 root wheel 512 Sep 16 2017 > librsvg-2.40.16_writes_to_HOME > drwxr-xr-x 3 root wheel 512 Sep 16 2017 > libsoup-2.56.0_writes_to_HOME > drwxr-xr-x 2 root wheel 512 Mar 24 2018 mnt > -rwx-- 1 root wheel 12271743 Mar 20 2018 obsd > drwxr-xr-x 3 root wheel 512 Sep 16 2017 pango-1.40.4_writes_to_HOME > drwxr-xr-x 3 root wheel 512 Sep 16 2017 polkit-0.113_writes_to_HOME > drwx-- 3 root wheel 512 Mar 24 2018 root > drwxr-xr-x 2 root wheel 1536 Jun 16 13:17 sbin > lrwxrwx--- 1 root wheel 11 Mar 24 2018 sys -> usr/src/sys > drwxrwxrwt 6 root wheel 512 Oct 18 12:44 tmp > drwxr-xr-x 17 root wheel 512 Mar 24 2018 usr > drwxr-xr-x 24 root wheel 512 Mar 24 2018 var > Are they some sort of core file?
Re: _writes_to_HOME directories in /
Hello, Did you have a full partition at some moment ? I had the same, as far as I remember I had a partition full at some point. Regards Le jeudi 18 octobre 2018 à 19:55:49 UTC+2, schwack a écrit : Was prepping for 6.4 upgrade and noticed a bunch of *_writes_to_HOME directories in my root file systyem. (as shown below) All created on Sept 16th. Not sure what I might have been doing on the system that day. Any thoughts on what these directories are, how they got there, and if safe to delete? schwack@skippy:/$ls -al total 110652 drwxr-xr-x 27 root wheel 1024 Oct 18 12:47 . drwxr-xr-x 27 root wheel 1024 Oct 18 12:47 .. -rw-r--r-- 1 root wheel 578 Apr 1 2017 .cshrc -rw-r--r-- 1 root wheel 468 Apr 1 2017 .profile drwxr-xr-x 2 root wheel 512 Mar 24 2018 altroot drwxr-xr-x 2 root wheel 512 Sep 16 2017 at-spi2-core-2.22.1_writes_to_HOME drwxr-xr-x 2 root wheel 512 Sep 16 2017 atk-2.22.0_writes_to_HOME drwxr-xr-x 2 root wheel 1024 Mar 24 2018 bin -rw-r--r-- 1 root wheel 82784 Apr 2 2018 boot -rwx-- 1 root wheel 12169910 Oct 18 12:44 bsd -rwx-- 1 root wheel 12163202 Sep 3 07:54 bsd.booted -rwx-- 1 root wheel 10984685 Sep 4 2017 bsd.mp -rw-r--r-- 1 root wheel 8777021 Oct 11 16:02 bsd.rd drwxr-xr-x 2 root wheel 512 Sep 16 2017 colord-1.3.3_writes_to_HOME drwxr-xr-x 3 root wheel 19456 Oct 18 12:44 dev drwxr-xr-x 27 root wheel 2048 May 27 21:14 etc drwxr-xr-x 2 root wheel 512 Sep 16 2017 gdk-pixbuf-2.36.6_writes_to_HOME drwxr-xr-x 3 root wheel 512 Sep 16 2017 gobject-introspection-1.50.0_writes_to_HOME drwxr-xr-x 2 root wheel 512 Sep 16 2017 gsettings-desktop-schemas-3.22.0_writes_to_HOME drwxr-xr-x 3 root wheel 512 Sep 16 2017 gtk+-2.24.31_writes_to_HOME drwxr-xr-x 3 root wheel 512 Sep 16 2017 gtk+-3.22.11_writes_to_HOME drwxr-xr-x 2 root wheel 512 Sep 16 2017 harfbuzz-1.4.5_writes_to_HOME drwxr-xr-x 3 root wheel 512 Mar 24 2018 home drwxr-xr-x 2 root wheel 512 Sep 16 2017 json-glib-1.2.8_writes_to_HOME drwxr-xr-x 2 root wheel 512 Sep 16 2017 librsvg-2.40.16_writes_to_HOME drwxr-xr-x 3 root wheel 512 Sep 16 2017 libsoup-2.56.0_writes_to_HOME drwxr-xr-x 2 root wheel 512 Mar 24 2018 mnt -rwx-- 1 root wheel 12271743 Mar 20 2018 obsd drwxr-xr-x 3 root wheel 512 Sep 16 2017 pango-1.40.4_writes_to_HOME drwxr-xr-x 3 root wheel 512 Sep 16 2017 polkit-0.113_writes_to_HOME drwx-- 3 root wheel 512 Mar 24 2018 root drwxr-xr-x 2 root wheel 1536 Jun 16 13:17 sbin lrwxrwx--- 1 root wheel 11 Mar 24 2018 sys -> usr/src/sys drwxrwxrwt 6 root wheel 512 Oct 18 12:44 tmp drwxr-xr-x 17 root wheel 512 Mar 24 2018 usr drwxr-xr-x 24 root wheel 512 Mar 24 2018 var
_writes_to_HOME directories in /
Was prepping for 6.4 upgrade and noticed a bunch of *_writes_to_HOME directories in my root file systyem. (as shown below) All created on Sept 16th. Not sure what I might have been doing on the system that day. Any thoughts on what these directories are, how they got there, and if safe to delete? schwack@skippy:/$ls -al total 110652 drwxr-xr-x 27 root wheel 1024 Oct 18 12:47 . drwxr-xr-x 27 root wheel 1024 Oct 18 12:47 .. -rw-r--r-- 1 root wheel 578 Apr 1 2017 .cshrc -rw-r--r-- 1 root wheel 468 Apr 1 2017 .profile drwxr-xr-x 2 root wheel 512 Mar 24 2018 altroot drwxr-xr-x 2 root wheel 512 Sep 16 2017 at-spi2-core-2.22.1_writes_to_HOME drwxr-xr-x 2 root wheel 512 Sep 16 2017 atk-2.22.0_writes_to_HOME drwxr-xr-x 2 root wheel 1024 Mar 24 2018 bin -rw-r--r-- 1 root wheel 82784 Apr 2 2018 boot -rwx-- 1 root wheel 12169910 Oct 18 12:44 bsd -rwx-- 1 root wheel 12163202 Sep 3 07:54 bsd.booted -rwx-- 1 root wheel 10984685 Sep 4 2017 bsd.mp -rw-r--r-- 1 root wheel 8777021 Oct 11 16:02 bsd.rd drwxr-xr-x 2 root wheel 512 Sep 16 2017 colord-1.3.3_writes_to_HOME drwxr-xr-x 3 root wheel 19456 Oct 18 12:44 dev drwxr-xr-x 27 root wheel 2048 May 27 21:14 etc drwxr-xr-x 2 root wheel 512 Sep 16 2017 gdk-pixbuf-2.36.6_writes_to_HOME drwxr-xr-x 3 root wheel 512 Sep 16 2017 gobject-introspection-1.50.0_writes_to_HOME drwxr-xr-x 2 root wheel 512 Sep 16 2017 gsettings-desktop-schemas-3.22.0_writes_to_HOME drwxr-xr-x 3 root wheel 512 Sep 16 2017 gtk+-2.24.31_writes_to_HOME drwxr-xr-x 3 root wheel 512 Sep 16 2017 gtk+-3.22.11_writes_to_HOME drwxr-xr-x 2 root wheel 512 Sep 16 2017 harfbuzz-1.4.5_writes_to_HOME drwxr-xr-x 3 root wheel 512 Mar 24 2018 home drwxr-xr-x 2 root wheel 512 Sep 16 2017 json-glib-1.2.8_writes_to_HOME drwxr-xr-x 2 root wheel 512 Sep 16 2017 librsvg-2.40.16_writes_to_HOME drwxr-xr-x 3 root wheel 512 Sep 16 2017 libsoup-2.56.0_writes_to_HOME drwxr-xr-x 2 root wheel 512 Mar 24 2018 mnt -rwx-- 1 root wheel 12271743 Mar 20 2018 obsd drwxr-xr-x 3 root wheel 512 Sep 16 2017 pango-1.40.4_writes_to_HOME drwxr-xr-x 3 root wheel 512 Sep 16 2017 polkit-0.113_writes_to_HOME drwx-- 3 root wheel 512 Mar 24 2018 root drwxr-xr-x 2 root wheel 1536 Jun 16 13:17 sbin lrwxrwx--- 1 root wheel11 Mar 24 2018 sys -> usr/src/sys drwxrwxrwt 6 root wheel 512 Oct 18 12:44 tmp drwxr-xr-x 17 root wheel 512 Mar 24 2018 usr drwxr-xr-x 24 root wheel 512 Mar 24 2018 var
Re: 6.4 available but sources incorrect
Den tors 18 okt. 2018 kl 15:37 skrev Peter J. Philipp : > > Hi, > > I know the announcement hasn't made it out yet afaik. But I want to give > notice that on ftp.eu as well as cdn mirrors the sources don't check out. > For one the key is the old 6.3 key and then it fails to signify. > > pub -x SHA256.sig-tgz ports.tar.gz > < > Signature Verified > ports.tar.gz: FAIL > upsilon$ rm *gz > upsilon$ ls > SHA256.sig install64.iso > > I'm holding off on installing until this is fixed. Thanks! The amd64 > binaries > at least in the .iso from ftp.eu checked out fine on the 64 key. New SHA256.sig out on ftp.eu. mirror now. -- May the most significant bit of your life be positive.
6.4 available but sources incorrect
Hi, I know the announcement hasn't made it out yet afaik. But I want to give notice that on ftp.eu as well as cdn mirrors the sources don't check out. For one the key is the old 6.3 key and then it fails to signify. pub -x SHA256.sig-tgz ports.tar.gz< Signature Verified ports.tar.gz: FAIL upsilon$ rm *gz upsilon$ ls SHA256.sig install64.iso I'm holding off on installing until this is fixed. Thanks! The amd64 binaries at least in the .iso from ftp.eu checked out fine on the 64 key. Regards, -peter
