Results 1 to 2 of 2

Thread: BeOS client and network sockets

  1. #1
    Downsized Chinasaur's Avatar
    Join Date
    Dec 2001
    Location
    WA Wine Country
    Posts
    1,847

    BeOS client and network sockets

    My net connection died and I was checking the Net_Server and found what seems to be about 100 Socket(99) and Socket(100) threads. My other dual BeBox has two socket threads repeated over and over. The Tbird has only one socket thread repeated.

    Any idea what's going on?

    The good news is that I ironed out all my other crash issues which seemed to be heat or RAM issues. This one doesn't crash me, but I'm wondering why it doesn't kill old socket threads when it is finished accessing the net?
    Agent Smith was right!: "I hate this place. This zoo. This prison. This reality, whatever you want to call it, I can't stand it any longer. It's the smell! If there is such a thing. I feel saturated by it. I can taste your stink and every time I do, I fear that I've somehow been infected by it."

  2. #2

    Re: BeOS client and network sockets

    Originally posted by Chinasaur
    Any idea what's going on?

    The good news is that I ironed out all my other crash issues which seemed to be heat or RAM issues. This one doesn't crash me, but I'm wondering why it doesn't kill old socket threads when it is finished accessing the net?
    I think that's a symptom of Net_Server. I seem to remember back in the day Scot Hacker posting something about that to BeUserTalk, maybe when he had switched betips.net to BONE or linux. I think it runs on linux now, at least.

    maybe set up a script to manually kill and restart Net_Server periodically, to clean up all those zombie threads.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •