SCO UNIX and setuid(2)

Lyle Seaman lws at comm.wang.com
Wed Dec 19 08:37:39 AEST 1990


ingea at IFI.UIO.NO (Inge Arnesen) writes:

>SCO UNIX SysV/386 3.2 has introduced login UID (LUID) as account
>identification. Once set, it cannot be changed (with setuid(2)). Is it
>possible to have  a daemon running as root with the LUID not set and to set
>the LUID from a forked child ?

Yup.  This is the crux of the reason that certain TCP/IP daemons don't
work correctly when you run "/etc/tcp start" manually, and why certain
other daemons don't work correctly UNLESS you run "/etc/tcp start" manually.

-- 
Lyle                  Wang           lws at capybara.comm.wang.com
508 967 2322     Lowell, MA, USA     Source code: the _ultimate_ documentation.



More information about the Comp.unix.sysv386 mailing list