At Mon, 29 Jun 2020 21:48:13 +0200, Jaromír Dole ek
wrote:
Subject: Re: fork and COW
>
> However COW is only relevant before php-fpm does exec of ImageMagick.
> Immediately after fork the child shares the address space with the
> parent having the memory pages marked as COW, after exec the
At Mon, 29 Jun 2020 10:00:06 +0530, Mayuresh wrote:
Subject: How to configure npf to restrict nfs to localhost
>
> Looking to share host FS with a qemu guest using NFS.
>
> Do not want to expose the NFS ports to outside world. Firstly, what all
> ports are in question - is it 111, 1000 and 2049
Le lun. 29 juin 2020 à 22:38, Dima Veselov a écrit :
> Is it
> dropped because php exited and now this process has its own new
> reservations as much as it need for itself?
Yes, the whole 512M address space is dropped on exec.
> > It's likely Something Else (tm).
>
> Thank you, I will
On Mon, 29 Jun 2020, Benny Siegert wrote:
I have used command lines such as
some_command | xargs pkg_admin set rebuild=YES
in the past.
Ah. That looks very promising.
My experiments with command lines such as
pkg_admin set rebuild=YES package1 package2 etc
or
pkg_admin set rebuild=YES
On 29.06.2020 22:48, Jaromír Doleček wrote:
I know running binary on image upload is a bad idea, but I wonder
why in our testing environment on Linux it does not happen. My thought
was somewhere around COW capabilities of fork() but as I know COW is
implemented in NetBSD as well. Is it true
Le lun. 29 juin 2020 à 21:18, Dima Veselov a écrit :
> I know running binary on image upload is a bad idea, but I wonder
> why in our testing environment on Linux it does not happen. My thought
> was somewhere around COW capabilities of fork() but as I know COW is
> implemented in NetBSD as well.
Greetings,
I have some problems with my php-fpm web-server backends which occur on
image upload. I found php-fpm forking and running ImageMagick's convert
as much times as much pictures one try to upload. Uploading 10 pictures
at once will make the daemon fork 10 times, 512M each and memory is
Michael van Elst wrote:
On Mon, Jun 29, 2020 at 07:08:40PM +0300, Staffan Thomén wrote:
Chavdar Ivanov wrote:
# ccdconfig -c ccd0 0 /dev/zvol/dsk/internal1/photos@backup
You are mapping a snapshot, it will be r/o.
You have to promote it first.
While it's true that the snapshot is r/o,
On Mon, Jun 29, 2020 at 07:08:40PM +0300, Staffan Thomén wrote:
> Chavdar Ivanov wrote:
> > > # ccdconfig -c ccd0 0 /dev/zvol/dsk/internal1/photos@backup
> >
> > You are mapping a snapshot, it will be r/o.
> >
> > You have to promote it first.
>
> While it's true that the snapshot is r/o,
On Mon, 29 Jun 2020 at 17:08, Staffan Thomén wrote:
>
> Chavdar Ivanov wrote:
> >> # ccdconfig -c ccd0 0 /dev/zvol/dsk/internal1/photos@backup
> >
> > You are mapping a snapshot, it will be r/o.
> >
> > You have to promote it first.
>
> While it's true that the snapshot is r/o, surely it
On Mon, Jun 29, 2020 at 10:43 AM Bob Bernstein wrote:
>
> The man page for pkg_admin contains this line:
>
> set variable=value pkg ...
>
> Do the three final "..." indicate that if it is desired to set
> that variable to that value for more than one package, then can
> be named in a
Chavdar Ivanov wrote:
# ccdconfig -c ccd0 0 /dev/zvol/dsk/internal1/photos@backup
You are mapping a snapshot, it will be r/o.
You have to promote it first.
While it's true that the snapshot is r/o, surely it shouldn't crash the system.
And is there a reason why ccd would require r/w?
On Mon, 29 Jun 2020 at 16:31, Staffan Thomén wrote:
>
> Michael van Elst wrote:
> > mlel...@serpens.de (Michael van Elst) writes:
> >
> >> mlel...@serpens.de (Michael van Elst) writes:
> >>> ci4...@gmail.com (Chavdar Ivanov) writes:
> # ccdconfig -c ccd0 0 /dev/zvol/dsk/pail/nbsd1
>
Michael van Elst wrote:
mlel...@serpens.de (Michael van Elst) writes:
mlel...@serpens.de (Michael van Elst) writes:
ci4...@gmail.com (Chavdar Ivanov) writes:
# ccdconfig -c ccd0 0 /dev/zvol/dsk/pail/nbsd1
ccdconfig: ioctl (CCDIOCSET): /dev/ccd0d: Inappropriate ioctl for device
That's a
On Mon, 29 Jun 2020 at 13:04, Uwe Klaus wrote:
>
> On Mon, 29 Jun 2020, Jaromír Dole?ek wrote:
>
> > I'd recommend switching over to (also built-in) dhcpcd.
> This is a DHCP client, isn't it.
> I need a reliable DHCP server.
I've had very good experiences with dnsmasq from pkgsrc - which can
Hi,
I was always thinking dhcpd is a DHCP server, but dhcpcd is a DHCP client,
so they are not interchangable. Am I missing something?
As for original question - me personally not using buit-in dhcpd because
of broken DNS updates, so I would recommend switching to pkgsrc version.
On Mon, Jun
On Mon, 29 Jun 2020, Jaromír Dole?ek wrote:
I'd recommend switching over to (also built-in) dhcpcd.
This is a DHCP client, isn't it.
I need a reliable DHCP server.
Le lun. 29 juin 2020 à 13:05, Uwe Klaus a écrit :
I am using the built-in dhcpd daemon with a GENERIC kernel on 9.0_STABLE
I'd recommend switching over to (also built-in) dhcpcd.
Jaromir
Le lun. 29 juin 2020 à 13:05, Uwe Klaus a écrit :
>
>
> I am using the built-in dhcpd daemon with a GENERIC kernel on 9.0_STABLE
> amd64.
> On several vacations am seeing messages like this
>
> Jun 29 09:56:19 hgb1 dhcpd[319]: Null
I am using the built-in dhcpd daemon with a GENERIC kernel on 9.0_STABLE
amd64.
On several vacations am seeing messages like this
Jun 29 09:56:19 hgb1 dhcpd[319]: Null pointer in option_cache_dereference:
/usr/src/external/mpl/dhcp/bin/server/../../dist/server/dhcp.c(3994)
Jun 29 09:55:51
The man page for pkg_admin contains this line:
set variable=value pkg ...
Do the three final "..." indicate that if it is desired to set
that variable to that value for more than one package, then can
be named in a whitespace-separated list?
Thank you
--
A test of right and wrong must be
On Mon, Jun 29, 2020 at 11:26:37AM +0530, Mayuresh wrote:
> On Mon, Jun 29, 2020 at 10:00:06AM +0530, Mayuresh wrote:
> > Any hints for how to block these ports for outside world and keep open for
> > localhost?
>
> Tried:
>
> group "external" on $ext_if {
> ...
> block final to any port
21 matches
Mail list logo
