Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Paolo Aglialoro
Thanks for the answer Stuart! Yes, I had created the file 644 root:wheel as listed (mtime is of yesterday I as deleted and recreated it when fiddling before writing to list): $ l /var/log/c2821.log -rw-r--r-- 1 root wheel - 1 May 4 15:43 /var/log/c2821.log $ l /var/log/switch.log -rw-r--r--

Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Stuart Henderson
On 2017-05-04, Paolo Aglialoro wrote: > Hi all, > > I have an internal LAN syslogd server (recently upgraded to 6.1) since a > couple of years. It was successfully logging an old 2611XM cisco router, > now logs a dell switch and the new 2851 cisco router which swapped the old >

OpenBSD 6.1: relayd does not start more than 3 processes

2017-05-05 Thread Maxim Bourmistrov
Hey, on OpenBSD 6.0-stable I have following configuration for relayd: snip——— interval 10 timeout 1200 prefork 15 log all —— Respective login.conf to spawn more relayd procs: relayd:\ :maxproc-max=31:\ :maxproc-cur=15:\ :openfiles=65536:\

Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Allan Streib
> -rw-r--r-- 1 root wheel - 1 May 4 15:43 /var/log/c2821.log ^ [...] > local1.debug/var/log/c2851.log

Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Paolo Aglialoro
Thank you everybody! It was just a stupid typo, yes sometimes it's so hard to see what's in front of the screen Now the router has correctly started logging in the file. I also noticed it's still logging in /var/log/messages, is this correct? Thanks On Fri, May 5, 2017 at 4:38 PM, Peter

Re: OpenBSD 6.1: relayd does not start more than 3 processes

2017-05-05 Thread Andre Ruppert
Hm, I got a relayd-problem with a similar config. 100% CPU load nearly all 10 days with 5.9, same behavior all 3-4 weeks with 6.0. Wrong-ordered relayd.conf too. looks like this when running in trouble: _relayd 33851 100.0 0.1 2004 4496 ?? Rp15Apr17 3363:59.52 relayd: relay

Re: OpenBSD 6.1: relayd does not start more than 3 processes

2017-05-05 Thread Hiltjo Posthuma
On Fri, May 05, 2017 at 12:30:56PM +0200, Maxim Bourmistrov wrote: > > Hey, > on OpenBSD 6.0-stable I have following configuration for relayd: > > snip——— > interval 10 > timeout 1200 > prefork 15 > log all > —— > > Respective login.conf to spawn more relayd procs: > >

Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Peter Hessler
On 2017 May 05 (Fri) at 15:38:36 +0200 (+0200), Paolo Aglialoro wrote: :As written, mtime was due by me recreating the file trying to make things :work, not by syslog. :As of today, in fact, mtime is still unchanged, while output to :/var/log/messages still flowing from router. : : :On Fri, May 5,

Re: OpenBSD 6.1: httpd.conf macro usage and string concatenation

2017-05-05 Thread Edgar Pettijohn
It won't. You only get to set a macro once. It's more for ease of configuration for a variable that will be used multiple times. ⁣Sent from BlueMail ​ On May 5, 2017, 8:11 AM, at 8:11 AM, Torsten wrote: >Hi! > >I thought I could copy the same static server definition block and

Re: OpenBSD 6.1: relayd does not start more than 3 processes

2017-05-05 Thread Maxim Bourmistrov
> 5 maj 2017 kl. 14:41 skrev Hiltjo Posthuma : > > On Fri, May 05, 2017 at 12:30:56PM +0200, Maxim Bourmistrov wrote: >> >> Hey, >> on OpenBSD 6.0-stable I have following configuration for relayd: >> >> snip——— >> interval 10 >> timeout 1200 >> prefork 15 >> log

Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Peter Hessler
The file you were looking at was named c2821.log. This has a '2' in the name. c2851.log is the one you referenced in the config file. it has a '5' in the name. That is what Allan and I were refering to. If the below was exactly how you created the files, then please restart syslogd, to ensure

Re: OpenBSD 6.1: relayd does not start more than 3 processes

2017-05-05 Thread Maxim Bourmistrov
> 5 maj 2017 kl. 15:55 skrev Maxim Bourmistrov : > > >> 5 maj 2017 kl. 14:41 skrev Hiltjo Posthuma : >> >> On Fri, May 05, 2017 at 12:30:56PM +0200, Maxim Bourmistrov wrote: >>> >>> Hey, >>> on OpenBSD 6.0-stable I have following configuration

Intel t7250 cpu and vmm

2017-05-05 Thread Jan Lambertz
Hi, right now (6.1 current amd64) my Intel t7250 CPU is not supported by vmm. Is there any chance this will change in the next months or should i go for new hardware ? Thank you so far for this great Software :-).

Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Paolo Aglialoro
Sorry Peter, what do '2' or '5' stand for? And what does creating a file with '5' mean? This was my procedure: # cat "" > c2851.log # chown root:wheel c2851.log # chmod 644 c2851.log On Fri, May 5, 2017 at 3:46 PM, Peter Hessler wrote: > On 2017 May 05 (Fri) at 15:38:36

Re: OpenBSD 6.1: relayd does not start more than 3 processes

2017-05-05 Thread Florian Ermisch
Am 5. Mai 2017 16:05:09 MESZ schrieb Maxim Bourmistrov : > >> 5 maj 2017 kl. 15:55 skrev Maxim Bourmistrov >: >> >> >>> 5 maj 2017 kl. 14:41 skrev Hiltjo Posthuma : >>> >>> On Fri, May 05, 2017 at 12:30:56PM +0200,

