Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!rpi!bu.edu!wang!comm.wang.com!lws From: lws@comm.wang.com (Lyle Seaman) Newsgroups: comp.unix.sysv386 Subject: Re: SCO UNIX and setuid(2) Message-ID: <1990Dec18.213739.26892@comm.wang.com> Date: 18 Dec 90 21:37:39 GMT References: Organization: Wang Labs, Platform Comms. Lines: 14 ingea@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@capybara.comm.wang.com 508 967 2322 Lowell, MA, USA Source code: the _ultimate_ documentation.