On 01.12.2010 14:13 Pawel Nastachowski wrote > Wiadomość napisana przez Przemysław Knycz w dniu 2010-12-01, o godz. 14:07: >>> Apostrophes in birdc arguments should be OK because they are processed >>> by UNIX shell. >> >> Same here: >> # bash >> r...@zwrotnica:~# birdc show route 65.52.0.0/16 >> BIRD 1.2.5 ready. >> IP address expected >> r...@zwrotnica:~# birdc show route 65.52.0.0\/16 >> BIRD 1.2.5 ready. >> IP address expected >> r...@zwrotnica:~# dash >> # birdc show route 65.52.0.0\/16 >> BIRD 1.2.5 ready. >> IP address expected >> # birdc show route 65.52.0.0/16 >> BIRD 1.2.5 ready. >> IP address expected >> >> ii dash 0.5.5.1-7.2 POSIX-compliant shell >> ii bash 4.1-3 The GNU Bourne Again SHell >> GNU bash, version 4.1.5(1)-release (x86_64-pc-linux-gnu) > > waw-rs1# uname -a > FreeBSD waw-rs1 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Sun Oct 17 08:50:44 CEST > 2010 r...@waw-rs1:/usr/obj/usr/src/sys/PLIX amd64 > waw-rs1# birdc show route 65.52.0.0/16 > BIRD 1.2.5 ready. > Network not in table > waw-rs1# bash > [r...@waw-rs1 ~]# birdc show route 65.52.0.0/16 > BIRD 1.2.5 ready. > Network not in table > > FreeBSD :-))) >
So, what is the conclusion? This is a OS/shell problem, not a BIRD problem. Given so, is there anyone who is able to explain, what actually happens? I have never ever seen, that "/" irritates any program. Otoh I'm an absolute OS/shell novice ... TIA and best regards, Arnold -- Arnold Nipper / nIPper consulting, Sandhausen, Germany email: arn...@nipper.de phone: +49 6224 9259 299 mobile: +49 152 53717690 fax: +49 6224 9259 333
signature.asc
Description: OpenPGP digital signature
