WorkFroce Central Email List

2016-12-13 Thread Kathy Jones
Hi,

Would you be interested WorkFroce Central users contact information for your
marketing campaigns?

We also have other technology users like: Sybase, SuccessFactors, Business
Objects, SharePoint, Nuxeo, IBM, Tomcat, Weblogic, Glassfish, Wildfly,
Websphere, EMC, Brocade, VMware, HP Network Storage, Hitachi Unified
Storage, EMC, ShoreTel, Juniper Networks, AT, Citrix Systems, Cisco
Systems, Riverbed, F5 Networks, Arista Networks, Cloudera, Teradata,
Netezza, MicroStrategy, Cognos, SAS, SAP NetWeaver, SAP MDM, SAP EPM, SAP
CRM, SAP HANA, SAP BPM, SAP PLM, SAP ERP, SAP Jam, SAP GRC, Lync Server and
Many more...


Below are the few titles of your interest: 

Chief Information Officer
Chief Technology Officer
Software Developers
Chief Engineers
IT Director
IT Manager
CISO and many more.

If you are looking for particular titles from your target geography, please
let me know and i will get back to you with a free sample file and more
information regarding the same.

 

Note: If this is not relevant to you please reply back with your Target
Market, we have all types of target market available.

Please review and let me know your thoughts.

Await your response!

Thanks,
Kathy Jones
Data Specialist


To opt out please response as  Unsubscribe
 



Re: Define path of configuration files in systemd unit

