I have been trying to get uugetty_ps accepting incoming calls,
but after a caller connects, they are logged off immediatly by
uugetty* up the line. I turned on DEBUG=777 and
discovered uugetty was making the lock file for the line under
one process id, then somehow changing (respawning?) to a new
process id, failing to recognise its own lockfile and then
initializing the line again (hence logging off the poor
person dialing in).
"highlights" from DEBUG=777 output:
A user has just dialed in, uugetty locks the line
as process id 538, all is well:
...
Jul 19 22:24:39 magrathea uugetty[538]: D_RUN: locking the line
Jul 19 22:24:39 magrathea uugetty[538]: D_LOCK: makelock(/usr/spool/uucp/LCK..ttyS1) called
Jul 19 22:24:39 magrathea uugetty[538]: D_LOCK: temp = (/usr/spool/uucp/LCK..TM.a00538)
Jul 19 22:24:39 magrathea uugetty[538]: D_LOCK: lock made
...
The MYSTERY bit, uugetty suddenly decides to change
process id's from 538 to 736 and start itself again ?
...
Jul 19 22:25:03 magrathea uugetty[538]: D_RUN: signal set: funcs.c:495
Jul 19 22:25:03 magrathea uugetty[538]: D_RUN: alarm set: funcs.c:496
Jul 19 22:25:19 magrathea uugetty[736]: uugetty version 2.0.7d started at Tue Jul 19 22:
25:19 1994
Jul 19 22:25:19 magrathea uugetty[736]: D_DEF: defvalue(SYSTEM) called
Jul 19 22:25:19 magrathea uugetty[736]: D_DEF: defvalue returns NULL
...
Now when uugetty checks the lock files, process 538
does not exist:
...
Jul 19 22:25:22 magrathea uugetty[736]: D_RUN: checking for lockfiles...
Jul 19 22:25:22 magrathea uugetty[736]: D_LOCK: checklock(/usr/spool/uucp/LCK..ttyS1) called
Jul 19 22:25:22 magrathea uugetty[736]: D_LOCK: read 538 from the lockfile
Jul 19 22:25:22 magrathea uugetty[736]: D_LOCK: no active process has lock, will remove
...
I am using slackware 1.2.0 and getty_ps 2.0.7e, but
2.0.7d exhibits the same problem. Very rarly it will actually
actually work, and then it works great.
I guess the heart of the problem is why does
uugetty suddenly change process id's half way through a
dial in connection ? Is there a way to force it to remain
at one process id ?
Any help or ideas would be GREATLY appreciated as this
problem has been taunting me for some time.
Keith.