On Sun, 28 Mar 2021, Stuart Henderson wrote:
It is something that could possibly be caused by bad hardware or a
glitch in the power feed amongst other options (the latter may affect
some machines differently than others)..
I've had a string of power "blips" over the last year or so. Oddly
Hi Stefan!
sorry for the even longer delay - but dayjob was demanding, working
even on sunday.
However, if you can read this message, it means that I am connected
through the internal ipw card to WEP WiFi at the first attempt.
Wonderful. Great work, Stefan,
Both patches together applied,
Ax0n writes:
> I initially noticed it when I hopped in a video room on Discord in Firefox
> and folks could see me and I could hear them, but Discord got no audio. It
> turns out, nothing gets any audio. sysctl has audio and video recording
> enabled, and pledge/unveil has been tweaked just a
On 2021-03-28, David Newman wrote:
> On 3/28/21 4:58 AM, Kristjan Komloši wrote:
>
>> On 3/27/21 10:27 PM, David Newman wrote:
>>> OpenBSD 6.8 GENERIC#5 i386
>>>
>>> One of my systems rebooted at 03:01 local time today. I've seen kernel
>>> panics and bad hardware but I've never seen OpenBSD
On Sun, Mar 28, 2021 at 05:58:31PM +0200, Riccardo Mottola wrote:
> However, if you can read this message, it means that I am connected through
> the internal ipw card to WEP WiFi at the first attempt. Wonderful. Great
> work, Stefan,
Great, thank you for confirming! I have committed the fix.
I initially noticed it when I hopped in a video room on Discord in Firefox
and folks could see me and I could hear them, but Discord got no audio. It
turns out, nothing gets any audio. sysctl has audio and video recording
enabled, and pledge/unveil has been tweaked just a little for firefox to
On 3/28/21 4:58 AM, Kristjan Komloši wrote:
> On 3/27/21 10:27 PM, David Newman wrote:
>> OpenBSD 6.8 GENERIC#5 i386
>>
>> One of my systems rebooted at 03:01 local time today. I've seen kernel
>> panics and bad hardware but I've never seen OpenBSD "just reboot" by
>> itself, ever.
>>
>> There's
On 2021-03-28 18:56, Omar Polo wrote:
Thanks Omar, I like this approach! I'm pretty green to C so this is
what I have (which doesn't work):
#include
int main(void) {
execl("/bin/lowdown", NULL);
}
There is no HTML render but at least no errors, but cgit
On 2021-03-28 18:14, Omar Polo wrote:
Paul W. Rankin writes:
The cgit about-filter doesn't want an executable to do e.g. the
Markdown conversation, rather it wants a script that will return the
command to perform this, e.g.:
#!/bin/sh
case "$1" in
(*.md) exec
On 2021-03-28 15:37, Paul W. Rankin wrote:
I'm running cgit with httpd + slowcgi and can't seem to get the
about-filter to work. Both httpd and slowcgi run in the default chroot
of /var/www.
I've compiled lowdown with "-static -pie" to /var/www/bin/lowdown
(chroot /bin/lowdown) with
On 3/27/21 10:27 PM, David Newman wrote:
OpenBSD 6.8 GENERIC#5 i386
One of my systems rebooted at 03:01 local time today. I've seen kernel
panics and bad hardware but I've never seen OpenBSD "just reboot" by
itself, ever.
There's no cron job that would do this. last(1) is no help; it shows the
On 2021-03-28, Kristaps Dzonsons wrote:
$ cat < my-cgit-filter.c
#include
int
main(void)
{
execl("/bin/lowdown", "lowdown", NULL);
return 1;
}
EOF
So essentially all this is doing is stripping off the command line
arguments.
$ cc
$ cat < my-cgit-filter.c
#include
int
main(void)
{
execl("/bin/lowdown", "lowdown", NULL);
return 1;
}
EOF
$ cc my-cgit-filter.c -o my-cgit-filter.c -static
Instead of downloading, recompiling, and installing lowdown; then
building and installing a program that execs the
Paul W. Rankin writes:
> On 2021-03-28 18:56, Omar Polo wrote:
>>> Thanks Omar, I like this approach! I'm pretty green to C so this is
>>> what I have (which doesn't work):
>>> #include
>>> int main(void) {
>>> execl("/bin/lowdown", NULL);
>>> }
>>> There is no HTML
Paul W. Rankin writes:
> On 2021-03-28 18:14, Omar Polo wrote:
>> Paul W. Rankin writes:
>>> The cgit about-filter doesn't want an executable to do e.g. the
>>> Markdown conversation, rather it wants a script that will return the
>>> command to perform this, e.g.:
>>> #!/bin/sh
>>>
Hello,
I've build a python3 deamon which look for specific patterns in any log file.
For each of those patterns you assign a weight. Once the max weight is reached
in a period of time the associated IP is added to a pf table for a certain
amount of time (1 day typically but can be changed).
16 matches
Mail list logo
