Re: radeondrm failure on amd64 but not on i386?

2018-11-16 Thread Jonathan Gray
On Thu, Nov 15, 2018 at 09:15:48PM -0700, Andy Bradford wrote: > Hello, > > I recently installed OpenBSD 6.4 amd64 and radeondrm fails to load > properly. I then installed OpenBSD 6.4 i386 on the same hardware (to a > USB pendrive) and it works fine. Any ideas? There are many ways of gett

isc bind - error sending response: would block

2018-11-16 Thread Paul B. Henson
I recently updated a couple servers that were running OpenBSD 6.3 with bind 9.11.3 to OpenBSD 6.4 and bind 9.11.4pl2. Since then, I'm been getting a large number of "error sending response: would block" log messages: Nov 15 11:03:58 lisa named[79587]: client @0x6f2f02bc440 10.128.30.77#65198 (p64

Re: Vacation with smtpd doesn't work in 6.4

2018-11-16 Thread Martin Sukany
You're right, thanks. I set it up this way as I noticed similar behaviour in some bigger providers ... - changed now back to meet 2487. M> On 11/16/18 6:43 PM, Penty Wenngren wrote: On Fri, Nov 16, 2018 at 05:54:13PM +0100, Martin Sukany wrote: Hello Craig, I don't think so .. I'm just e

Re: Having security patches to packages while running -stable

2018-11-16 Thread Ivan Krylov
> > Does this mean that I should either build the packages from ports > > myself, or use someone else's binary packages (e.g. those from > > m:tier); no other options? > > Yes. Thank you for the answer! -- Best regards, Ivan

Re: Vacation with smtpd doesn't work in 6.4

2018-11-16 Thread Penty Wenngren
On Fri, Nov 16, 2018 at 05:54:13PM +0100, Martin Sukany wrote: > Hello Craig, > > I don't think so .. I'm just enforcing encrypted communication ... :) > > { > > listen on vio0 port25 tls-require auth-optional pki sukany.cz > > } > > M> RFC 2487: A publicly-referenced SMTP server MUST NOT r

Simple case with not obvious solution

