> Am 11.07.2024 um 04:14 schrieb Mike Fischer :
>
> For now I’ll assume that I have gotten lucky in my tests.
I have just confirmed this assumption. I was able to trigger the problem on a
VirtualHost I had not tried before on the same server with the same browser.
So, I’ll patie
Hi Theo,
> Am 11.07.2024 um 03:47 schrieb Theo Buehler :
>
> On Thu, Jul 11, 2024 at 03:32:20AM +0200, Mike Fischer wrote:
>> Any progress on this?
>>
>> I just updated a server to apache-httpd-2.4.61 (from apache-httpd-2.4.59)
>> and initial testing seems t
Any progress on this?
I just updated a server to apache-httpd-2.4.61 (from apache-httpd-2.4.59) and
initial testing seems to indicate that this issue is now fixed? At least I was
not able to trigger the bug on a host that has several VirtualHosts on the same
IP/port combination with different c
ieb Stuart Henderson :
>
> On 2023/07/10 15:57, Mike Fischer wrote:
>>>> (Note: I know this could be further reduced to just one master process for
>>>> each version with a chroot(2) and a non-chroot(2) pool defined in the
>>>> single php-fpm.conf for ea
Hi Stuart,
thanks for your response. Please see my inline comments below…
> Am 10.07.2023 um 13:26 schrieb Stuart Henderson :
>
> (moving to ports@, reply-to set)
>
>
> On 2023-07-10, Mike Fischer wrote:
>> Hi!
>>
>> I’m trying to figure out the best way
Just a note: DokuWiki 2023-04-04 "Jack Jackrum“ works fine in my manually
upgraded test setups on OpenBSD 7.3.
But people who use embedded HTML or PHP (on private wikis) will need to install
additional plugins, as that functionality was removed. This is mentioned in the
release notes but some p
roblem also submitted here:
> https://bugs.chromium.org/p/chromium/issues/detail?id=1409224
>
> Any ideas to solve the problem?
>
> Bambero
--
Mike Fischer
mike.fisc...@fi-works.de
> Am 13.09.2022 um 15:58 schrieb Landry Breuil :
>
> Le Sat, Aug 13, 2022 at 09:30:45AM +0200, Landry Breuil a écrit :
>> Le Sat, Aug 13, 2022 at 09:15:30AM +0200, Rafael Sadowski a écrit :
>>> I'm no longer a dokuwiki user so I can't test it. The update looks quite
>>> simple. My motivation is
> Am 07.09.2022 um 11:26 schrieb Landry Breuil :
>
> Le Wed, Sep 07, 2022 at 11:10:14AM +0200, Omar Polo a écrit :
>>
>> I'm having an issue (that is 100% PEBCAK) with php-curl that seems to
>> be unable to resolve hostnames, but this is not an issue with the port
>> itself: even a simple php s
> Am 13.03.2022 um 10:23 schrieb Stefan Hagen :
>
> Mike Fischer wrote (2022-03-13 01:17 CET):
>> Hi ports@,
>>
>> The current version 2.4.0p0 of wp-cli seems pretty old, given that
>> 2.6.0 was released in January.
>> https://make.wordpress.org/cli
Hi ports@,
The current version 2.4.0p0 of wp-cli seems pretty old, given that 2.6.0 was
released in January.
https://make.wordpress.org/cli/2022/01/26/wp-cli-v2-6-0-release-notes/
Version 2.6.0 includes security fixes from version 2.5.0:
https://make.wordpress.org/cli/2021/05/19/wp-cli-v2-5-0-re
> Am 18.02.2022 um 03:23 schrieb J Doe :
>
> Hi,
>
> I was looking at the ports list for Suricata that is available from:
> https://openports.se/security/suricata
>
> The package update notes mention both Suricata 6.0.3 and 6.0.4, but when I
> check the ports via pkg_add I receive the follow
> Am 01.02.2022 um 15:52 schrieb Aaron Bieber :
>
> Aautomaticlly synchronize git repositories.
Spelling?
` done by the apachectl script does not fully reload the
httpd2 binary from disk? If that theory is correct then `apachectl
stop;apachectl start` would probably have worked correctly as well.
Anyway, I hope I helped prevent anyone else getting a little scare like I did
:-)
--
Mike Fischer
>
/local/lib/apache2/mod_ssl.so
mod_ssl.so was updated:
304 -rw-r--r-- 1 root bin 289196 Sep 27 19:22
/usr/local/lib/apache2/mod_ssl.so
The solution was to run the following:
# rcctl restart apache2
httpd2 is now running again.
HTH
--
Mike Fischer
fischer+o...@lavielle.com
shut up now ;-)
Thanks!
--
Mike Fischer
> Am 02.06.2021 um 00:14 schrieb Giovanni Bechis :
>
> On 6/1/21 11:37 PM, Mike Fischer wrote:
>>> Am 01.06.2021 um 23:24 schrieb Giovanni Bechis :
>>>
>>> On 6/1/21 9:15 PM, Stuart Henderson wrote:
>>
> Am 01.06.2021 um 23:24 schrieb Giovanni Bechis :
>
> On 6/1/21 9:15 PM, Stuart Henderson wrote:
>> On 2021/06/01 16:10, Mike Fischer wrote:
>>> Friendly ping:
>>>
>>> Not that this is urgent, but this patch hasn’t made it into the ports tree
>&
Friendly ping:
Not that this is urgent, but this patch hasn’t made it into the ports tree yet
AFAICT.
Could someone with CVS write permission please ok and commit (or NAK)
Giovanni's patch?
Thx.
--
Mike Fischer
> Am 15.05.2021 um 16:13 schrieb Mike Fischer :
>
> Hi Giovann
ary/module/package should not actually be needed in
my case. My expectation would be that FATAL errors would lead to an imminent
abort of the process. But this is probably something for upstream to consider.
--
Mike Fischer
> Am 15.05.2021 um 11:53 schrieb Giovanni Bechis :
>
> On Fri, Ma
ocket-INET6-2.72p0 (or install something else that
installs this as a dependency)
Question:
=
If this causes an error marked as FATAL, shouldn’t p5-IO-Socket-INET6 be
included with the postgrey package as a dependency?
Thanks!
--
Mike Fischer
Thanks Stuart! That was very helpful.
I must have missed that part of the pkg_add man page ;-)
--
Mike Fischer
> Am 08.01.2021 um 12:08 schrieb Stuart Henderson :
>
> "Instead I have to specify the full version, e.g. pkg_add php-7.4.14" -
> that's not needed, y
Hi Paul!
Thanks!
Yes, I guess I’ll live with the extra packages.
--
Mike Fischer
> Am 08.01.2021 um 11:00 schrieb Paul de Weerd :
>
> Short version: it's complicated. I decided to let php-7.3 getting
> installed not bother me :)
admin using the
system.
Thanks!
--
Mike Fischer
l take these issues into account?
--
Mike Fischer
://github.com/jimrazmus/greyscanner
which might be more correct?
THX.
--
Mike Fischer
> Am 14.12.2020 um 11:59 schrieb Boudewijn Dijkstra :
>
> greyscanner
ike Fischer
> Am 19.11.2020 um 17:16 schrieb Stuart Henderson :
>
> On 2020/11/19 16:02, Mike Fischer wrote:
>> With another slight modification it now works:
>> pexp="perl: .*postgrey.*${daemon_flags:+ ${daemon_flags}}.*“
>> (added -* after postgrey)
>
> Ah
:58PM0:00.12 perl:
postgrey -d --inet=10023 (perl)
root 17938 0.0 0.092 248 p0 R+/04:01PM0:00.00 grep postgrey
#
Thanks for your help!
--
Mike Fischer
> Am 19.11.2020 um 15:53 schrieb Stuart Henderson :
>
> On 2020/11/19 15:17, Mike Fischer wrote:
>> Hi
e is being used but it is not solving the problem.
?
--
Mike Fischer
> Am 19.11.2020 um 15:03 schrieb Stuart Henderson :
>
> On 2020/11/19 14:50, Mike Fischer wrote:
>> Hi Stuart,
>>
>> Here it is:
>> # cat /var/run/rc.d/postgrey
>> daemon_class=daemo
Hi Stuart,
Here it is:
# cat /var/run/rc.d/postgrey
daemon_class=daemon
daemon_flags=--inet=10023
daemon_rtable=0
daemon_timeout=30
daemon_user=root
pexp=perl: /usr/local/libexec/postgrey -d --inet=10023
#
Thanks!
--
Mike Fischer
> Am 19.11.2020 um 14:24 schrieb Stuart Henderson :
>
&g
postgrey is unmodified, i.e. as installed by the package.
- We are (obviously) using postgrey with postfix.
Thanks!
--
Mike Fischer
30 matches
Mail list logo
