hacker@vela.acs.oakland.edu (Thomas J. Hacker) (04/27/91)
Hello again! Well, I'm attempting to start ISIS on a DECStation 5000, running Ultrix 4.1, and I get the message in the subject line, and then it dies. here's the pertinent service entries isis 1601/udp isis 1602/tcp isis 1603/bcast and site + 001:1601,1602,1603 mars.acs.oakland.edu acs,decstation + 002:1601,1602,1603 saturn.acs.oakland.edu acs,decstation I think the protos process starts, so I'm wondering if the process detector isn't detecting. Any help would be appreciated. -Thanks! -Tom
ken@CS.Cornell.EDU (Ken Birman) (04/27/91)
In article <6149@vela.acs.oakland.edu> hacker@vela.acs.oakland.edu (Thomas J. Hacker) writes: > >Hello again! > >Well, I'm attempting to start ISIS on a DECStation 5000, running Ultrix 4.1, >and I get the message in the subject line, and then it dies. > >here's the pertinent service entries >isis 1601/udp >isis 1602/tcp >isis 1603/bcast > >and site >+ 001:1601,1602,1603 mars.acs.oakland.edu acs,decstation >+ 002:1601,1602,1603 saturn.acs.oakland.edu acs,decstation > >I think the protos process starts, so I'm wondering if the process detector >isn't detecting. > >Any help would be appreciated. > >-Thanks! >-Tom This is usually due to a "well known" bug in V2.1... in protos/pr_client.c there is a call to chmod(ux_addr.sun_path, 0x666); the mode should be 0666: chmod(ux_addr.sun_path, 0666); If the problem still occurs with this change, something is probably wrong with write permissions in /tmp, i.e. someone else ran ISIS and left the ISIS named socket around in a mode that you can't unlink (this will be a file named /tmp/Is1602 in your case) Ken -- Kenneth P. Birman E-mail: ken@cs.cornell.edu 4105 Upson Hall, Dept. of Computer Science TEL: 607 255-9199 (office) Cornell University Ithaca, NY 14853 (USA) FAX: 607 255-4428