2018-11-16 Thread sven falempin
Amazing Readers, In my syslog.conf I put ssllog.my.domain when the computer start syslog is like : meeeh your pppoe has not started yet :-( ; IE: bad hostname @ssllog.my.domain so I have to SIGHUP when network is actually ready. Is there a common way to solve this ( I failed to find one in man

Re: Vacation with smtpd doesn't work in 6.4

2018-11-16 Thread Martin Sukany
Hello Craig, I don't think so .. I'm just enforcing encrypted communication ... :) { listen on vio0 port25 tls-require auth-optional pki sukany.cz } M> On 11/16/18 4:50 PM, Craig Skinner wrote: Martin, your mail server is badly configured (broken):- Begin forwarded message: From: mail

Re: OpenBSD with root FS mounted read only

2018-11-16 Thread Kevin Chadwick
On 11/16/18 3:43 PM, Jarkko Oranen wrote: > As far as I'm aware, they are/were originally separated largely due to > historical reasons anyway, not because it's inherently better to keep > them separate. However they came about it is inherently better. Linux often takes the easy rather than best r

Re: Vacation with smtpd doesn't work in 6.4

2018-11-16 Thread Craig Skinner
Martin, your mail server is badly configured (broken):- Begin forwarded message: From: mailer-dae...@britvault.co.uk (Mail Delivery System) To: skin...@britvault.co.uk Subject: Undelivered Mail Returned to Sender Date: Fri, 16 Nov 2018 12:17:13 + (GMT) This is the mail system at host tea

Re: OpenBSD with root FS mounted read only

2018-11-16 Thread Jarkko Oranen
On Thu, 2018-11-15 at 18:55 +, Kevin Chadwick wrote: > > This kind of demonstrates Lennart Poeterings recent tweet/boast about > unified > /usr to actually be a bad idea likely taken up by Debian out of > frustration and > not desire/design. > Well, to be fair in Linuxland the separation bet

bind and error sending response: would block

2018-11-16 Thread Kapetanakis Giannis
Hi, after upgrading one of my bind (cache resolver) machines to 6.4 (release) I'm getting these errors quite often: Nov 16 15:55:14 server named[30616]: client: warning: client @0x6591da02440 xxx.xxx.xxx.xxx#39702 (a1928.d.akamai.net): error sending response: would block https://kb.isc.org/doc

radeondrm failure on amd64 but not on i386?

2018-11-16 Thread Andy Bradford
Hello, I recently installed OpenBSD 6.4 amd64 and radeondrm fails to load properly. I then installed OpenBSD 6.4 i386 on the same hardware (to a USB pendrive) and it works fine. Any ideas? dmesg for both follow: OpenBSD 6.4 (GENERIC.MP) #364: Thu Oct 11 13:30:23 MDT 2018 dera...@amd6

Re: Vacation with smtpd doesn't work in 6.4

2018-11-16 Thread Martin Sukany
Well, I figured out, that problem is in vacation itself, where is missing proper control of recipient's address. In case, the header of original message contains line like:     From: vacation encloses the message by "<>", so SMTPD then receives sth like:     RCPT TO: <> As a temporary hack,

Re: OpenBSD with root FS mounted read only

2018-11-16 Thread Kevin Chadwick
On 11/15/18 9:53 PM, Stuart Henderson wrote: > well, it's not just time fsck'ing, those checks can fail, and then if > you don't have OOB you have to go visit the machine .. I assume sync doesn't solve that entirely?

Re: OpenBSD with root FS mounted read only

2018-11-16 Thread Kevin Chadwick
On 11/16/18 10:06 AM, Daniel Polak wrote: >>> The main benefit of read-only is not having to do disk checks but the time  >>> for >>> root is negligible. >> well, it's not just time fsck'ing, those checks can fail, and then if >> you don't have OOB you have to go visit the machine .. True, but the

Re: Changing kern.nprocs and kern.nfiles

2018-11-16 Thread Mik J
These are values recommended by an application I want to install on my Openbsd machine. Since I have a hard time to make it work properly, I want to apply their settings before thightening things I'm still in test mode. Le vendredi 16 novembre 2018 à 12:07:25 UTC+1, Otto Moerbeek a écri

Re: Changing kern.nprocs and kern.nfiles

2018-11-16 Thread Otto Moerbeek
On Fri, Nov 16, 2018 at 10:46:12AM +, Mik J wrote: > Hello, > Thank you to both of you. > I had already changed openfiles-max=65536 in login.conf and > kern.maxproc=16384 in sysctl.conf. > Have a nice day But why? -Otto > > Le vendredi 16 novembre 2018 à 11:18:42 UTC+1, Otto

Re: Changing kern.nprocs and kern.nfiles

2018-11-16 Thread Mik J
Hello, Thank you to both of you. I had already changed openfiles-max=65536 in login.conf and kern.maxproc=16384 in sysctl.conf. Have a nice day Le vendredi 16 novembre 2018 à 11:18:42 UTC+1, Otto Moerbeek a écrit : On Fri, Nov 16, 2018 at 10:55:23AM +0100, Martijn van Duren wrote: >

Re: Changing kern.nprocs and kern.nfiles

2018-11-16 Thread Otto Moerbeek
On Fri, Nov 16, 2018 at 10:55:23AM +0100, Martijn van Duren wrote: > On 11/16/18 10:24 AM, Mik J wrote: > > Hello, > > > > Does anyone know how to change these values ? > > > > # sysctl kern.nprocs=52 > > sysctl: kern.nprocs: Operation not permitted > > # sysctl kern.nfiles=575 > > sysctl: kern.

Re: OpenBSD with root FS mounted read only

2018-11-16 Thread Daniel Polak
Stuart Henderson wrote on 15-11-2018 22:53: On 2018-11-15, Kevin Chadwick wrote: The main benefit of read-only is not having to do disk checks but the time for root is negligible. well, it's not just time fsck'ing, those checks can fail, and then if you don't have OOB you have to go visit th

Re: Changing kern.nprocs and kern.nfiles

2018-11-16 Thread Martijn van Duren
On 11/16/18 10:24 AM, Mik J wrote: > Hello, > > Does anyone know how to change these values ? > > # sysctl kern.nprocs=52 > sysctl: kern.nprocs: Operation not permitted > # sysctl kern.nfiles=575 > sysctl: kern.nfiles: Operation not permitted > > Regards > See sysctl(2): Second level

Changing kern.nprocs and kern.nfiles

2018-11-16 Thread Mik J
Hello, Does anyone know how to change these values ? # sysctl kern.nprocs=52 sysctl: kern.nprocs: Operation not permitted # sysctl kern.nfiles=575 sysctl: kern.nfiles: Operation not permitted Regards