[28530] in Perl-Users-Digest

home help back first fref pref prev next nref lref last post

Perl-Users Digest, Issue: 9894 Volume: 10

daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Thu Oct 26 18:05:50 2006

Date: Thu, 26 Oct 2006 15:05:10 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)

Perl-Users Digest           Thu, 26 Oct 2006     Volume: 10 Number: 9894

Today's topics:
        ANNOUNCE: new module: Daemon::Generic ((null))
    Re: can someone unban me from freenode irc? #perl ? <bik.mido@tiscalinet.it>
    Re: Can't find string terminator ... <glennj@ncf.ca>
    Re: Check box use <tzz@lifelogs.com>
    Re: complex regular expression question <attn.steven.kuo@gmail.com>
    Re: complex regular expression question <wahab@chemie.uni-halle.de>
        Encoding problem: Rsquo to a with a hat <afrinspray@gmail.com>
    Re: Encoding problem: Rsquo to a with a hat <tadmc@augustmail.com>
        how do i update one section of a page leaving rest? <bootiack@yahoo.com>
    Re: how do i update one section of a page leaving rest? <bik.mido@tiscalinet.it>
    Re: how do i update one section of a page leaving rest? <DJStunks@gmail.com>
    Re: how do i update one section of a page leaving rest? <markrat@gmail.com>
    Re: how do i update one section of a page leaving rest? <bik.mido@tiscalinet.it>
    Re: how do i update one section of a page leaving rest? <tadmc@augustmail.com>
    Re: how do i update one section of a page leaving rest? <DJStunks@gmail.com>
        Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)

----------------------------------------------------------------------

Date: Thu, 26 Oct 2006 20:31:51 GMT
From: muir@idiom.com ((null))
Subject: ANNOUNCE: new module: Daemon::Generic
Message-Id: <J7rGFM.1656@zorch.sf-bay.org>

NAME
     Daemon::Generic - framework to provide start/stop/reload for a daemon

SYNOPSIS
     use Daemon::Generic;

     sub gd_run { ... stuff }
     sub gd_preconfig { ... stuff }

     newdaemon();

DESCRIPTION
    Daemon::Generic provides a framework for starting, stopping,
    reconfiguring daemon-like programs. The framework provides for standard
    commands that work for as init.d files and as apachectl-like commands.

    Programs that use Daemon::Generic subclass Daemon::Generic to override
    its behavior. Almost everything that Genric::Daemon does can be
    overridden as needed.

