We've recently moved from a 10.4 to a 10.5 setup and now have an odd
problem.
The 10.5 server is running as an Open Directory Master with a number
of other unix systems configured as LDAP client systems. One of the
purposes of the server is to run a build management python script
that uses ssh to connect to the various unix client systems and run
builds, transferring source and results with scp. This worked
perfectly under 10.4. We didn't upgrade from 10.4 but setup a new
installation on a new server, although there wasn't anything non-
standard about the 10.4 original setup.
With 10.5, if the initiating session on the server is left logged in
(via ssh from a workstation) then all continues to work. However, if
the build script process is daemonised and the initiating ssh
session terminated then the ssh and scp commands issued by the build
script fail with 'You don't exist, go away!'. This was not an issue
with 10.4 and its important that daemonised build processes work as
they can run for more than 24 hours and can also be started by
crontab.
I've read various articles about this message and ssh, to do with
chroot and whether the user id in question is present in /etc/
passwd, but this would not seem to be relevant when the user info is
coming from LDAP.
This said, Leopard Tiger are in reality two different Operating
Systems, and their internals are rather different, especially with
respect to processes. IIRC ttys are no longer attached to many process
types (such as daemons) and ssh maybe expecting a terminal. However to
comment beyond that without the information formerly mentioned would
be wild guesses.
-dhan
------------------------------------------------------------------------
Dan Shoop
Computer Scientist
iWiring / U.S. Technical Services
