Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0

Tom, A virtual machine setup is an operating system running on an operating system on top of an operating system. OK, not quite. The middle one, the VM itself, is as a bit less complex than a full operating system as machine-independent code goes, but nevertheless the machine-dependent

Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0

Hello Mike just to follow up the issue seems to still occur with the kern.timecounter hardware set to i8254 sysctl kern.timecounter kern.timecounter.tick=1 kern.timecounter.timestepwarnings=0 kern.timecounter.hardware=i8254 kern.timecounter.choice=i8254(0) acpihpet0(1000) acpitimer0(1000)

Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0

Hi Mike Just to say the gaps in ping response seems get worse as the uptime increases ie with the uptime around 5 minutes the gaps between ping results are around 1 sec (what I consider normal) with the uptime around 2 hrs 45 minutes the gaps between ping results are 13 sec with the uptime 8 hrs

Re: mandoc output paper size

Hi Jan, Jan Stary wrote on Thu, Oct 26, 2017 at 09:31:38PM +0200: In the ps file generated by mandoc you should have this line: %%DocumentMedia: Default 595 841 0 () () Where 595 841 correspond to A4. If you set output paper to "letter" that line will say:

Re: mandoc output paper size

Hi Jan, Jan Stary wrote on Thu, Oct 26, 2017 at 10:39:20AM +0200: > This is -current/amd64. My /etc/man.conf in its entirety is 'output > paper a4'. The A4 paper size is what we mostly use around these > parts; otherwise I would not even have a man.conf of course. > > I am not sure whether man

Re: mandoc output paper size

> > > In the ps file generated by mandoc you should have this line: > > > > > > %%DocumentMedia: Default 595 841 0 () () > > > > > > Where 595 841 correspond to A4. If you set output paper to "letter" > > > that line will say: > > > > > > %%DocumentMedia: Default 612 790 0 () () Yes. It

Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0

On Thu, Oct 26, 2017 at 19:05 +0100, Tom Smyth wrote: > Lads, > > Im pleased to say that my testing of OpenBSD 6.1 and OpenBSD 6.2 > Release > amd64 , > appear to work a little better in Proxmox PVE5.1 as released this week, > > I used iso version 5.1-722cc488-1 from Proxmox > Updated on 24

Re: testing cabling and NIC hardware with one machine

On 10/25/17 10:20 PM, Tony Sarendal wrote: Configure the interfaces into separate rdomains. /T Yup that works. For sure I know the packets are traveling along the wire using rdomains now. But I wonder how much of the RTT on each packet is due to the kernel/driver/rdomain code now. And also

Sent here by mistake (instead to bugs@) Sorry!

In article Walter Alejandro Iglesias wrote: > Hi Ruben, > > In article > Ruben > Miller wrote: > > In article > >

Re: cwm 6.2: Windows losing focus while cycling (ALT-TAB)

Hi Ruben, In article Ruben Miller wrote: > In article > Ruben Miller wrote: > >The speed is not a problem, since

Re: mandoc output paper size

Hi Walter, Walter Alejandro Iglesias wrote on Thu, Oct 26, 2017 at 05:11:10PM +0200: > https://www.gnu.org/software/gv/manual/gv.html\ > #Paper-Keywords-and-paper-size-in-points Mandoc uses the exact paper size as specified by ISO 216 in millimeters: A3 297 x 420 A4 210 x 297 A5 148

Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0

Lads, Im pleased to say that my testing of OpenBSD 6.1 and OpenBSD 6.2 Release amd64 , appear to work a little better in Proxmox PVE5.1 as released this week, I used iso version 5.1-722cc488-1 from Proxmox Updated on 24 October 2017 The Console no longer freezes but after a few hours the

6.2: dhclient -L option appends, not overwrites

I just upgraded from 6.1 to 6.2 (amd64) and I'm noticing a differing behavior with dhclient. I use the -L option to write out the offered and effective leases. With 6.1, when a lease was renewed, the -L lease file was overwritten with the new information. With 6.2, when a lease is renewed, it

Re: mandoc output paper size

On Thu, Oct 26, 2017 at 07:24:43PM +0200, Ingo Schwarze wrote: > Hi Walter, > > Walter Alejandro Iglesias wrote on Thu, Oct 26, 2017 at 05:44:16PM +0200: > > > I have files generated with GNU roff that defaults to letter size. > > That's the upstream (GNU troff) default when you compile GNU

Re: mandoc output paper size

Hi Amelia, Amelia A Lewis wrote on Thu, Oct 26, 2017 at 10:41:55AM -0400: > On Thu, 26 Oct 2017 16:14:36 +0200 (CEST), Walter Alejandro Iglesias wrote: >> In the ps file generated by mandoc you should have this line: >> >> %%DocumentMedia: Default 595 841 0 () () >> >> Where 595 841

Re: mandoc output paper size

Hi Walter, Walter Alejandro Iglesias wrote on Thu, Oct 26, 2017 at 05:44:16PM +0200: > I have files generated with GNU roff that defaults to letter size. That's the upstream (GNU troff) default when you compile GNU troff from the git repository with automake and autoconf. If i understand

Re: mandoc output paper size

Answering myself. In article Walter Alejandro Iglesias wrote: > As a side note. You made me realize of something I didn't notice when > I migrated to openbsd; I have files generated with GNU roff that > defaults to letter size. This

Re: mandoc output paper size

