search for: regex_matches

I think having this logic buried within libhid/libusb (libusb:libusb_open(), line 179 to 206) is ultimately a mistake, albeit one that I am probably responsible for. Would it make sense to confine libhid to low-level operations, and leave the decision of trying to reopen vs. retrying to open to the high-level driver, in this case usbhid-ups? I envision that the code in usbhid-ups:reconnect_ups()

...slapd[8287]: => acl_mask: to all values by "", (=n) Feb 23 17:44:36 localhost slapd[8287]: string_expand: pattern: cn=Manager,dc=tuluc,dc=com Feb 23 17:44:36 localhost slapd[8287]: => string_expand: expanded: cn=Manager,dc=tuluc,dc=com Feb 23 17:44:36 localhost slapd[8287]: => regex_matches: string:^I Feb 23 17:44:36 localhost slapd[8287]: => regex_matches: rc: 1 no matches Feb 23 17:44:36 localhost slapd[8287]: string_expand: pattern: cn=replicator,dc=tuluc,dc=com Feb 23 17:44:36 localhost slapd[8287]: => string_expand: expanded: cn=replicator,dc=tuluc,dc=com Feb 23 17:44:36...

When I use clang on Windows to compile a program using regular expressions to intermediate code, then run the result through llvm-link and finally try to generate an executable, I get an error. All of these ingredients are necessary; it works if the program doesn't use regular expressions, and it works if I compile it directly instead of going via intermediate code. The use of the exact

On Sun, Aug 23, 2009 at 8:28 PM, Chris Lattner<clattner at apple.com> wrote: > > On Aug 23, 2009, at 5:50 PM, OvermindDL1 wrote: > >> On Sun, Aug 23, 2009 at 6:32 PM, Daniel Dunbar<daniel at zuster.org> wrote: >>> >>> This is too heavy, and we don't need the extra features, and regexec >>> is well tested and much more standard. Unless there

On Aug 23, 2009, at 5:50 PM, OvermindDL1 wrote: > On Sun, Aug 23, 2009 at 6:32 PM, Daniel Dunbar<daniel at zuster.org> > wrote: >> This is too heavy, and we don't need the extra features, and regexec >> is well tested and much more standard. Unless there is an >> overwhelming > > 'regexec' I had never heard of, figured it was a library, turns

Am I wrong saying that actually anyone that use klibc has to use insmod patch or build a monolithic kernel? Could not the insmod patch be include? That will make everyone life easier on klibc upgrade. Gilles

Arjen de Korte wrote: > - HIDOpenDevice() will now handle closing the device on reload if > needed, so that HIDCloseDevice() can now really close it and free > the allocated memory for report buffer and parsed report descriptor. If I remember correctly, the old behavior on "reopen" was to keep the previous report descriptor, and try to find a device that matches the previously

Hi Folks, This is my first post on nut-upsdev. I would like to share a small patch to enable support for the Powercool PCRACK 1200VA ups. I found that the UPS uses megatec/krauler protocol but is sensitive to the USB buffer length passed to it in requests via usb_get_string(), and usb_get_string_simple(). If the buflen is greater than 102 then the ups will reply to requests but does not

Sorry about the noise guys. Below a significantly improved patch. The main difference is that all calls to usb_get_string_.. have been wrapped in a new function nut_usb_get_string()  that is implemented in libusb.c This was necessary in order to make the bufflen_fix available in libusb.c where usb_get_string() is called in libusb_open() This wrapper function mops up and hides all the work