EXAMPLE USAGE OUTPUT
    Unless overriden, the usage output for your program will look something
    like this:

     Usage: $progname [ -c file ] [ -f ] { start | stop | reload | restart | help | version | check }
      -c            Specify configuration file (defaults to $configfile)
      -f            Run in the foreground (don't detach)
      start         Starts a new $progname if there isn't one running already
      stop          Stops a running $progname
      reload        Causes a running $progname to reload it's config file.  Starts
                    a new one if none is running.
      restart       Stops a running $progname if one is running.  Starts a new one.
      check         Check the configuration file and report the daemon state
      help          Display this usage info
      version       Display the version of $progname

CONSTRUCTION
    To hand control over to "Daemon::Generic", call "newdaemon()". Control
    will be handed back through method calls to functions you define.

    Your @ISA will be modified to include "Daemon::Generic" if if it isn't
    already there.

    These are the arguments to "newdaemon()". Defaults are in (parenthesis).

    progname       ($0) The name of this program. This will be used for
                   logging and for naming the PID file.

    configfile     ("/etc/$progname.conf") The location of the configuration
                   file for this daemon.

    pidbase        (/var/run/$progname) We include the configuration file
                   name as part of the pid file in case there are multiple
                   instances of this deamon. The pidbase is is the part of
                   the PID file that does not include the configuration file
                   name.

    pidfile        ("$pidbase.$configfile.pid") The location of the process
                   id file.

    foreground     (0) Do not detach/daemon and run in the foreground
                   instead.

    debug          (0) Turn on debugging.

    no_srand       (0) Normall srand() is called. If no_srand is set then
                   srand() won't be called.

    options        () Additional arguments for Getopt::Long::GetOptions
                   which is used to parse @ARGV. Alternatively: define
                   "&gd_more_opt()".

    minimum_args   (1) Minimum number of @ARGV arguments after flags have
                   been processed.

    maximum_args   (1) Maximum number of @ARGV arguments after flags have
                   been processed.

    version        ($pkg::VERSION) The version number of the daemon.

MUST-OVERRIDE CALLBACK METHODS
    The package that subclasses Daemon::Generic must provide the following
    callback methods.

    gd_preconfig() "gd_preconfig()" is called to parse the configuration
                   file ("$self->{configfile}"). Preconfig is called on all
                   invocations of the daemon ("daemon reload", "daemon
                   check", "daemon stop", etc). It shouldn't start anything
                   but it can and should verify that the config file is
                   fine.

                   The return value should be a hash. With one exception,
                   the return value is only used by "gd_postconfig()". The
                   exception is that "gd_preconfig()" may return a revised
                   PID file location (key "pidfile").

    gd_run()       This is where you put your main program.

MAY-OVERRIDE CALLBACK METHODS
    The package that subclasses Daemon::Generic does not have to override
    these methods but it may want to.

    gd_postconfig(%config)
                   Postconfig() is called only when the daeamon is actually
                   starting up. (Or on reconfigs). It is passed the return
                   value from "gd_preconfig".

    gd_setup_signals()
                   Set things up so that SIGHUP calls gd_reconfig_event()
                   and SIGINT calls gd_quit_event(). It will call these at
                   any time so if you want to delay signal delivery or
                   something you should override this method.

    gd_getopt()    This is invoked to parse the command line. Useful things
                   to modify are:

                   $self->{configfile} The location of the configuration
                                       file to be parsed by
                                       "gd_preconfig()".

                   $self->{foreground} Run in the foreground (don't
                                       daemonize).

                   $self->{debug}      Use it yourself.

                   The supplied "gd_getopt()" method uses Getopt::Long.

    gd_parse_argv()
                   Parse any additional command line arguments beyond what
                   "gd_getopt()" handled.

                   $ARGV[0] needs to be left alone if it is one of the
                   following standard items:

                   start     Start up a new daemon.

                   stop      Stop the running daemon.

                   restart   Stop the running daemon, start a new one.

                   reload    Send a signal to the running daemon, asking it
                             to reconfigure itself.

                   check     Just check the configuration file.

                   help      Print the help screen (probably usage()).

                   version   Display the daemon's version.

                   There is no default "gd_parse_argv()".

    gd_check($pidfile, $pid)
                   Normal behavior: return. Define additional checks to run
                   when the "check" command is given. A $pid will only be
                   supplied if there is a daemon running.

    gd_version()   Normal behavior: display a version message and exit.

    gd_help()      Normal behavior: call "gd_usage()".

    gd_commands_more()
                   Used by "gd_usage()": provide information on additional
                   commands beyond "start", "stop", "reload", etc. Return is
                   an array of key value pairs.

                    sub gd_commands_more 
                    {
                           return (
                                   savestate => 'Tell xyz server to save its state',
                                   reset     => 'Tell xyz servr to reset',
                           );
                    }

    gd_flags_more  Like "gd_commands_more()" but defines additional command
                   line flags. There should also be a "gd_more_opt()" or an
                   "options" argument to "new()".

    gd_positional_more
                   Like "gd_commands_more()" but defines positional
                   arguments.

    gd_usage()     Display a usage message. The return value from
                   "gd_usage()" is the exit code for the program.

    gd_more_opt()  () Additional arguments for Getopt::Long::GetOptions
                   which is used to parse @ARGV. Alternatively: pass
                   "options" to "new()".

    gd_pidfile()   Figure out the PID file should be.

    gd_error()     Print out an error (call die?)

    gd_other_cmd() Called $ARGV[0] isn't one of the commands that
                   Daemon::Generic knows by default. Default behavior: call
                   "gd_usage()" and exit(1).

    gd_daemonize() Normal behavior: "fork()", "fork()", detach from tty.

    gd_redirect_output()
                   Normal behavior: redirect "STDOUT" and "STDERR" to
                   "logger -t $progname[$$]". Used by "gd_daemonize()".

    gd_logname()   Normal behavior: $progname[$$]. Used by
                   "gd_redirect_output()".

    gd_reconfig_event()
                   Normal behavior: call "gd_postconfig(gd_preconfig))".
                   Only referenced by "gd_setup_signals()".

    gd_quit_event()
                   Normal behavior: exit. Only referenced by
                   "gd_setup_signals()".

    gd_kill($pid)  Used by the "stop" and "restart" commands to get rid of
                   the old daemon. Normal behavior: send a SIGINT. Check to
                   see if process $pid has died. If it has not, keep
                   checking and if it's still alive. After
                   $Daemon::Generic::force_quit_delay seconds, send a
                   SIGTERM. Keep checking. After another
                   $Daemon::Generic::force_quit_delay seconds, send a
                   SIGKILL (-9). Keep checking. After
                   "$Daemon::Generic::force_quit_delay * 4" seconds or 60
                   seconds (whichever is smaller), give up and exit(1).

    gd_install     Installs the daemon so that it runs automatically at next
                   reboot. Currently done with a symlink to $0 and
                   "/usr/sbin/update-rc.d". Please send patches for other
                   methods!

    gd_can_install Returns a function to do an "gd_install" if installation
                   is possible. Returns 0 otherwise.

    gd_install_pre($method)
                   Normal behavior: return. Called just before doing an
                   installation. The method indicates the installation
                   method (currently always "update-rc.d".)

    gd_install_post($method)
                   Normal behavior: return. Called just after doing an
                   installation.

    gd_uninstall   Will remove the daemon from the automatic startup regime.

    gd_can_uninstall
                   Returns a function to do the work for "gd_uninstall" if
                   it's possible. 0 otherwise.

    gd_uninstall_pre($method)
                   Normal behavior: return. Called just before doing an
                   un-installation. The method indicates the installation
                   method (currently always "update-rc.d".)

    gd_install_post($method)
                   Normal behavior: return. Called just after doing an
                   un-installation.

MEMBER DATA
    Since you need to subclass Daemon::Generic, you need to know what the
    internal data structures for Daemon::Generic are. With two exceptions,
    all of the member data items begin with the prefix "gd_".

    configfile     The location of the configuration file. (Not used by
                   Daemon::Generic).

    debug          Display debugging? (Not used by Daemon::Generic)

    gd_args        The original %args passed to "new".

    gd_progname    The process name. (defaults to $0)

    gd_pidfile     The location of the process ID file.

    gd_foreground  Are we running in the foreground?

EXAMPLE PROGRAM
     my $sleeptime = 1;

     newdaemon(
            progname        => 'ticktockd',
            pidfile         => '/var/run/ticktockd.pid',
            configfile      => '/etc/ticktockd.conf',
     );

     sub gd_preconfig
     {
            my ($self) = @_;
            open(CONFIG, "<$self->{gd_configfile}") or die;
            while(<CONFIG>) {
                    $sleeptime = $1 if /^sleeptime\s+(\d+)/;
            }
            close(CONFIG);
            return ();
     }

     sub gd_run
     {
            while(1) {
                    sleep($sleeptime);
                    print scalar(localtime(time))."\n";
            }
     }

SEE ALSO
    With a while(1) and delayed signal delivery: Daemon::Generic::While1.

    With Event: Daemon::Generic::Event.

    Other modules that do similar things: Net::Daemon, Net::Server,
    Net::Server::Daemonize, NetServer::Generic, Proc::Application::Daemon,
    Proc::Daemon, Proc::Forking.

LICENSE
    Copyright(C) 2006 David Muir Sharnoff <muir@idiom.com>. This module may
    be used and distributed on the same terms as Perl itself.

-- 




------------------------------

Date: 26 Oct 2006 21:25:11 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: can someone unban me from freenode irc? #perl ?
Message-Id: <vq22k2lupmctt5dd84ihs3rjeh2t8jqd3t@4ax.com>

On 26 Oct 2006 09:30:08 -0700, "gavino" <bootiack@yahoo.com> wrote:

>Michele calm down, go jack off or something.  I like perl much better
>than ja-vaa!!!

Me to-oo. So wha-aat?!?


Michele
-- 
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
 .'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,


------------------------------

Date: 26 Oct 2006 18:29:15 GMT
From: Glenn Jackman <glennj@ncf.ca>
Subject: Re: Can't find string terminator ...
Message-Id: <slrnek1vjr.3c3.glennj@smeagol.ncf.ca>

At 2006-10-26 12:37PM, "Henry Law" wrote:
>  Amer Neely wrote:
>  
> > seems more likely to be an artifact of something else. Notepad has some 
> > quirky behaviour as well. Try this:
> > 1. Open Notepad
> > 2. Type the text "this app can break" (without quotes)
> > 3. Save the file
> > 4. Re-open the file in Notepad
>  
>  The weirdest thing I've seen.

Notepad is wrongly interpreting that file as unicode.
Explained at http://en.wikipedia.org/wiki/Notepad


-- 
Glenn Jackman
Ulterior Designer


------------------------------

Date: Thu, 26 Oct 2006 20:38:30 +0100
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: Check box use
Message-Id: <g69pscehnpl.fsf@lifelogs.com>

On 26 Oct 2006, krakle@visto.com wrote:

> Which proves that most programmers are anti-social geeks who don't
> know how to speak to someone properly.

You forgot "can't get a date" and "live in their parents' basement."
If you are going to stereotype, do it right.

Ted


------------------------------

Date: 26 Oct 2006 11:42:32 -0700
From: "attn.steven.kuo@gmail.com" <attn.steven.kuo@gmail.com>
Subject: Re: complex regular expression question
Message-Id: <1161888152.428561.170180@e3g2000cwe.googlegroups.com>



On Oct 26, 9:18 am, "markpark" <mark.le...@morganstanley.com> wrote:
> I know perl is good for what i need to do but i find regular
> expressions very difficult and
> and this is what i think is needed.
>
> IBM2006-09-29 09:30:03.00000N7800081.90000000N003398C
> IBM2006-09-29 09:30:04.00006N70081.90000000N003412C
>
> I have a lines in a file such as above and all i want to pull is the
> fields
>
> date and time ( 1 field )
>
> 2006-09-29 09:30:03
>
> and the price
>
> 81.9
>
> and write them out top a file with a comma in between the two fields.
>
> i don't even want the letters IBM in the output.
>
> an additional complication is is that there are cases where the price
> could be in the hundreds in
> which case, it has to be taken out to 3 digits before the decimal
> rather than just 2.
>
> another additional complication is that the stock could be MSFT in
> which
> case therew are 4 characters first instead of 3.
>
> so , essentially, the price is always the four numbers before the
> second dot in the file
> but the 2 digits after the second dot are part of the price also.
>
> if that helps ?
>
> this problem seems like a mess to me.



Yes, considering how some stocks
have prices that exceed $9999.99 -- ever heard of
Berkshire Hathaway (ticker symbol
BRK-A as listed on the NYSE)?  At current valuations,
that may be listed in your "report" with something
like:

BRK-A2006-10-26 09:30:04.00006N ... 104500.00000000N003412C

If you limit yourself to 4 digits before the decimal separator
you would seriously undervalue that stock.  It seems
you need to better define how these strings are encoded.

-- 
Regards,
Steven



------------------------------

Date: Thu, 26 Oct 2006 20:56:50 +0200
From: Mirco Wahab <wahab@chemie.uni-halle.de>
Subject: Re: complex regular expression question
Message-Id: <ehr0l8$pdr$1@mlucom4.urz.uni-halle.de>

Thus spoke Mirco Wahab (on 2006-10-26 19:18):
>         my ($d,$t) =  $fields[0] =~ /\D+([-\d]+)\s+(.+?)$/;
>         my  $buck  = ($fields[1] =~ /(\d{4})$/)[0] + 0;
>         my ($cent) =  $fields[2] =~ /^(\d{2})/;


According to Stevens remark, one would better
write the extracion like:

  ...
  while(<DATA>) {
    if( (my @fields = split /\./)   > 2 ) {
      my ($d,$t) =  $fields[0] =~ /(\d{4}-[-\d]+)\s+(.+?)$/;
      my  $buck  = ($fields[1] =~ /(\d{4})$/)[0] + 0;
      my ($cent) =  $fields[2] =~ /^(\d{2})/;
      printf "$d $t, %7.2f \$\n", $buck+$cent/100;
   }
 }
 ...

which would handle things like 4-digit stock prices
and company names like T3332006-09-29-...

Regards

Mirco


------------------------------

Date: 26 Oct 2006 12:08:59 -0700
From: "afrinspray" <afrinspray@gmail.com>
Subject: Encoding problem: Rsquo to a with a hat
Message-Id: <1161889739.619425.24110@b28g2000cwb.googlegroups.com>

I posted a message titled "Best way to remove body/html tag from
HTML::Element tree" on Sep 6 2006.

Tad McClellan helped me out by referring me to
http://perlmonks.org/?node_id=3D554219 which explains using
XML::SAX::Writer.  Everything was going well with the tag parsing until
I started giving the sax parser special characters for quotes:

Hopefully these characters make it through... it's converting:
& r s q u o ; (no spaces)
to:=20
=E2 (a with a hat)

Thanks in advance....


Mike



------------------------------

Date: Thu, 26 Oct 2006 16:02:08 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: Encoding problem: Rsquo to a with a hat
Message-Id: <slrnek28ig.gtl.tadmc@tadmc30.august.net>

afrinspray <afrinspray@gmail.com> wrote:

> Tad McClellan helped me out by referring me to
> http://perlmonks.org/?node_id=554219


No I didn't.


-- 
    Tad McClellan                          SGML consulting
    tadmc@augustmail.com                   Perl programming
    Fort Worth, Texas


------------------------------

Date: 26 Oct 2006 11:42:41 -0700
From: "gavino" <bootiack@yahoo.com>
Subject: how do i update one section of a page leaving rest?
Message-Id: <1161888161.308042.136520@m7g2000cwm.googlegroups.com>

How Do i updae one section of  a page leaving the rest?



------------------------------

Date: 26 Oct 2006 21:27:06 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: how do i update one section of a page leaving rest?
Message-Id: <5u22k2p72njco5bo8naqa7u3seda2bfacj@4ax.com>

On 26 Oct 2006 11:42:41 -0700, "gavino" <bootiack@yahoo.com> wrote:

>How Do i updae one section of  a page leaving the rest?

$page =~ s/$startsection.*?$endsection/;


Michele
-- 
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
 .'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,


------------------------------

Date: 26 Oct 2006 12:45:31 -0700
From: "DJ Stunks" <DJStunks@gmail.com>
Subject: Re: how do i update one section of a page leaving rest?
Message-Id: <1161891931.396270.67820@e3g2000cwe.googlegroups.com>


Michele Dondi wrote:
> On 26 Oct 2006 11:42:41 -0700, "gavino" <bootiack@yahoo.com> wrote:
>
> >How Do i updae one section of  a page leaving the rest?
>
> $page =~ s/$startsection.*?$endsection/;

well I hate to do this, but

  Substitution replacement not terminated at -e line 1.

haha,
-jp



------------------------------

Date: 26 Oct 2006 13:09:19 -0700
From: "MarkRat" <markrat@gmail.com>
Subject: Re: how do i update one section of a page leaving rest?
Message-Id: <1161893359.765033.275300@f16g2000cwb.googlegroups.com>


gavino wrote:
> How Do i updae one section of  a page leaving the rest?

use CGI::Ajax



------------------------------

Date: 26 Oct 2006 23:01:53 +0200
From: Michele Dondi <bik.mido@tiscalinet.it>
Subject: Re: how do i update one section of a page leaving rest?
Message-Id: <bc82k29mkh5t07ciukh6c144k3rhk0elmg@4ax.com>

On 26 Oct 2006 12:45:31 -0700, "DJ Stunks" <DJStunks@gmail.com> wrote:

>> $page =~ s/$startsection.*?$endsection/;
>
>well I hate to do this, but
>
>  Substitution replacement not terminated at -e line 1.

(How do you know it was on -e line 1? Actually it wasn't!! :-)

Why do you hate to do so? We're not here advertise broken code. My
mistake, I stand corrected:

$page =~ s/$startsection(.*?)$endsection/update_section($1)/e;


Michele
-- 
{$_=pack'B8'x25,unpack'A8'x32,$a^=sub{pop^pop}->(map substr
(($a||=join'',map--$|x$_,(unpack'w',unpack'u','G^<R<Y]*YB='
 .'KYU;*EVH[.FHF2W+#"\Z*5TI/ER<Z`S(G.DZZ9OX0Z')=~/./g)x2,$_,
256),7,249);s/[^\w,]/ /g;$ \=/^J/?$/:"\r";print,redo}#JAPH,


------------------------------

Date: Thu, 26 Oct 2006 15:55:33 -0500
From: Tad McClellan <tadmc@augustmail.com>
Subject: Re: how do i update one section of a page leaving rest?
Message-Id: <slrnek2865.gtl.tadmc@tadmc30.august.net>

gavino <bootiack@yahoo.com> wrote:

> How Do i updae one section of  a page leaving the rest?


By writing a Perl program that updates one section of a page
and leaving the rest.


-- 
    Tad McClellan                          SGML consulting
    tadmc@augustmail.com                   Perl programming
    Fort Worth, Texas


------------------------------

Date: 26 Oct 2006 14:21:22 -0700
From: "DJ Stunks" <DJStunks@gmail.com>
Subject: Re: how do i update one section of a page leaving rest?
Message-Id: <1161897682.324378.56360@m7g2000cwm.googlegroups.com>


Michele Dondi wrote:
> On 26 Oct 2006 12:45:31 -0700, "DJ Stunks" <DJStunks@gmail.com> wrote:
>
> >> $page =~ s/$startsection.*?$endsection/;
> >
> >well I hate to do this, but
> >
> >  Substitution replacement not terminated at -e line 1.
>
> (How do you know it was on -e line 1? Actually it wasn't!! :-)
>
> Why do you hate to do so? We're not here advertise broken code. My
> mistake, I stand corrected:
>
> $page =~ s/$startsection(.*?)$endsection/update_section($1)/e;

just because this is a stupid thread started by an even stupider troll
and because I know you know better :)

picking nits,
-jp



------------------------------

Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin) 
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>


Administrivia:

#The Perl-Users Digest is a retransmission of the USENET newsgroup
#comp.lang.perl.misc.  For subscription or unsubscription requests, send
#the single line:
#
#	subscribe perl-users
#or:
#	unsubscribe perl-users
#
#to almanac@ruby.oce.orst.edu.  

NOTE: due to the current flood of worm email banging on ruby, the smtp
server on ruby has been shut off until further notice. 

To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.

#To request back copies (available for a week or so), send your request
#to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
#where x is the volume number and y is the issue number.

#For other requests pertaining to the digest, send mail to
#perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
#sending perl questions to the -request address, I don't have time to
#answer them even if I did know the answer.


------------------------------
End of Perl-Users Digest V10 Issue 9894
***************************************


home help back first fref pref prev next nref lref last post