[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Bind problem on SunOS4 (was: SU for group admin)
>>reboot the SUN
You're joking. I'm just a user and there were 14 others in the who table
when I checked. I get it you don't run on mainframes often ? Ever took
your site down because you had a typo in a cron file ?
By the way ls /var/spool/mail | wc -l yields about 6000 entries on this
machine. Are you sure that you would take it down ?
>>wild shot...
It was extremely dark.
>>differences fm Linux
SUN is more BSDish than Linux. That;s ok because BSD has better IP
networking than Linux. The pun is that the server was written for BSD,
modified for Linux and now refuses to run on a SUN.
>>cluttered socket table
All the server instances exited with sigsegv. Even those that worked (i.e.
there are more bugs than is obvious). The normal thing to happen for an
unproperly closed socket followed by a bind is a regular error returned in
errno. SIGSEGV means that I tried to write to some segment I can't. And
that happens in bind. The only way this could happen imho is if
sizeof(sockaddr) < stizeof(sockaddr_in) imho.
Peter Lorand Peres
------------------
plp@actcom.co.il 100310.2360 on CIS (please use Internet address for mail)
http://ourworld.compuserve.com/homepages/plp
Follow-Ups:
References: