Hi,
i run a lot telnet scripts using /dev/tcp for cisco routers, lately we
have newer models of cisco routers which have ios-xr which is based on
linux and also some mikrotik routers which are again based on linux,
on these devices when i run my script all i get is ÿý^Xÿý
ÿý#ÿý'ÿý$ÿý! in my output
On 4/28/2011 7:09 AM, Allan Pinto wrote:
Hi,
i run a lot telnet scripts using /dev/tcp for cisco routers, lately we
have newer models of cisco routers which have ios-xr which is based on
linux and also some mikrotik routers which are again based on linux,
on these devices when i run my script all
On 4/28/2011 7:09 AM, Allan Pinto wrote:
>
> Hi,
> i run a lot telnet scripts using /dev/tcp for cisco routers, lately we
> have newer models of cisco routers which have ios-xr which is based on
> linux and also some mikrotik routers which are again based on linux,
> on these devices when i run my
Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: freebsd8.0
Compiler: i686-gentoo-freebsd8.0-gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i686'
-DCONF_OSTYPE='freebsd8.0' -DCONF_MACHTYPE='i686-gentoo-freebsd8.0'
-DCONF_VENDOR='gentoo' -DLOCALEDIR='
On 4/29/11 12:25 PM, Johan Hattne wrote:
> Bash Version: 4.2
> Patch Level: 8
> Release Status: release
>
> Description:
> Following a report about a year ago, the determination of the
> executable status used by bash's built-in test command was changed.
> The original issue was that the ac
On Tuesday, April 19, 2011 16:38:57 Chet Ramey wrote:
> > seems to be just like the bug fixed in bash41-006, but with a diff for
> > loop style. simple example:
>
> Try the attached patch and let me know the results. It fixes this
> case and a couple of others.
sorry for the delay ... that patch
