On Sat, Apr 02, 2005 at 11:03:30PM +0200, Torsten Landschoff wrote: > That code was there since 2.1.30-1 and worked all the time. Not to > mention that I am not seeing this problem. Maybe my grep is too old?
Well i can confirm this does not comes from the latest uplaod (thank you for the spring clean !). I am looking after creating a file at slapd start and running db4.2_recover in case the server was not shutdowned properly (the file being erased by the init script stop action). Would you consider such a patch (not too soon , i still have a lot to fix before adding features ..). > > the regex domain regex is broken because there is a "-" at the end: > > '^[a-zA-Z0-9-.]*$' > > echo "test.server" | grep -q '^[a-zA-Z0-9-.]*$' > > grep: Invalid range end > Interestingly this works here: > > [EMAIL PROTECTED]:~$ echo "test.server"|grep -q '^[a-zA-Z0-9-.]*$' && echo ok > ok > > What version of grep are you using? And what are you locale settings? > 2.5.1.ds1-4 from unstable. root is using C (i tried POSIX too). I also tested it with my user locale [EMAIL PROTECTED] so i end up with : grep -q '^[a-zA-Z0-9\-\.]*$' still working on my configuration and following the uber KISS law that rules all things. Does it works with your grep version ? (there was a lot of change to fix bugs for utf8 in grep range lately). There seems to be nothing about this issue in grep range in the docs ... I know they need to be escaped outside it but cannot tell about the inside. Thus i am CCing this email to grep maintainer. Greetings Alban -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