2016-12-13 Thread Patrick Hemmer
On 2016/12/13 11:14, Ricardo Fraile wrote:
> Hello Jarno,
>
>
> Yes, you are right, this is not an elegant solution, and reloading
> doesn't work. This is the systemd report:
>
>
> # systemctl status haproxy.service -l
> ● haproxy.service - HAProxy Load Balancer
>Loaded: loaded (/etc/systemd/system/haproxy.service; enabled)
>Active: active (running) since Tue 2016-12-13 09:25:13 CET; 1s ago
>   Process: 28736 ExecReload=/bin/kill -USR2 $MAINPID (code=exited,
> status=0/SUCCESS)
>   Process: 28764 ExecStartPre=/bin/sh -c /usr/local/sbin/haproxy -c -q
> -- /etc/haproxy/* (code=exited, status=0/SUCCESS)
>  Main PID: 28766 (sh)
>CGroup: /system.slice/haproxy.service
>├─28766 /bin/sh -c /usr/local/sbin/haproxy-systemd-wrapper
> -p /run/haproxy.pid -- /etc/haproxy/*
>├─28769 /usr/local/sbin/haproxy-systemd-wrapper
> -p /run/haproxy.pid
> -- /etc/haproxy/haproxy.conf /etc/haproxy/z.conf /etc/haproxy/zz.conf
>├─28770 /usr/local/sbin/haproxy -Ds -p /run/haproxy.pid
> -- /etc/haproxy/haproxy.conf /etc/haproxy/z.conf /etc/haproxy/zz.conf
>└─28771 /usr/local/sbin/haproxy -Ds -p /run/haproxy.pid
> -- /etc/haproxy/haproxy.conf /etc/haproxy/z.conf /etc/haproxy/zz.conf
>
>
> Thanks,
>
>
> El lun, 12-12-2016 a las 19:36 +0200, Jarno Huuskonen escribió:
>> Hi Ricardo,
>>
>> On Mon, Dec 12, Ricardo Fraile wrote:
>>> Yes, shell expansion did the trick, this is the working systemd unit:
>>>
>>>
>>> [Unit]
>>> Description=HAProxy Load Balancer
>>> After=network.target
>>>
>>> [Service]
>>> ExecStartPre=/bin/sh -c "/usr/local/sbin/haproxy -c -q
>>> -- /etc/haproxy/*"
>>> ExecStart=/bin/sh -c "/usr/local/sbin/haproxy-systemd-wrapper
>>> -p /run/haproxy.pid -- /etc/haproxy/*"
>>> ExecReload=/bin/kill -USR2 $MAINPID
>> Does the /bin/sh -c add extra process to haproxy process tree ?
>> Does systemctl status haproxy that "Main PID:" belongs to
>> haproxy-systemd-wrapper process and reloading config works ?
>>
>> -Jarno
>>

You can solve that specific issue easily by adding `exec` to the command.

ExecStart=/bin/sh -c "exec /usr/local/sbin/haproxy-systemd-wrapper
-p /run/haproxy.pid -- /etc/haproxy/*"

-Patrick


Re: Define path of configuration files in systemd unit

2016-12-13 Thread Ricardo Fraile
Hello Jarno,


Yes, you are right, this is not an elegant solution, and reloading
doesn't work. This is the systemd report:


# systemctl status haproxy.service -l
● haproxy.service - HAProxy Load Balancer
   Loaded: loaded (/etc/systemd/system/haproxy.service; enabled)
   Active: active (running) since Tue 2016-12-13 09:25:13 CET; 1s ago
  Process: 28736 ExecReload=/bin/kill -USR2 $MAINPID (code=exited,
status=0/SUCCESS)
  Process: 28764 ExecStartPre=/bin/sh -c /usr/local/sbin/haproxy -c -q
-- /etc/haproxy/* (code=exited, status=0/SUCCESS)
 Main PID: 28766 (sh)
   CGroup: /system.slice/haproxy.service
   ├─28766 /bin/sh -c /usr/local/sbin/haproxy-systemd-wrapper
-p /run/haproxy.pid -- /etc/haproxy/*
   ├─28769 /usr/local/sbin/haproxy-systemd-wrapper
-p /run/haproxy.pid
-- /etc/haproxy/haproxy.conf /etc/haproxy/z.conf /etc/haproxy/zz.conf
   ├─28770 /usr/local/sbin/haproxy -Ds -p /run/haproxy.pid
-- /etc/haproxy/haproxy.conf /etc/haproxy/z.conf /etc/haproxy/zz.conf
   └─28771 /usr/local/sbin/haproxy -Ds -p /run/haproxy.pid
-- /etc/haproxy/haproxy.conf /etc/haproxy/z.conf /etc/haproxy/zz.conf


Thanks,


El lun, 12-12-2016 a las 19:36 +0200, Jarno Huuskonen escribió:
> Hi Ricardo,
> 
> On Mon, Dec 12, Ricardo Fraile wrote:
> > Yes, shell expansion did the trick, this is the working systemd unit:
> > 
> > 
> > [Unit]
> > Description=HAProxy Load Balancer
> > After=network.target
> > 
> > [Service]
> > ExecStartPre=/bin/sh -c "/usr/local/sbin/haproxy -c -q
> > -- /etc/haproxy/*"
> > ExecStart=/bin/sh -c "/usr/local/sbin/haproxy-systemd-wrapper
> > -p /run/haproxy.pid -- /etc/haproxy/*"
> > ExecReload=/bin/kill -USR2 $MAINPID
> 
> Does the /bin/sh -c add extra process to haproxy process tree ?
> Does systemctl status haproxy that "Main PID:" belongs to
> haproxy-systemd-wrapper process and reloading config works ?
> 
> -Jarno
> 





Re: [PATCH] Add fe_name/be_name fetchers next to existing fe_id/be_id

2016-12-13 Thread Marcin Deranek
On 12/13/2016 11:25 AM, Willy Tarreau wrote:
>> I think we'll definitely need to have some string-oriented operators. We
>> could implement them using converters (eg: append and compare mostly), but
>> we also thought that we could replace every sample fetch with a converter
>> and allow all expressions to be simplified (eg: a fetcher would just be
>> like a converter except that it doesn't affect the existing stack and
>> pushes a new value).
>>
>> With all that in mind, I'm not much tempted to implement too many things
>> if we have to redesign them a short time later!
Makes sense. Any ETA when this is going to arrive ?
>> Yes sure :-)  Feel free to send a patch regarding this otherwise I may forget
>> just like I forgot to remove "1.5" from the stats page before releasing 
>> 1.7.1.

Attached.

Marcin
--- doc/configuration.txt.old	2016-12-12 22:57:04.0 +0100
+++ doc/configuration.txt	2016-12-13 12:34:47.385694584 +0100
@@ -13182,7 +13182,7 @@
 
 fe_id : integer
   Returns an integer containing the current frontend's id. It can be used in
-  backends to check from which backend it was called, or to stick all users
+  backends to check from which frontend it was called, or to stick all users
   coming via a same frontend to the same server.
 
 fe_name : string


lua support does not build on FreeBSD

2016-12-13 Thread Dmitry Sivachenko
Hello,

I am unable to build haproxy-1.7.x on FreeBSD:

cc -Iinclude -Iebtree -Wall -O2 -pipe -O2 -fno-strict-aliasing -pipe  
-fstack-protector   -DFREEBSD_PORTS-DTPROXY -DCONFIG_HAP_CRYPT 
-DUSE_GETADDRINFO -DUSE_ZLIB  -DENABLE_POLL -DENABLE_KQUEUE -DUSE_CPU_AFFINITY 
-DUSE_OPENSSL  -DUSE_LUA -I/usr/local/include/lua53 -DUSE_DEVICEATLAS 
-I/place/WRK/ports/net/haproxy/work/deviceatlas-enterprise-c-2.1 -DUSE_PCRE 
-I/usr/local/include -DUSE_PCRE_JIT  -DCONFIG_HAPROXY_VERSION=\"1.7.1\" 
-DCONFIG_HAPROXY_DATE=\"2016/12/13\" -c -o src/hlua_fcn.o src/hlua_fcn.c
src/hlua_fcn.c:1019:27: error: no member named 's6_addr32' in 'struct in6_addr'
if (((addr1->addr.v6.ip.s6_addr32[0] & addr2->addr.v6.ma...
  ~ ^
src/hlua_fcn.c:1019:62: error: no member named 's6_addr32' in 'struct in6_addr'
  ...if (((addr1->addr.v6.ip.s6_addr32[0] & addr2->addr.v6.mask.s6_addr32[0]...
~~~ ^
src/hlua_fcn.c:1020:27: error: no member named 's6_addr32' in 'struct in6_addr'
 (addr2->addr.v6.ip.s6_addr32[0] & addr1->addr.v6.ma...
  ~ ^
src/hlua_fcn.c:1020:62: error: no member named 's6_addr32' in 'struct in6_addr'
  ...(addr2->addr.v6.ip.s6_addr32[0] & addr1->addr.v6.mask.s6_addr32[0])) &&
   ~~~ ^
src/hlua_fcn.c:1021:27: error: no member named 's6_addr32' in 'struct in6_addr'
((addr1->addr.v6.ip.s6_addr32[1] & addr2->addr.v6.ma...
  ~ ^
src/hlua_fcn.c:1021:62: error: no member named 's6_addr32' in 'struct in6_addr'
  ...((addr1->addr.v6.ip.s6_addr32[1] & addr2->addr.v6.mask.s6_addr32[1]) ==
~~~ ^
src/hlua_fcn.c:1022:27: error: no member named 's6_addr32' in 'struct in6_addr'
 (addr2->addr.v6.ip.s6_addr32[1] & addr1->addr.v6.ma...
  ~ ^
src/hlua_fcn.c:1022:62: error: no member named 's6_addr32' in 'struct in6_addr'
  ...(addr2->addr.v6.ip.s6_addr32[1] & addr1->addr.v6.mask.s6_addr32[1])) &&
   ~~~ ^
src/hlua_fcn.c:1023:27: error: no member named 's6_addr32' in 'struct in6_addr'
((addr1->addr.v6.ip.s6_addr32[2] & addr2->addr.v6.ma...
  ~ ^
src/hlua_fcn.c:1023:62: error: no member named 's6_addr32' in 'struct in6_addr'
  ...((addr1->addr.v6.ip.s6_addr32[2] & addr2->addr.v6.mask.s6_addr32[2]) ==
~~~ ^
src/hlua_fcn.c:1024:27: error: no member named 's6_addr32' in 'struct in6_addr'
 (addr2->addr.v6.ip.s6_addr32[2] & addr1->addr.v6.ma...
  ~ ^
src/hlua_fcn.c:1024:62: error: no member named 's6_addr32' in 'struct in6_addr'
  ...(addr2->addr.v6.ip.s6_addr32[2] & addr1->addr.v6.mask.s6_addr32[2])) &&
   ~~~ ^
src/hlua_fcn.c:1025:27: error: no member named 's6_addr32' in 'struct in6_addr'
((addr1->addr.v6.ip.s6_addr32[3] & addr2->addr.v6.ma...
  ~ ^
src/hlua_fcn.c:1025:62: error: no member named 's6_addr32' in 'struct in6_addr'
  ...((addr1->addr.v6.ip.s6_addr32[3] & addr2->addr.v6.mask.s6_addr32[3]) ==
~~~ ^
src/hlua_fcn.c:1026:27: error: no member named 's6_addr32' in 'struct in6_addr'
 (addr2->addr.v6.ip.s6_addr32[3] & addr1->addr.v6.ma...
  ~ ^
src/hlua_fcn.c:1026:62: error: no member named 's6_addr32' in 'struct in6_addr'
  ...(addr2->addr.v6.ip.s6_addr32[3] & addr1->addr.v6.mask.s6_addr32[3]))) {
   ~~~ ^
16 errors generated.




In netinet6/in6.h I see:

#ifdef _KERNEL  /* XXX nonstandard */
#define s6_addr8  __u6_addr.__u6_addr8
#define s6_addr16 __u6_addr.__u6_addr16
#define s6_addr32 __u6_addr.__u6_addr32
#endif


