Re: Unresolvable loghost FQDNs in syslog.conf

[Edgar Pettijohn]

On 16-08-15 14:01:51, Darren S. wrote:
> Hoping to verify expected behavior of unresolvable FQDNs for remote
> loghosts in syslog.conf(5).
> 
> *.notice;auth,authpriv,cron,ftp,kern,lpr,mail,user.none
> @loghost.example.com
> auth,daemon,syslog,user.info;authpriv,kern.debug
> @loghost.example.com
> 
> In the above configuration, if loghost.example.com cannot be resolved,
> is it expected that syslogd(8) should detect this and log a warning,

If in debug it will warn you.

> or exit with an error, or proceed to run normally and simply fail to
> log to the remote host?

It should proceed normally as you could have it logging to file as well.  

> 
> Looking at a case in 5.8 (amd64) where the latter seems to be
> happening after the log host was recently updated in DNS with a new
> hostname but configuration update was missed on log clients. Wondering
> if this is bug or feature (or if I've missed something).
> 
> Regards,
> 
> -- 
> Darren Spruell
> phatbuck...@gmail.com
> 

-- 
Edgar Pettijohn

[Job] Senior Firewall Technician in Edinburgh, Scotland

[Craig Skinner]

I've no connection, but thought it might be of interest to others:

http://www.JobServe.Co.UK/Ep1qJ

British jobs are often 37hours/wk, ~30 days paid holiday & monthly pay.

Unresolvable loghost FQDNs in syslog.conf

[Darren S.]

Hoping to verify expected behavior of unresolvable FQDNs for remote
loghosts in syslog.conf(5).

*.notice;auth,authpriv,cron,ftp,kern,lpr,mail,user.none
@loghost.example.com
auth,daemon,syslog,user.info;authpriv,kern.debug
@loghost.example.com

In the above configuration, if loghost.example.com cannot be resolved,
is it expected that syslogd(8) should detect this and log a warning,
or exit with an error, or proceed to run normally and simply fail to
log to the remote host?

Looking at a case in 5.8 (amd64) where the latter seems to be
happening after the log host was recently updated in DNS with a new
hostname but configuration update was missed on log clients. Wondering
if this is bug or feature (or if I've missed something).

Regards,

-- 
Darren Spruell
phatbuck...@gmail.com

Re: Driving 4k Display for OpenBSD Workstation

[Bryan Vyhmeister]

I neglected one solution to having a 4k Display with OpenBSD. I was
reading about Haswell and 4k in context of the Mac mini which uses a low
power series of processors that do not support 4k at 60 Hz. The regular
Haswell chips like the Xeon E3 1275 v3 I am using now, do support 4k at
60 Hz using DisplayPort. My Dell P4317Q seems to be working fine at 4k
with inteldrm(4) and this processor. Thanks for the suggestions.

I will also test my Skylake build with efifb(4) and wsfb(4) once my Xeon
E3 1275 v5 arrives in a few days but I suspect it will be very slow as
has been predicted.

Bryan

Re: ifconfig(8) display aliases by default

[Theo de Raadt]

> Is there any reason why ifconfig(8) do not display IPv4 aliases by default ?
> If there isn't, I can send a patch to make it the default behaviour.

that is intentional.

ifconfig(8) display aliases by default

[Denis Fondras]

Hello,

Is there any reason why ifconfig(8) do not display IPv4 aliases by default ?
If there isn't, I can send a patch to make it the default behaviour.

Denis

Re: 5.9: vmx0: device timeout

[Kurt Mosiejczuk]

On Sat, Aug 13, 2016 at 03:40:28PM +0200, mxb wrote:


> > On 11 aug. 2016, at 21:44, Kurt Mosiejczuk  wrote:

> > I've noticed that for 5.9, any VMs (in VMware) using vmx(4), end up putting
> > "vmx0: device timeout" into the dmesg a bunch when under network load.

> > I switched one of the VMs to vic(4) and the messages stop.  Another VM that
> > I haven't gotten to upgrading from 5.8 to 5.9 yet doesn't show this in its
> > dmesg and it's our reasonably busy web server.

> > Anyone else see this?  I noticed there were a bunch of changes to vmx(4)
> > after 5.8 as part of the network mpsafe work.

> > dmesg below.

> Hey,
> it would be nice to define ???network load???.
> I have several VMs running 5.8-stable/5.9-stable/current without seeing this.

I was easily able to duplicate it when doing an rsync backup to another
server.  That's when I looked at my IMAP server and noticed it had the
same complaint in the dmesg (and have since switched that to vic(4)).

Does that describe it better?

--Kurt

Re: problem trying to import a 3.4m database with phpmyadmin

[STeve Andre']

Well guess what--I fixed it.

In /etc/php5-6.ini, a semi-colon is used for comment lines.
I used a colon.

It misparses things when you do that.  Silently.

I need to clean my eyeballs now...

Sorry for the noise, but at least you can remember this.
(reason 416 to not be crazy about php...)

--STeve Andre'

On 08/15/16 05:41, STeve Andre' wrote:

   This is on an amd64 -current system updated/compiled as of

Aug 8 7am; using the 8/13 packages.


I'm trying to use phpMyAdmin to import a database into maria.

in /etc/php-5.6ini I've set memory_limit to 256m, post_max_size

to 16m and upload_max_filesize to 8m.


The db I'm trying to import is 3.4m.  Under import in phpmyadmin

it says (max 2,048k) for importing, hence my doing what php faq

1.16 said about the above three params in php.ini.


Now I notice that suhosin says in /var/log/messages

 ALERT - script tried to disable memory_limit by setting it to a 
negative value -1 bytes which is not allowed (attacker '10.0.0.5', 
file '/u/php/www/import.php', line 296)



So, I am wondering how suhosin is seeing this, and how one gets

phpmyadmin to deal with > 2M files.  That is always says 2,048K

says I'm not changing things correctly?  I've restarted apache and

even rebooted but I always get the 2M max notice.


Any ideas?  I'm pressed for time on this, sigh.  Pointers would be

much appreciated.


--STeve Andre'

problem trying to import a 3.4m database with phpmyadmin

[STeve Andre']

   This is on an amd64 -current system updated/compiled as of

Aug 8 7am; using the 8/13 packages.


I'm trying to use phpMyAdmin to import a database into maria.

in /etc/php-5.6ini I've set memory_limit to 256m, post_max_size

to 16m and upload_max_filesize to 8m.


The db I'm trying to import is 3.4m.  Under import in phpmyadmin

it says (max 2,048k) for importing, hence my doing what php faq

1.16 said about the above three params in php.ini.


Now I notice that suhosin says in /var/log/messages

 ALERT - script tried to disable memory_limit by setting it to a 
negative value -1 bytes which is not allowed (attacker '10.0.0.5', file 
'/u/php/www/import.php', line 296)



So, I am wondering how suhosin is seeing this, and how one gets

phpmyadmin to deal with > 2M files.  That is always says 2,048K

says I'm not changing things correctly?  I've restarted apache and

even rebooted but I always get the 2M max notice.


Any ideas?  I'm pressed for time on this, sigh.  Pointers would be

much appreciated.


--STeve Andre'