next message in archive
next message in thread
previous message in archive
previous message in thread
Index of Subjects
Index of Subjects
On Oct 3, 8:43am, "Michael T. Smith" wrote:
} On Sat, 3 Oct 1998, John Nemeth wrote:
}
} > This I don't understand. Why didn't you just use the stuff that
} > came with Solaris (possibly bringing OS patches up to date)?
}
} Probably because we're using scsiTerminal Servers, the stsmon/pmadm/sacadm
} stuff wasn't working right. The STS docs suggested agetty which also
} didn't work right (users would hang up, and the next user to dial in would
} be dropped right into their mailbox, etc.). We chose mgetty because it
This sounds like either the modems were misconfigured (didn't
have &C1 set), there is a problem with the serial cables (CD line
looped back), there is a problem with the STS boxes (don't support CD
properly), or there is a serious bug in the STS driver. I realise
this is a very serious security issue that needed to be fixed
immediately; but, I think in the long run, it would be best to fix the
problem that the STS setup has with CD, so that it can be used with
standard system utilities.
} controls modem answering in software, so there's no chance of the modem
} answering by itself before the session's been cleaned up.
Yeah, but if you can't detect dropped sessions, then they will
stick around until idled kills them instead of being cleaned up right
away.
} > This isn't always easily done. I need an idled with an exception
} > list. I did get a preliminary one, but it was really buggy. Has that
} > been debugged yet?
}
} We have it working on Solaris, and it was working on SunOS 4 before that.
} No exception list yet although there is a stub for that in the code.
I have it working on Solaris too, but without an exception list,
I don't want to run it.
}-- End of excerpt from "Michael T. Smith"
next message in archive
next message in thread
previous message in archive
previous message in thread
Index of Subjects