Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mel.connect.com.au!munnari.OZ.AU!news.ecn.uoknor.edu!feed1.news.erols.com!howland.erols.net!ais.net!ameritech.net!uunet!in2.uu.net!206.67.134.2!hst1us.satlink.com!satlink!un3.satlink.com!un1!jorge From: jorge@un1.satlink.com (Jorge) Newsgroups: comp.dcom.sys.cisco,comp.unix.bsd.bsdi.misc Subject: Re: xtacacsd and bsdi Date: 5 Mar 1997 11:39:39 -0300 Organization: Satlink, Argentina Lines: 20 Message-ID: <jorge.857572498@un1> References: <331D2E1C.BBE@dragon.net.au> <E6JGJx.Fu0@spcuna.spc.edu> NNTP-Posting-Host: un1.satlink.com X-Newsreader: NN version 6.5.0 CURRENT #1 Xref: euryale.cc.adfa.oz.au comp.dcom.sys.cisco:52959 comp.unix.bsd.bsdi.misc:6213 Terry Kennedy <terry@spcuna.spc.edu> writes: >In comp.dcom.sys.cisco Boyd 'Meridian' Currey <boydc@dragon.net.au> wrote: >> We are running BSD O/S 2.0, and xtacacsd 2.0. Has anyone else seen >> this problem? Is there an incompatibilty with xtacacsd and bsdi? >> Surely xtacacsd shouldn't die, and should return a more useful message. > > Those are both pretty old versions. BSD/OS is at 3.0 now (2.1 was current > until last week) and I think the free tacacs+ server is up to 2.1 in release > state and 3.0 is available as a beta. At this point I don't know if we are talking about the xtacacs or tacacs+ daemon. I know for sure, that tacacs+ 2.1 will die frequently on machines with non-native sockets. This is because the daemon is taking a return error from the "accept" call as a fatal error and dies. But I guess that BSD O/S _is_ a native socket machine (where accept should never return a non-fatal error), so I'm not sure this is your case. Jorge