On 24.05.18 09:15, Bernhard Fröhlich wrote:
On Thu, May 24, 2018 at 3:06 AM, Jason A. Donenfeld wrote:
We now have a release, so the full instructions for the packages are:
1. wireguard-tools, providing wg(8) and wg-quick(8)
Runtime dependencies: bash, wireguard-go
Buildtime dependencies: gmak
On 25.05.18 09:29, Bernhard Fröhlich wrote:
On Fri, May 25, 2018 at 12:24 AM, Chris H wrote:
On Thu, 24 May 2018 22:16:42 +0200 "Bernhard Froehlich"
said
Am 24.05.2018 21:06 schrieb Chris H :
On Thu, 24 May 2018 19:39:22 +0200 "Jason A. Donenfeld"
said >
Hi Chris, > > > > On Thu, May 2
On 24.05.18 13:07, Jason A. Donenfeld wrote:
On Thu, May 24, 2018 at 12:43 PM, Jan Bramkamp wrote:
Did I understand correctly that both these ports are userspace
implementations and have a similar per packet overhead to OpenVPN and fastd?
Indeed they're userspace ports. Maybe down the
On 25.05.18 15:11, Bernhard Fröhlich wrote:
On Fri, May 25, 2018 at 12:05 PM, Jan Bramkamp wrote:
On 25.05.18 09:29, Bernhard Fröhlich wrote:
On Fri, May 25, 2018 at 12:24 AM, Chris H wrote:
On Thu, 24 May 2018 22:16:42 +0200 "Bernhard Froehlich"
said
Am 24.05.2018 21:
Please run python under truss -f. Does it try to close(2) all possible
file descriptors? Does the runtime decrease if fdescfs is mounted at
/dev/fd?
On 11.04.19 15:16, Alexander Zagrebin wrote:
> Hi!
>
> I've noticed the subprocess performance issue with python 3.
> For example, this simple scrip
The reason is that that python does something stupid (tm). It tries to
close all file descriptors (except a few whitelisted ones) up to the
maximum file descriptor number. It does this by asking the kernel for
the maximum possible number and closing everything it doesn't want to
keep. Some time lat
Probably ;-) Please create a PR for this to get it fixed.
On 15.04.19 21:09, Serpent7776 wrote:
Hello,
I've just stumbled upon a possible typo in Makefile:
DEBUG_CONFIGURE_EBABLE=¦¦ debug
Shouldn't this be ENABLE instead of EBABLE?
___
freeb
On 24.05.19 12:07, Grzegorz Junka wrote:
Hey,
Is there any policy/document when a bug can be closed? For example, is
it OK to close a bug that is fixed upstream but not yet in ports?
Thanks
GrzegorzJ
I don't know of any official policy, but as a user (and port maintainer)
I would prefer an
On 08/09/15 14:45, Kubilay Kocak wrote:
On 8/09/2015 5:21 PM, Matthew Seaman wrote:
On 08/09/2015 07:46, Jimmy Renner wrote:
I don't know if this is the right list to post to but for me lots (a bit
over 100) of ports are updated but if I do a pkg upgrade not much is
updated. This has been the
On 02/03/16 16:15, Kristian Kræmmer Nielsen wrote:
Hi,
This mail-address is written in "MAINTAINER" for multimedia/zoneminder -
does that actually mean the port has no maintainer?
Exactly.
___
freebsd-ports@freebsd.org mailing list
https://lists.free
On 21/04/16 17:21, Jim Ohlstein wrote:
Hello,
I'm trying to get Mailman working in a 10.3 amd64 jail. Everything
works, except Mailman doesn't talk to Postfix. Incoming mail works and
posts to the list's archives but no outgoing email is sent. I asked in
the Mailman list and they seem to think i
rce code compresses well. Can you use a
read-only lzma or gzip compressed filesystem with GEOM uncompress?
* Can you use snapshots (and rerooting) to rollback failed updates
instead of keeping two full copies around?
-- Jan Bramkamp
___
freebsd-por
On 04/01/2017 18:32, Andriy Gapon wrote:
Do you I understand correctly that it is impossible now to install both samba44
and libreoffice using the official FreeBSD package repository?
Or samba44 and KDE?
If yes, then that sucks...
Yes and yes it sucks. The "solution" is to build your own repo
On 05/01/2017 11:43, Kurt Jaeger wrote:
Hi!
[openldap-client vs openldap-sasl-client and libreoffice etc]
Yes and yes it sucks. The "solution" is to build your own repo and set
the right flags to always use the same LDAP client port. With binary
packages and the speed of modern x86_64 systems I
On 05/01/2017 12:04, Matthew Seaman wrote:
On 01/05/17 10:43, Kurt Jaeger wrote:
Hi!
[openldap-client vs openldap-sasl-client and libreoffice etc]
Yes and yes it sucks. The "solution" is to build your own repo and set
the right flags to always use the same LDAP client port. With binary
package
On 05/01/2017 11:56, Franco Fichtner wrote:
On 5 Jan 2017, at 11:44 AM, Julian Elischer wrote:
On 5/01/2017 6:30 PM, Jan Bramkamp wrote:
On 04/01/2017 18:32, Andriy Gapon wrote:
Do you I understand correctly that it is impossible now to install both samba44
and libreoffice using the
On 17/02/2017 09:25, Matthieu Volat wrote:
On Fri, 17 Feb 2017 10:37:16 +0300
abi wrote:
17.02.2017 00:22, Chris H пишет:
On Thu, 16 Feb 2017 15:48:57 -0500 Baho Utot wrote
On 02/16/17 15:40, George Mitchell wrote:
On 02/16/17 15:33, Baho Utot wrote:
On 02/16/17 14:01, Lowell Gilbert wr
On 10/03/2017 14:26, Hans de Hartog wrote:
I have an old web server (10.1-RELEASE-p9) which is running for years
without any upgrades. Now I want to install a simple port (trafshow, to
see what's going on).
It first want to upgrade pkg from 1.5.1 to 1.10.0_2 but that doesn't work:
[1/1] Upgra
On 10/03/2017 14:47, Guido Falsi wrote:
On 03/10/17 14:26, Hans de Hartog wrote:
I have an old web server (10.1-RELEASE-p9) which is running for years
without any upgrades. Now I want to install a simple port (trafshow, to
see what's going on).
It first want to upgrade pkg from 1.5.1 to 1.10.
On 10/03/2017 15:08, Konstantin Belousov wrote:
On Fri, Mar 10, 2017 at 02:55:13PM +0100, Jan Bramkamp wrote:
Among other
things FreeBSD 10.3 added a bunch of new *at() system calls like openat.
These *at() system calls are useful inside (capsicum) sandboxes. Your
old 10.1 kernel lacks those
On 10/03/2017 17:04, Kurt Jaeger wrote:
Hi!
I have an old web server (10.1-RELEASE-p9) which is running for years
I had one with 9.3 something, and upgrading it from the pkg repo
took not a huge amount of time, yesterday evening...
So maybe upgrading is a good thing, if not too many fancy th
ontact with the right people?
-- Jan Bramkamp
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
On 05.12.17 10:53, Aryeh Friedman wrote:
First some background (my typical use cases for ports):
0. FreeBSD lilith 11.1-RELEASE FreeBSD 11.1-RELEASE #0 r321664: Fri Jul 28
23:35:18 EDT 2017 root@lilith:/usr/obj/usr/src/sys/GENERIC amd64
1. Daily routine (current):
cd /usr/src
On 06.12.17 23:23, Dave Horsfall wrote:
On Wed, 6 Dec 2017, Jan Bramkamp wrote:
Synth and poudriere are parallel build tools and as such are very
taxing on the system. I suspect your system is unstable under such
load, because of a configuration error or unreliable hardware. One
such
On 07.12.17 13:51, Baho Utot wrote:
users also don't want to wake up to the fact that what worked a few days
ago not is working ie fetch/update port repo run synth and then get a "
What the fuck has just happened now" only to be put down by the so
called folks in charge here for even asking.
I use saslauthd with GSSAPI (aka Kerberos) authentication inside jails.
IIRC you have to install a second package to add GSSAPI support to
saslauthd.
On 18.04.18 15:49, Andrea Venturoli wrote:
Hello.
I'm trying to setup saslauthd (in a jail) to authenticate to a Samba AD
DC (in another jail)
26 matches
Mail list logo