So it seems that s6_addr32 macro is defined only when this header is included 
during kernel build.





Re: [External] Re: [PATCH] Add fe_name/be_name fetchers next to existing fe_id/be_id

2016-12-13 Thread Willy Tarreau
Hi Marcin,

On Tue, Dec 13, 2016 at 10:53:05AM +0100, Marcin Deranek wrote:
> On 12/12/2016 03:14 PM, Willy Tarreau wrote:
> > Just merged now, thanks. A few weeks ago someone needed it, I guess it
> > was for logging, and I thought we had it though it was not the case, so
> > I realized we were missing it. In fact we still have quite a number of
> > fields available as log tags which do not have an equivalent sample fetch
> > function. It would be nice to ensure we have all of them and document the
> > equivalence as well in the logformat table.
> Thank you Willy. For logging you can use %f (which is already there)
> although in some places fetcher is required and then you are stuck.
> BTW: Once I can "extract" frontend name is there a way to compare
> "dynamic" data (eg. frontend name) with another "dynamic" data (eg. host
> header) ? From what I can see we can easily compare "dynamic" data with
> "static" data (eg. some predefined string), but not eg. 2 variables.

No there's no such thing unfortunately. Thierry implemented support for
variables in the arithmetic operators to allow *some* manipulation to be
performed (eg: in order to compare a and b, you can subtract b to a and
compare the result), but there's nothing similar with strings. We wanted
to implement something like an RPN engine, a stack-based evaluator a bit
like forth or various such languages, which require very few tricks and
can be very fast. But it was not done by lack of time.