OpenBSD 6.1: httpd.conf macro usage and string concatenation

2017-05-05 Thread Torsten
Hi! I thought I could copy the same static server definition block and only change a unique macro definition at the top of each server. But this is not working: ## # from httpd.conf ## # [...] # macro definition certroot="/etc/ssl/httpd"

Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Paolo Aglialoro
As written, mtime was due by me recreating the file trying to make things work, not by syslog. As of today, in fact, mtime is still unchanged, while output to /var/log/messages still flowing from router. On Fri, May 5, 2017 at 2:27 PM, Allan Streib wrote: > > > -rw-r--r--

Re: OpenBSD/octeon and "OpenBSD/patches/6.0/common/002_perl.patch.sig"

2017-05-05 Thread Doggie
W dniu 2017-05-05 o 00:18, Theo de Raadt pisze: Strange noone else noticed this for so many months. My pleasure :) Anyways, it is not that important. I won't reroll a 6.0 errata for something so minor. We'll keep an eye out for next time. That is fine with me. Thanks, Theo. -- Cheers,

Re: Incorrect file destination when logging with syslogd

2017-05-05 Thread Stuart Henderson
On 2017-05-05, Paolo Aglialoro wrote: > Thank you everybody! > > It was just a stupid typo, yes sometimes it's so hard to see what's in > front of the screen > Now the router has correctly started logging in the file. > > I also noticed it's still logging in

Re: OpenBSD 6.1: relayd does not start more than 3 processes

2017-05-05 Thread Hiltjo Posthuma
On Fri, May 05, 2017 at 04:33:02PM +0200, Florian Ermisch wrote: > > > Am 5. Mai 2017 16:05:09 MESZ schrieb Maxim Bourmistrov > : > > > >> 5 maj 2017 kl. 15:55 skrev Maxim Bourmistrov > >: > >> > >> > >>> 5 maj 2017 kl. 14:41 skrev Hiltjo

Re: Intel t7250 cpu and vmm

2017-05-05 Thread Mike Larkin
On Fri, May 05, 2017 at 03:16:58PM +0200, Jan Lambertz wrote: > Hi, > > right now (6.1 current amd64) my Intel t7250 CPU is not supported by vmm. > Is there any chance this will change in the next months or should i go for > new hardware ? > > Thank you so far for this great Software :-).

Version skew?

2017-05-05 Thread Donald Allen
I am running current on an amd64 system. I updated the system from the latest (5/4) snapshot this morning, downloaded from the Alberta site. But I am (still) unable to install the following package: doas /usr/sbin/pkg_add rust quirks-2.319 signed on 2017-05-03T14:53:25Z Can't install rust-1.16.0

mips64el packages deprecated?

2017-05-05 Thread Roland Kammerer
Hi guys, Today I upgraded to OpenBSD 6.1 and saw that none of the mirrors seem to contain packages for mips64el anymore. For example compare [1] and [2]. Is that intentional? I wonder because mips64el is still in the "Many pre-built packages for each architecture" list[3]. Are they still

Re: mips64el packages deprecated?

2017-05-05 Thread Christian Weisgerber
On 2017-05-05, Roland Kammerer wrote: > Today I upgraded to OpenBSD 6.1 and saw that none of the mirrors seem to > contain packages for mips64el anymore. > > Are they still building? Yes. -- Christian "naddy" Weisgerber na...@mips.inka.de

Re: Version skew?

2017-05-05 Thread Donald Allen
The /etc/installurl file is not present on either of my 'current' systems. Reading the man pages, it looks to me like installurl is related to the new syspatch facility, which I believe is for tracking the STABLE branch. As I said, I'm running CURRENT, so if I've got all this right, the fact that

Re: Version skew?

2017-05-05 Thread Sebastien Marie
On Fri, May 05, 2017 at 02:15:26PM -0400, Donald Allen wrote: > I am running current on an amd64 system. I updated the system from the > latest (5/4) snapshot this morning, downloaded from the Alberta site. > But I am (still) unable to install the following package: > > doas /usr/sbin/pkg_add

Re: Version skew?

2017-05-05 Thread Kapfhammer, Stefan
Hello Donald, PKG_PATH is deprecated since 6.1-RELEASE. Use /etc/installurl instead. https://man.openbsd.org/installurl Freundliche Grüße / Regards -stefan kapfhammer Originalnachricht Von: Donald Allen Gesendet: Freitag, 5. Mai 2017 20:16 An: OpenBSD general usage list Betreff: Version

Re: Version skew?

2017-05-05 Thread Manuel Solis
Hello, Donald Perhaps you should try: 1- doas echo "https://ftp.openbsd.org/pub/OpenBSD; > /etc/installurl (or any other mirror you like) and then again doas pkg_add rust I certainly do not know exactly the process and all stuff, but maybe you should get help in the faq page (

Re: OpenBSD 6.1: httpd.conf macro usage and string concatenation

2017-05-05 Thread Walter Alejandro Iglesias
In article <39c822f4-07f1-3544-0a8e-b75446f94...@4ss.de> you wrote: > Hi! > > I thought I could copy the same static server definition block and only > change a unique macro definition at the top of each server. But this is > not working: > > ## > # from httpd.conf >

Theo opinion of virtual machines

2017-05-05 Thread SOUL_OF_ROOT 55
Theo de Raadt said in the past about virtual machines: >A few of us just spent some time again debugging an application level >problem ... and once again realized that the application was running >on OpenBSD inside the Innobox's VirtualBox VM. >Argh. >http://www.virtualbox.org/ticket/639 >Sun