On Mon, 27 Jan 2020, Paul de Weerd wrote:
> Hi all,
>
> Following up from my previous (PEBKAC) issue[1], I kept working on my
> ruleset. I found, what I believe to be, another issue. Here's the
> reduced ruleset that reproduces the problem:
> [snip details]
>
> The problem is in the IPv6
I've just updated to the latest snap, and now every SSH connection I
make is asking me to accept updated hostkeys.
$ ssh somehost
Learned new hostkey: RSA SHA256:
Learned new hostkey: ED25519 SHA256:
Accept updated hostkeys? (yes/no):
I see that some changes have been occurring
I generally do this on a user level with some editors like emacs,
cuz I run spacemacs which is prone to crashes, cuz of over 9000 plugins
Small improvement: Keep a PID file, along with pgrep, because of
multiple emacs-server instances
It has worked a bit better than simple pgrep
If anyone
Irresponsible people like myself have been known to put cron jobs in place to
look for, and if necessary restart crashy daemons.
This could referred to as a kludge, though many would argue that is to mild an
aspersion to cast upon it.
PID=`pgrep gloob`
if [ -z "$PID" ]
then
Hi Patrick,
Patrick Kristiansen wrote on Mon, Jan 27, 2020 at 08:13:28PM +0100:
> Is there something like the FreeBSD daemon(8) command for OpenBSD,
> which can run a process in the background and restart it if it
> crashes?
Absolutely not, we are strongly convinced this is an utterly stupid
Hi everyone,
Is there something like the FreeBSD daemon(8) command for OpenBSD, which
can run a process in the background and restart it if it crashes? That
is, is there a command that comes with OpenBSD's base image with these
capabilities? Surprisingly, Google hasn't revealed anything useful to
Joel Carnat(j...@carnat.net) on 2020.01.27 18:21:43 +0100:
> Hi,
>
> I'm setting up an HTTP(S) Reverse Proxy with relayd(8).
>
> I have one listener with multiple FQDN allowed.
> But I also have a common path that must be treated separately.
>
> As for now, I have:
> http protocol "https" {
>
Hi,
I'm setting up an HTTP(S) Reverse Proxy with relayd(8).
I have one listener with multiple FQDN allowed.
But I also have a common path that must be treated separately.
As for now, I have:
http protocol "https" {
match request header "Host" value "one.domain.local" forward to
match
On Mon, 27 Jan 2020 at 13:59, Justin Noor wrote:
>
> Hello community,
>
> I'm looking for any advice on how to troubleshoot some strange and
> catastrophic behavior on my OpenBSD machine. Seemingly out of nowhere, it
> started freezing to the extent that only a forced shutdown (holding down
> the
A full dmesg would certainly help. Also, do you see anything in
/var/log/messages?
On Mon, Jan 27, 2020 at 4:01 PM Justin Noor wrote:
>
> Hello community,
>
> I'm looking for any advice on how to troubleshoot some strange and
> catastrophic behavior on my OpenBSD machine. Seemingly out of
Hello community,
I'm looking for any advice on how to troubleshoot some strange and
catastrophic behavior on my OpenBSD machine. Seemingly out of nowhere, it
started freezing to the extent that only a forced shutdown (holding down
the power button) gets me out of it. I suspect it's some kind of
Hi all,
Following up from my previous (PEBKAC) issue[1], I kept working on my
ruleset. I found, what I believe to be, another issue. Here's the
reduced ruleset that reproduces the problem:
[root@ferrari] # cat pf.tmp
IntIF=em1
# only allow DNS to the unbound instance listening on em1 (v4 and
12 matches
Mail list logo