Front page | perl.perl5.porters |
Postings from April 2012
On Thu Dec 23 09:52:19 2004, rgarciasuarez@mandrakesoft.com wrote: > erik@vontaene.de (via RT) wrote: > > I recently had the problem of having the error message > > "Setuid script not plain file" > > with every perl script I used. > > However after a _really_ long time I found out what the problem was: > > For some reason - no I don't know - /dev/null what set suid. > > The fact that perl stats /dev/null sounds like a bug to me. > Not sure why it happens. Needs investigation. > > > I don't want to write a long story here so just this: > > can you please more verbose output to your error messages? > > Just like - in this case _which_ file is set suid. > > Would be really nice. > > Before we figure out what happens, I at least documented the error: > > Change 23672 by rgs@grubert on 2004/12/23 17:21:37 > > The "Setuid script not plain file" error wasn't documented. > > Affected files ... > > ... //depot/perl/pod/perldiag.pod#393 edit > > Differences ... > > ==== //depot/perl/pod/perldiag.pod#393 (text) ==== > > @@ -3500,6 +3500,11 @@ > (F) The setuid emulator won't run a script that is writable by the > world, because the world might have written on it already. > > +=item Setuid script not plain file > + > +(F) The setuid emulator won't run a script that isn't read from a file, > +but from a socket, a pipe or another device. > + > =item shm%s not implemented > > (F) You don't have System V shared memory IPC on your system. > Looks like this error was removed at some point in the 5.8 series (it's not present in 5.8.8), so I vote to close this. --- via perlbug: queue: perl5 status: open https://rt.perl.org:443/rt3/Ticket/Display.html?id=33159Thread Previous | Thread Next