(Illustration by Gaich Muramatsu)
On Fri, Sep 22, 2000 at 10:36:27AM -0500, Corey R. Halpin wrote: > > On Thu, Sep 21, 2000 at 06:01:17PM -0500, Corey R. Halpin wrote: > > > Venus is decidedly running, I've checked the logs and such. > > > More than that, I can move around and do things within /coda. > > > I'm at a loss. > > > > Ehh, strace codacon, and see which port it is trying to open. It should > > be either /usr/coda/spool/mariner, or whatever is specified in > > /etc/coda/venus.conf. > > > > Jan > > It was trying to bind to port 848, and failing because codacon was not set > uid, as it should have been. > Another small bug in the 5.3.8 makefile, maybe? What?? Codacon binding to an inet port?? It should try to open a unix domain socket. And it definitely does not have to run setuid! telos- ls -l /usr/bin/codacon -rwxr-xr-x 1 root root 38050 Jun 23 21:04 /usr/bin/codacon telos- ps auxwww | grep codacon jaharkes 3653 0.0 0.1 1112 188 p9 S Sep 18 2:02 codacon 'strace codacon': socket(PF_UNIX, SOCK_STREAM, 0) = 3 connect(3, {sun_family=AF_UNIX, sun_path="/usr/coda/spool/mariner"}, 110)=0 'strace codacon -tcp': socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 3 connect(3, {sin_family=AF_INET, sin_port=htons(2430), sin_addr=inet_addr("127.0.0.1")}, 16) = 0 (The mariner tcp-port on venus is by default disabled, it only exists for backwards compatibility and `demo' purposes). JanReceived on 2000-09-22 12:11:48