|
Horms wrote:
>
> On Mon, Sep 11, 2000 at 09:21:35AM -0400, Joseph Mack wrote:
> > David Rodrigues wrote:
> > >
> > >
> > >I get a weird hexadecimal number on the target:port for the service.
> > >
> > > ipvsadm -a -t 192.168.1.221:80 -r 192.168.1.225 -g
> > > I get this from an ipvsadm -L
> > > Prot LocalAddress:Port Scheduler Flags
> > > -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> > > TCP C0A801DD:0050 wlc
> > > -> 01000000:0000 Masq 0 0 0
> >
> >
> > despite what you think, your ipvsadm doesn't match the ipvs version
> > you have. If you're using RedHat, it seems (from postings here)
> > that RedHat has shipped a miss-matched ipvsadm/ipvs in 6.2
>
> Actually I beleive that this particular "problem" is infact
> a patch to ipvsadm that prints values out in Hex rather than
> decimal.
my mistake then
> 0xC0A801DD = 192.168.1.221
> 0x0050 = 80
> ...
>
> Presumably Red Hat patch ipvsadm to print values out in hex to make
> it easier for elements of Piranha to parse the output of ipvsadm.
aren't computers supposed to be able to do that and present
the user with human readable output?
Joe
--
Joseph Mack PhD, Senior Systems Engineer, Lockheed Martin
contractor to the National Environmental Supercomputer Center,
mailto:mack.joseph@xxxxxxx ph# 919-541-0007, RTP, NC, USA
|
