Hi, I've got a weird problem with an old un-supported dentist program
that runs on Openserver 5.0.4. For some reason, it gives error
messages in certain menus if the user logs in on ttyp2, ttyp3, ttyp4
or ttyp5. Is there any way to make these 4 pseudo ttys appear to be
busy so nobody ever connects on them???

Thanks,
PW

PW Herman wrote:

> Hi, I've got a weird problem with an old un-supported dentist program
> that runs on Openserver 5.0.4. For some reason, it gives error
> messages in certain menus if the user logs in on ttyp2, ttyp3, ttyp4
> or ttyp5. Is there any way to make these 4 pseudo ttys appear to be
> busy so nobody ever connects on them???

If you open the master sides (/dev/ptyp2 etc.), they will be busied out.
You can do that with a very simple shell script that you could e.g. run
as an rc script. For example,

#!/bin/sh

# Busy out ports ttyp2, 3, 4, 5 because "un-supported dentist program"
# is allergic to them...

sleep 1000000000 < /dev/ptyp2 &
sleep 1000000000 < /dev/ptyp3 &
sleep 1000000000 < /dev/ptyp4 &
sleep 1000000000 < /dev/ptyp5 &

Save as /etc/rc2.d/S99pty-hold or something like that.

You can save a few processes if you wish (but this gets messy if you
want to busy out dozens of ports):

cd /dev
sleep 1000000000 2<ptyp2 3<ptyp3 4<ptyp4 5<ptyp5 &
# Note that shell syntax allows redirecting fd's 0-9, no higher: 10<
# does not work.

>Bela<

In article <c5a0626d.0310021152.1e7ec391@posting.google.com >,
PW Herman <pagingmrherman@hotmail.com> wrote:
>Hi, I've got a weird problem with an old un-supported dentist program
>that runs on Openserver 5.0.4. For some reason, it gives error
>messages in certain menus if the user logs in on ttyp2, ttyp3, ttyp4
>or ttyp5. Is there any way to make these 4 pseudo ttys appear to be
>busy so nobody ever connects on them???

I'd look at the permissions & ownership of the master & slave devices
associated with those.

But in any case, sure, to busy them out just open the master side:

cd /dev && sleep 1000000000 <ptyp2 1<ptyp3 2<ptyp4 3<ptyp5 &

John
--
John DuBois spcecdt@armory.com KC6QKZ/AE http://www.armory.com/~spcecdt/

Bela Lubkin <belal@sco.com> wrote in message news:<20031002213417.GL11780@sco.com>...
> PW Herman wrote:
>
> > Hi, I've got a weird problem with an old un-supported dentist program
> > that runs on Openserver 5.0.4. For some reason, it gives error
> > messages in certain menus if the user logs in on ttyp2, ttyp3, ttyp4
> > or ttyp5. Is there any way to make these 4 pseudo ttys appear to be
> > busy so nobody ever connects on them???
>
> If you open the master sides (/dev/ptyp2 etc.), they will be busied out.
> You can do that with a very simple shell script that you could e.g. run
> as an rc script. For example,
>
> #!/bin/sh
>
> # Busy out ports ttyp2, 3, 4, 5 because "un-supported dentist program"
> # is allergic to them...
>
> sleep 1000000000 < /dev/ptyp2 &
> sleep 1000000000 < /dev/ptyp3 &
> sleep 1000000000 < /dev/ptyp4 &
> sleep 1000000000 < /dev/ptyp5 &
>
> Save as /etc/rc2.d/S99pty-hold or something like that.
>
> You can save a few processes if you wish (but this gets messy if you
> want to busy out dozens of ports):
>
> cd /dev
> sleep 1000000000 2<ptyp2 3<ptyp3 4<ptyp4 5<ptyp5 &
> # Note that shell syntax allows redirecting fd's 0-9, no higher: 10<
> # does not work.
>
> >Bela<

Thanks, that's just what the doctor ordered!!!

PW