I think we'll definitely need to have some string-oriented operators. We
could implement them using converters (eg: append and compare mostly), but
we also thought that we could replace every sample fetch with a converter
and allow all expressions to be simplified (eg: a fetcher would just be
like a converter except that it doesn't affect the existing stack and
pushes a new value).

With all that in mind, I'm not much tempted to implement too many things
if we have to redesign them a short time later!

> Side note: In docs/configuration.txt I came across this:
> 
> fe_id : integer
>   Returns an integer containing the current frontend's id. It can be used in
>   backends to check from which backend it was called, or to stick all users
>   coming via a same frontend to the same server.
> 
> shouldn't this contain:
> ...It can be used in backends to check from which FRONTEND it was
> called... ?

Yes sure :-)  Feel free to send a patch regarding this otherwise I may forget
just like I forgot to remove "1.5" from the stats page before releasing 1.7.1.

Thanks,
Willy




Re: [External] Re: [PATCH] Add fe_name/be_name fetchers next to existing fe_id/be_id

2016-12-13 Thread Marcin Deranek
On 12/12/2016 03:14 PM, Willy Tarreau wrote:
> Just merged now, thanks. A few weeks ago someone needed it, I guess it
> was for logging, and I thought we had it though it was not the case, so
> I realized we were missing it. In fact we still have quite a number of
> fields available as log tags which do not have an equivalent sample fetch
> function. It would be nice to ensure we have all of them and document the
> equivalence as well in the logformat table.
Thank you Willy. For logging you can use %f (which is already there)
although in some places fetcher is required and then you are stuck.
BTW: Once I can "extract" frontend name is there a way to compare
"dynamic" data (eg. frontend name) with another "dynamic" data (eg. host
header) ? From what I can see we can easily compare "dynamic" data with
"static" data (eg. some predefined string), but not eg. 2 variables.
Regards,

Marcin

Side note: In docs/configuration.txt I came across this:

fe_id : integer
  Returns an integer containing the current frontend's id. It can be used in
  backends to check from which backend it was called, or to stick all users
  coming via a same frontend to the same server.

shouldn't this contain:
...It can be used in backends to check from which FRONTEND it was
called... ?