[Bug 306007] Re: "Syntax error" in default bindresvport.blacklist

2011-08-10 Thread Bug Watch Updater
** Changed in: glibc (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/306007 Title: "Syntax error" in default bindresvport.blacklist To manage notifications

[Bug 306007] Re: "Syntax error" in default bindresvport.blacklist

2010-07-13 Thread Bug Watch Updater
** Changed in: glibc (Debian) Status: Unknown => New -- "Syntax error" in default bindresvport.blacklist https://bugs.launchpad.net/bugs/306007 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bu

[Bug 306007] Re: "Syntax error" in default bindresvport.blacklist

2010-07-13 Thread Jared Showalter
** Bug watch added: Debian Bug tracker #588144 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588144 ** Also affects: glibc (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=588144 Importance: Unknown Status: Unknown -- "Syntax error" in default bindresvport.blackli

[Bug 306007] Re: "Syntax error" in default bindresvport.blacklist

2010-07-13 Thread Jared Showalter
** Changed in: glibc (Ubuntu) Status: New => Confirmed -- "Syntax error" in default bindresvport.blacklist https://bugs.launchpad.net/bugs/306007 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-

[Bug 306007] Re: "Syntax error" in default bindresvport.blacklist

2010-07-13 Thread Jared Showalter
AlainKnaff's comment #3 is entirely correct. This bug is also easy to reproduce, as described in the initial comment, although as noted in comment #3, it is not tabs per se that are the problem: anything other than '#' or end-of-line is a problem. I encountered this with ypbind taking the port 63

[Bug 306007] Re: "Syntax error" in default bindresvport.blacklist

2010-02-16 Thread AlainKnaff
Just out of curiosity: why is this marked as incomplete? What is missing to make it complete? -- "Syntax error" in default bindresvport.blacklist https://bugs.launchpad.net/bugs/306007 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 306007] Re: "Syntax error" in default bindresvport.blacklist

2009-03-02 Thread AlainKnaff
Just did an apt-get source glibc, and in the diff, I found the following code snippet, in glibc-2.7/debian/patches/any/local- bindresvport_blacklist.diff , in sunrpc/bindrsvprt.c , which seems to be meant to parse one line: ++ tmp = strchr (cp, '#'); /* remove comments */ ++ if (tmp) ++

[Bug 306007] Re: "Syntax error" in default bindresvport.blacklist

2009-03-02 Thread AlainKnaff
Unfortunately not :-( r...@hitchhiker:/home/alain/cprog# ltrace -S ~alain/bin/x86_64/bindresvport SYS_brk(NULL)= 0x601000 SYS_mmap(0, 4096, 3, 34, 0x) = 0x7f0d6093 SYS_access("/etc/ld.so.nohwcap",

[Bug 306007] Re: "Syntax error" in default bindresvport.blacklist

2009-03-02 Thread Colin Watson
This is a bit mystifying, because as far as I can see the parser *does* honour tabs as you would expect. It just uses strtoul() on the whole line and thus stops at the first character that isn't part of a number. 'ltrace -S' might help to narrow down what's going on here. ** Changed in: glibc (Ub