diff options
author | Jarkko Hietaniemi <jhi@iki.fi> | 2000-08-14 14:08:28 +0000 |
---|---|---|
committer | Jarkko Hietaniemi <jhi@iki.fi> | 2000-08-14 14:08:28 +0000 |
commit | 0325b4c4b7ee03ae5602904f2a8f8c7254d59b1b (patch) | |
tree | db267340f71bb0f6d130629998bccf12b022770b | |
parent | 3170649431eb5688b22560d1c824cf4b7252a79c (diff) | |
download | perl-0325b4c4b7ee03ae5602904f2a8f8c7254d59b1b.tar.gz |
Drop the eg/ mentions and also mention the recent suidperl thing.
p4raw-id: //depot/perl@6617
-rw-r--r-- | jpl/README | 3 | ||||
-rw-r--r-- | lib/ExtUtils/Embed.pm | 2 | ||||
-rw-r--r-- | pod/perlcompile.pod | 3 | ||||
-rw-r--r-- | pod/perlfaq8.pod | 9 | ||||
-rw-r--r-- | pod/perlsec.pod | 11 |
5 files changed, 6 insertions, 22 deletions
diff --git a/jpl/README b/jpl/README index 57f52c4f71..66da2ec5a0 100644 --- a/jpl/README +++ b/jpl/README @@ -224,8 +224,7 @@ Information on accessing the bleeding edge JPL via CVS can be found at: More Info --------- -You can look at the Sample and Test directories, as well as the ../eg -directory for examples. +You can look at the Sample and Test directories. Perhaps the most important bit of advice we can give you is to watch diff --git a/lib/ExtUtils/Embed.pm b/lib/ExtUtils/Embed.pm index b649b6b77b..863ab7e005 100644 --- a/lib/ExtUtils/Embed.pm +++ b/lib/ExtUtils/Embed.pm @@ -484,7 +484,7 @@ B<xsinit()> uses the xsi_* functions to generate most of it's code. =head1 EXAMPLES For examples on how to use B<ExtUtils::Embed> for building C/C++ applications -with embedded perl, see the eg/ directory and L<perlembed>. +with embedded perl, see L<perlembed>. =head1 SEE ALSO diff --git a/pod/perlcompile.pod b/pod/perlcompile.pod index e5544ec444..282592e9fb 100644 --- a/pod/perlcompile.pod +++ b/pod/perlcompile.pod @@ -183,9 +183,6 @@ one-liners: rename $was, $_ unless $was eq $_; } -(this is the I<rename> program that comes in the I<eg/> directory -of the Perl source distribution). - The decompiler has several options for the code it generates. For instance, you can set the size of each indent from 4 (as above) to 2 with: diff --git a/pod/perlfaq8.pod b/pod/perlfaq8.pod index ed22ba0c59..0ac462021b 100644 --- a/pod/perlfaq8.pod +++ b/pod/perlfaq8.pod @@ -443,9 +443,8 @@ probably get away with setting an environment variable: If you want finer granularity than the 1 second that the sleep() function provides, the easiest way is to use the select() function as -documented in L<perlfunc/"select">. If your system has itimers and -syscall() support, you can check out the old example in -http://www.perl.com/CPAN/doc/misc/ancient/tutorial/eg/itimers.pl . +documented in L<perlfunc/"select">. Try the Time::HiRes and +the BSD::Itimer modules (available from CPAN). =head2 How can I measure time under a second? @@ -906,10 +905,6 @@ Background yourself like this: The Proc::Daemon module, available from CPAN, provides a function to perform these actions for you. -=head2 How do I make my program run with sh and csh? - -See the F<eg/nih> script (part of the perl source distribution). - =head2 How do I find out if I'm running interactively or not? Good question. Sometimes C<-t STDIN> and C<-t STDOUT> can give clues, diff --git a/pod/perlsec.pod b/pod/perlsec.pod index 4185e84803..6b50b92f96 100644 --- a/pod/perlsec.pod +++ b/pod/perlsec.pod @@ -291,12 +291,6 @@ in C: Compile this wrapper into a binary executable and then make I<it> rather than your script setuid or setgid. -See the program B<wrapsuid> in the F<eg> directory of your Perl -distribution for a convenient way to do this automatically for all your -setuid Perl programs. It moves setuid scripts into files with the same -name plus a leading dot, and then compiles a wrapper like the one above -for each of them. - In recent years, vendors have begun to supply systems free of this inherent security bug. On such systems, when the kernel passes the name of the set-id script to open to the interpreter, rather than using a @@ -308,9 +302,8 @@ program that builds Perl tries to figure this out for itself, so you should never have to specify this yourself. Most modern releases of SysVr4 and BSD 4.4 use this approach to avoid the kernel race condition. -Prior to release 5.003 of Perl, a bug in the code of B<suidperl> could -introduce a security hole in systems compiled with strict POSIX -compliance. +Prior to release 5.6.1 of Perl, bugs in the code of B<suidperl> could +introduce a security hole. =head2 Protecting Your Programs |