In article <20171026104155982590.bfb59...@talsever.com> Amelia A Lewis wrote: > On Thu, 26 Oct 2017 16:14:36 +0200 (CEST), Walter Alejandro Iglesias > wrote: > > In the ps file generated by mandoc you should have this line: > > > > %%DocumentMedia: Default 595 841 0 ()

Re: macpro boot openbsd 6.2 , but ,,,

hi at noon i attach old and cheap "ATI Radeon HD 2400 XT" insted of " nvidea Geforce GT 7300" , then lumina works well . at present i use manjarolinux's grub to boot openbsd . but this method is impossible to reproduce ( i do not know why ) . this morning i install [ *i686* mint linux ] to

Re: mandoc output paper size

On Thu, 26 Oct 2017 16:14:36 +0200 (CEST), Walter Alejandro Iglesias wrote: > In the ps file generated by mandoc you should have this line: > > %%DocumentMedia: Default 595 841 0 () () > > Where 595 841 correspond to A4. If you set output paper to "letter" > that line will say: > >

Re: mandoc output paper size

On 10/26/2017 02:25 PM, Jan Stary wrote: > On Oct 26 11:36:45, w...@roquesor.com wrote: >> In article <20171026083919.ga38...@www.stare.cz> Jan Stary >> wrote: >>> I am not sure whether man -Tpdf and man -Tps honour the paper size. >> >> I think it does. >> >> I don't have a

Re: mandoc output paper size

In article <20171026122507.ga13...@www.stare.cz> Jan Stary wrote: > On Oct 26 11:36:45, w...@roquesor.com wrote: > > In article <20171026083919.ga38...@www.stare.cz> Jan Stary > > wrote: > > > I am not sure whether man -Tpdf and man -Tps honour the paper size. > >

Re: mandoc output paper size

On Thu, 26 Oct 2017 14:25:07 +0200, Jan Stary wrote: > Yes it does. But why does it say e.g. "y841x595" instead of A4? > (Maybe "A4" is just a shorthand for that, I don't know). I don't think so. If that's the actual target size, it seems to be A1. https://en.wikipedia.org/wiki/ISO_216#A_series

Re: mandoc output paper size

On Oct 26 11:36:45, w...@roquesor.com wrote: > In article <20171026083919.ga38...@www.stare.cz> Jan Stary > wrote: > > I am not sure whether man -Tpdf and man -Tps honour the paper size. > > I think it does. > > I don't have a printer at hand to verify it but if in the gv(1)

Re: Chrome crashes with 6.2

I've also seen the problem like this, in fact it may be somewhat tricky sometimes to start chome at all. I've not reported since this is not desktop but server and chrome usage there is just exceptional case. If you are on desktop and you care about chrome health, it would be good if you obtain

Re: Chrome crashes with 6.2

Federico Giannici wrote: > Since I upgraded from OBSD 6.1 to 6.2 (amd64), at least half the time I > launch Chrome it crashes (with a "use after free"). We had a discussion in the ports@ list a couple of days ago: https://marc.info/?t=15085986372=1=2 -- caóc

CUPS and AVAHI (bloatware)

It is well known that cups does not need avahi. Avahi is an option, it requires dbus, which requires X11. If you have a server with limited resources and without X11, you cannot install the present cups package. Please remove cups's dependency on avahi.

Chrome crashes with 6.2

Since I upgraded from OBSD 6.1 to 6.2 (amd64), at least half the time I launch Chrome it crashes (with a "use after free"). Here is an example: casa:/home/giannici> chrome [99256:2090071984:1026/093638.414135:ERROR:process_metrics_openbsd.cc(258)] Not implemented reached in bool

Re: is there something missing in pledge?

On Tue, Oct 24, 2017 at 01:45:42PM +0200, Daniel Hartmeier wrote: > So all an attacker has to do is call pledge() again, with LESS > permissive promises, i.e. giving up getpw? > > #include > #include > > int main() > { > if (pledge("stdio rpath getpw", NULL) == -1) >

Re: pkg_add -u skipping mutt and python

This is because pkgpaths differ from previous versions for both of them. >From pkg_add(1): "To update packages in -u mode, pkg_add performs the following steps. [...] 4. Candidates are then matched according to their pkgpaths in order to weed out similar packages with distinct options." In

Re: mandoc output paper size

In article <20171026083919.ga38...@www.stare.cz> Jan Stary wrote: > I am not sure whether man -Tpdf and man -Tps honour the paper size. I think it does. I don't have a printer at hand to verify it but if in the gv(1) menu I select alternativelly A4 (or Letter) and Default I can

mandoc output paper size

This is -current/amd64. My /etc/man.conf in its entirety is 'output paper a4'. The A4 paper size is what we mostly use around these parts; otherwise I would not even have a man.conf of course. I am not sure whether man -Tpdf and man -Tps honour the paper size. man -Tpdf sox > man.pdf man

pkg_add -u skipping mutt and python

I'd appreciate any input on how several of my systems could have ended up with this pkg_add behaviour of not properly updating packages: # uname -a OpenBSD lamb.my.domain 6.2 GENERIC#132 amd64 # cat /etc/installurl

Re: PDF produced by mandoc

Hi Ingo, > > > This is current/amd64. I just produced a pdf of bc(1) with > > "man -Tpdf bc > bc.pdf". > > > > Trying to view that pdf with mupdf(1) complains thusly: > > (I can view and print the PDF fine though) > > > > warning: expected 'endobj' or 'stream' keyword (27 0 R) > >