Re: [PATCH] DOC: update INSTALL with supported OpenBSD / FreeBSD versions
On Fri, Oct 02, 2020 at 06:36:58PM -0400, Brad Smith wrote: > Update INSTALL with the OpenBSD / FreeBSD versions that are supported. Merged, thanks Brad! Willy
Re: Alternatives to PayPal
What about a Patron account. https://www.patreon.com/europe Cause I already asked multiple times for some other means of contribution as well. That would help a great deal, makeing it easier. I'm supporting multiple Opensource projects already this way. Would that be an option? Best regards Sebastian On 07.10.2020 11:03, Nicolas CARPi wrote: Dear list, Haproxy is an amazing project and it is clear that the devs are pouring a lot of energy and time into it. As a (very) small entrepreneur, I use Haproxy to host my services and I'm quite happy with it. It is an essential part of my business. I wish to redistribute a small part of the money I generate to this project, as I believe open source projects do need this, nothing is free in this world. Unfortunately, the only way to donate is through PayPal, and like many, I have a strong aversion to this company. May I suggest setting up an OpenCollective or Liberapay account (or both)? These services also allow to be transparent about who gets what and to remunerate recurrent contributors. Let me know what you think! :) Regards, ~Nicolas CARPi -- Far-Galaxy Networks Sebastian Fohler Asternstr. 5, 80689 München Mobil: 0173 8796211 E-Mail: i...@far-galaxy.de Web: http://www.far-galaxy.de Firmenangaben: http://www.far-galaxy.de/impressum <>
Alternatives to PayPal
Dear list, Haproxy is an amazing project and it is clear that the devs are pouring a lot of energy and time into it. As a (very) small entrepreneur, I use Haproxy to host my services and I'm quite happy with it. It is an essential part of my business. I wish to redistribute a small part of the money I generate to this project, as I believe open source projects do need this, nothing is free in this world. Unfortunately, the only way to donate is through PayPal, and like many, I have a strong aversion to this company. May I suggest setting up an OpenCollective or Liberapay account (or both)? These services also allow to be transparent about who gets what and to remunerate recurrent contributors. Let me know what you think! :) Regards, ~Nicolas CARPi
Re: [PATCH v2 0/4] add set server ssl command
Hello, adding some more thoughts we discussed internally with Pierre: - we started to use `show servers state`, as it was the only way to get the current config for the parameters we wanted to change with the existing runtime API. - even if it was not necessarily designed for that purpose, we need a way to get the current config. - we understood `show servers state` was more likely designed for internal usage, especially for `load-server-state-from-file`, so that my patch set has some implications. That being said, would it more acceptable to add a new API which which reflects all the `set` commands such as: - show server [/] would display all the config of a given server or all of them - show server / agent - show server / state - show server / weight etc and for my first proposition: - show server ssl [/] - set server ssl [/] on/off for our immediate usage around ssl we are also thinking about ca_file, crt, crt-file. This also would be a good answer to simplify how it is managed through the current dataplane API https://www.haproxy.com/documentation/dataplaneapi/latest/#operation/createServer What are your thoughts about it? -- William
Advertising offer
Hello, My name is Maria and I’m the marketing specialist in a huge IT company, and I really like the way you run your site. I would like to thank you for the high-quality work and excellent content on haproxy.com. I’m writing to you because I have some really interesting content ideas that could bring value to your target audience. We want to order to post an article with a link in return for financial rewards. Please let me know if it is possible and if so, send me the conditions of making a sponsored or guest post (price, etc.) Best , Maria Biz
[PATCH] BUG/MINOR: mworker: delete the pidfile when the master process is stopped
Hi, all, haproxy does not delete the pidfile when stopped. If the PID in the remaining pidfile is reused by other process, the operation using the pidfile may affect other process. In master-worker mode, fixed to delete pidfile when stopped. However, in the daemon mode, it has not been dealt with yet. Is there any objection to dealing only with master-worker mode? Best regards, MIZUTA Takeshi 0001-BUG-MINOR-mworker-delete-the-pidfile-when-the-master.patch Description: 0001-BUG-MINOR-mworker-delete-the-pidfile-when-the-master.patch
[PATCH] BUILD: Add a DragonFlyBSD target
Add a target for DragonFlyBSD 4.3 and above. diff --git a/INSTALL b/INSTALL index f562a7102..0263cf34c 100644 --- a/INSTALL +++ b/INSTALL @@ -376,6 +376,7 @@ and assign it to the TARGET variable : - linux-musl for Linux kernel 2.6.28 and above with musl libc - solaris for Solaris 10 and above - freebsd for FreeBSD 10 and above + - dragonfly for DragonFlyBSD 4.3 and above - netbsd for NetBSD - osx for Mac OS/X - openbsd for OpenBSD 6.3 and above diff --git a/Makefile b/Makefile index 7958b89d6..4aabe34dc 100644 --- a/Makefile +++ b/Makefile @@ -142,8 +142,9 @@ DOCDIR = $(PREFIX)/doc/haproxy TARGET system # Use TARGET= to optimize for a specific target OS among the # following list (use the default "generic" if uncertain) : -#linux-glibc, linux-glibc-legacy, linux-musl, solaris, freebsd, openbsd, -#netbsd, cygwin, haiku, aix51, aix52, aix72-gcc, osx, generic, custom +#linux-glibc, linux-glibc-legacy, linux-musl, solaris, freebsd, dragonfly, +#openbsd, netbsd, cygwin, haiku, aix51, aix52, aix72-gcc, osx, generic, +#custom TARGET = TARGET CPU @@ -371,6 +372,13 @@ ifeq ($(TARGET),freebsd) USE_ACCEPT4 USE_CLOSEFROM USE_GETADDRINFO) endif +# DragonFlyBSD 4.3 and above +ifeq ($(TARGET),dragonfly) + set_target_defaults = $(call default_opts, \ +USE_POLL USE_TPROXY USE_LIBCRYPT USE_THREAD USE_CPU_AFFINITY USE_KQUEUE \ +USE_ACCEPT4 USE_CLOSEFROM USE_GETADDRINFO) +endif + # Mac OS/X ifeq ($(TARGET),osx) set_target_defaults = $(call default_opts, \ @@ -773,8 +781,9 @@ all: @echo @echo "Please choose the target among the following supported list :" @echo - @echo " linux-glibc, linux-glibc-legacy, linux-musl, solaris, freebsd, openbsd, " - @echo " netbsd, cygwin, haiku, aix51, aix52, aix72-gcc, osx, generic, custom" + @echo " linux-glibc, linux-glibc-legacy, linux-musl, solaris, freebsd, dragonfly, " + @echo " iopenbs, netbsd, cygwin, haiku, aix51, aix52, aix72-gcc, osx, generic, " + @echo " custom" @echo @echo "Use \"generic\" if you don't want any optimization, \"custom\" if you" @echo "want to precisely tweak every option, or choose the target which" @@ -850,8 +859,9 @@ help: fi; \ else \ echo "TARGET not set, you may pass 'TARGET=xxx' to set one among :";\ -echo " linux-glibc, linux-glibc-legacy, solaris, freebsd, netbsd, osx,"; \ -echo " openbsd, aix51, aix52, aix72-gcc, cygwin, haiku, generic, custom"; \ +echo " linux-glibc, linux-glibc-legacy, solaris, freebsd, dragonfly, netbsd,"; \ +echo " osx, openbsd, aix51, aix52, aix72-gcc, cygwin, haiku, generic,"; \ +echo " custom"; \ fi $(Q)echo;echo "Enabled features for TARGET '$(TARGET)' (disable with 'USE_xxx=') :" $(Q)set -- $(foreach opt,$(patsubst USE_%,%,$(use_opts)),$(if $(USE_$(opt)),$(opt),)); echo " $$*" | (fmt || cat) 2>/dev/null
Re: Alternatives to PayPal
Hi, On Wed, Oct 07, 2020 at 11:20:25AM +0200, Sebastian Fohler wrote: > What about a Patron account. > > https://www.patreon.com/europe > > Cause I already asked multiple times for some other means of contribution as > well. > That would help a great deal, makeing it easier. > I'm supporting multiple Opensource projects already this way. > Would that be an option? Well, to make things clear, first let me remind that the paypal account is my personal account, which I have added a link to from the main page upon request by several people willing to donate many years ago. This has been helpful in the early days, allowing me buy some hardware to experiment during week-ends (such as the 10G lab), and to significantly improve the code's portability and efficiency on small systems. It used to serve to contribute to the hosting costs as well. Since then the project has considerably evolved, being backed by a company offering a much larger full-time development team. And users are well aware of this because nowadays donations are extremely rare (in the range of tens of dollars a year). But at the same time nowadays I do not need them at all anymore, so I'm perfectly fine with replacing the link with anything else. I've only been keeping it because I know that if I remove it, the question will come back again a few months later. The only thing is that I am *not* going to deal with yet another task that adds more burden, so if someone is willing to set up any account via $whatever company, they will have to handle it and pass me the replacement link. At least the paypal link doesn't cause me any extra work beyond replying "thank you" to donators once in a while. Just be aware that since donations are rare, I'm not at all convinced it will be worth doing anything particular. And at some point a solution will have to be found to spend the eventual money that would land there, so someone will have to handle this, and again it's certainly not me. My personal suggestion would be that those who want to give a few dollars better keep their money that they certainly need more than most developers or contributors do, because due to the project's nature, contributors generaly work in IT at levels at which, based on the high quality of their contributions, they're not expected to be starving at all (or if they do they definitely need to switch jobs as their skills are quite sought)! If anyone is ever willing to spend a large amount, like thousands of dollars, better hire someone to develop some useful desired features, it will be an excellent contribution to the project! Another great option is to contact your favorite distro's package maintainer and propose your donation there, because distro maintainers have been doing this thankless job for many years now and deserve some recognition as well. For anything else, offering time to look into bugs, testing -dev releases, improving the doc, contributing to the wiki etc is extremely valuable and helps all contributors at once. As you see, there are still plenty of options which do not require managing any new account anywhere. Thanks for your support :-) Willy
