[SPAM] Re: LED panel lighting factory from China.
DearSirs=orMadamwhomayconcerned, Goodday! ThisisCarina,salesmanagerfromS=imaoLED. Belowplsfindtheinformationof600*600mmLEDpanellig=ht36Wforyourreference: nb=sp; =20nbsp=; nbsp=; MS-PL18323Powernbs=p;36WPackingdetails:4=pcs/Carton CartonSize:L68times;W64ti=mes;H18cm GW:14.5kg/CartonUnitPriceUS$25.00SizeL597=*W597*T13mmInputVoltageAC8=5-265V/AC50/60HzLEDQTY80pc=sLEDType5630=SMDchipCCT2700=-6500KLumen3200=LMPowerfactor0.93CRI(Ra)Ra#65310;75MaterialPure=AluminumLifespangt;=50,000hours=Ifinterest,contactmeplease! =BestRegards! Yourssincerely, CarinaChen **Asia-BOSLINoptoelectronicsSciamp;TechGroup=CO.,LIMITEDFactoryADD:TaiHeRongIndustrialBldgA.LiaoK=eng.Shiyan,Shenzhen(518108)=20OfficeADD:Room722,B=uilding523,BaGuaLingIndustrialpark,BaGuaThirdRd,Futiandistrict=,shenzhenChinaMobile:+86-15361680980Fax:+86-755-2300710=7SkypeID:Simaoled30E-mail:Carina@simaoled.=com MSN:Shuangyue815@hotmail.comWebsite:www.si=maoled.com
[SPAM] Re: LED panel lighting factory from China.
DearSirs=orMadamwhomayconcerned, Goodday! ThisisCarina,salesmanagerfromS=imaoLED. Belowplsfindtheinformationof600*600mmLEDpanellig=ht36Wforyourreference: nb=sp; =20nbsp=; nbsp=; MS-PL18323Powernbs=p;36WPackingdetails:4=pcs/Carton CartonSize:L68times;W64ti=mes;H18cm GW:14.5kg/CartonUnitPriceUS$25.00SizeL597=*W597*T13mmInputVoltageAC8=5-265V/AC50/60HzLEDQTY80pc=sLEDType5630=SMDchipCCT2700=-6500KLumen3200=LMPowerfactor0.93CRI(Ra)Ra#65310;75MaterialPure=AluminumLifespangt;=50,000hours=Ifinterest,contactmeplease! =BestRegards! Yourssincerely, CarinaChen **Asia-BOSLINoptoelectronicsSciamp;TechGroup=CO.,LIMITEDFactoryADD:TaiHeRongIndustrialBldgA.LiaoK=eng.Shiyan,Shenzhen(518108)=20OfficeADD:Room722,B=uilding523,BaGuaLingIndustrialpark,BaGuaThirdRd,Futiandistrict=,shenzhenChinaMobile:+86-15361680980Fax:+86-755-2300710=7SkypeID:Simaoled30E-mail:Carina@simaoled.=com MSN:Shuangyue815@hotmail.comWebsite:www.si=maoled.com
Re:IGBT ,MODULE,IPM
Hello, How are you ? This is Ella from E-solution Technology , We are mainly selling IGBT modules like SEMIKRON,MITSUBISH,EUPEC,FUJI,TOSHIBA ,ect, And power module like MEANWELL ,CHINFA if you are in producing or repairing welding machine , inverters ,numerical control area , please don't hesitate to contact me . Large range of stock with low price and high quality . I hope i have the honor to start the cooperation with you sincerely Any further information ,welcome to contact me Best regards Ella E-Solution Technology com,ltd Add:Room 15A-19, Overseas Decoration Building ,zhenhua Road,Futian.SZ,China Skype:ella-chen86 Website:e-sotech.com
RE: HAProxy segfault
Hi David, Hi! HAProxy 1.6-dev1, CentOS6 Getting a segfault when trying connect to port 3389. segfault at 0 ip (null) sp 7fff18a41268 error 14 in haproxy[40+a4000] You are using the development tree, please upgrade latest git first, there are 233 commits since 1.6-dev1. Lukas
RE: HAProxy segfault
Thanks. tried this version, it works fine.. Ok, thanks for confirming.
mode tcp in front end will not override mode http in defaults
I found what I think is a couple of bugs. I'm running 1.5.12. If mode http or option forwardfor are in the defaults section, I cannot get a frontend configured with mode tcp to work. The mode tcp config is not overriding the default choice, it operates in the http mode specified in defaults. If option forwardfor is in defaults, config validation fails when the frontend specifies tcp mode. I could not find a way to turn off forwardfor in the frontend when it's enabled in defaults ... but I think when the frontend mode is tcp, that inherited option should probably be ignored. I can understand a config error if forwardfor is explicitly configured in the frontend. Here's the haproxy -vv output: HA-Proxy version 1.5.12 2015/05/02 Copyright 2000-2015 Willy Tarreau w...@1wt.eu Build options : TARGET = linux2628 CPU = native CC = gcc CFLAGS = -O2 -march=native -g -fno-strict-aliasing OPTIONS = USE_ZLIB=1 USE_OPENSSL=1 USE_PCRE=1 Default settings : maxconn = 2000, bufsize = 16384, maxrewrite = 8192, maxpollevents = 200 Encrypted password support via crypt(3): yes Built with zlib version : 1.2.8 Compression algorithms supported : identity, deflate, gzip Built with OpenSSL version : OpenSSL 1.0.2a 19 Mar 2015 Running on OpenSSL version : OpenSSL 1.0.2a 19 Mar 2015 OpenSSL library supports TLS extensions : yes OpenSSL library supports SNI : yes OpenSSL library supports prefer-server-ciphers : yes Built with PCRE version : 8.31 2012-07-06 PCRE library supports JIT : no (USE_PCRE_JIT not set) Built with transparent proxy support using: IP_TRANSPARENT IPV6_TRANSPARENT IP_FREEBIND Available polling systems : epoll : pref=300, test result OK poll : pref=200, test result OK select : pref=150, test result OK Total: 3 (3 usable), will use epoll.
[SPAM] Summer Deals: save 20% on AHD Cameras
DearMr./Mrs., Gladtogetyourcontactinformation!ThisisCarolfromTopVi=sionElectronicsLimited,whichspecializesinRamp;D,design,produc=tionandsalesoftheHDIPcamera,IPPTZcamera,Spycamera,NVRsys=tem,HDDVRsystem,DVRsystemetc. Thereareour AHDCameraBigPromotionsnow!Kindlyplea=sefindthepicturebelow. E-catalogwillbeprovidedifneeded.Emailmeorjustcallmedirectly.Thankyou!IfIluckenough,canIgetyourreply?On-lineDemoisreadyforyou,welcometoaskfordet=ails! CarolInternationalSalesDepartment**=**=Skype:first-cctvWebsite:www.first-cct=v.comTel:+862023329002Address:B1102,YueHaiSquare,No.1070,SanyuanliDaDao,G=uangzhou,ChinaProductrange:IPcamera,NVR,analoguecamera,DVR,bulletc=amera,hiddencamera,PTZcameraandaccessories.=**=**
Re: mode tcp in front end will not override mode http in defaults
On 5/15/2015 4:40 PM, Cyril Bonté wrote: If mode http or option forwardfor are in the defaults section, I cannot get a frontend configured with mode tcp to work. The mode tcp config is not overriding the default choice, it operates in the http mode specified in defaults. It should not, are you sure this is not because you're using a backend with mode http enabled ? both have to be in tcp mode to disable the defaults, as it is valid to have a frontend in tcp mode with a backend in http mode. This is a lab setup where I'm woking on active and passive FTP. I finally managed to get that functional in the lab, but now I need to configure the firewall (required since FTP uses TPROXY) to allow direct access to the back end servers -- this lab machine and the production load balancer pair also serve as the default gateway for their backend servers. That means that it is the only path to reach them, so I must have ssh passing through the firewall at an absolute minimum. This isn't an haproxy problem, but if anyone here knows how to get that working, I'd appreciate a hand. FYI, the SNAT that I configured for FTP is only activated on a source port of 20, so the private IP address on the back end server won't have to contend with NAT for ssh. When I noticed the problems I reported at the start of this thread, I copied my haproxy config for http and https, ripped out all the frontends and backends that were there, none of which had a mode command in them. Then I added the config for FTP, which DOES have a mode command. That wouldn't allow the FTP control channel to connect until I took the mode and option forwardfor out of defaults. The only place I had mode commands was in defaults and the frontends, the backends do not have mode commands. Once I solve the firewall issue with direct access to the back end servers, I will combine the http/https and ftp into a single haproxy config and put it on my production pair. Sometimes, you can use an interesting trick : do you know you can declare several defaults sections ? It allows to declare a defaults one for you http frontends/backends, and another one for the tcp ones. Is that as simple as having a defaults section followed by frontends and backends doing http/https, then another defaults section with the tcp settings, followed by the frontends and backends for tcp? Do all settings reset back to just what's in global for the second defaults section? Thanks, Shawn
Re: mode tcp in front end will not override mode http in defaults
Hi Shawn, Le 16/05/2015 00:10, Shawn Heisey a écrit : I found what I think is a couple of bugs. I'm running 1.5.12. If mode http or option forwardfor are in the defaults section, I cannot get a frontend configured with mode tcp to work. The mode tcp config is not overriding the default choice, it operates in the http mode specified in defaults. It should not, are you sure this is not because you're using a backend with mode http enabled ? both have to be in tcp mode to disable the defaults, as it is valid to have a frontend in tcp mode with a backend in http mode. If option forwardfor is in defaults, config validation fails when the frontend specifies tcp mode. I could not find a way to turn off forwardfor in the frontend when it's enabled in defaults ... but I think when the frontend mode is tcp, that inherited option should probably be ignored. I can understand a config error if forwardfor is explicitly configured in the frontend. I guess you are seeing a warning, not en error, and then the validation shouldn't fail. Sometimes, you can use an interesting trick : do you know you can declare several defaults sections ? It allows to declare a defaults one for you http frontends/backends, and another one for the tcp ones. -- Cyril Bonté
