You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by Ceki Gulcu <cg...@urbanet.ch> on 2001/01/19 12:24:40 UTC
RE: Rollover for each day ? Is this possible ??
Jim,
Ooops! I got a DateRollingAppender from you too? Eirik Lygre has also sent
me one. Roberto Leong has too. Their contributions are attached.
Jim, can you please repost your contribution on this list? I seem to have
lost it. Sorry, I haven't been handling this item particularly well.
What I would like to see is the following:
0) Keep in mind that log4j is not in the quickie business. Much of the
success of the package can be attributed to solving problems well, not just
solving them.
1) The new appender should have flexible way of expressing the rollover
frequency, perhaps in the same format as in the Unix crontabs file which I
belive is also a Posix standard. I am not aware of any library that
supports this. JDring (http://webtools.dyade.fr/jdring/) seems to have most
of the functionality needed except parsing the crontab format. Anyone know
anything better?
As a side note, the omission of a crontab/at functionality in Java core
libraries seems like a major oversight. Try buying stock a day later then
what the customer ordered. See how many customers stay with your brokerage
house. :-)
2) The new appender should not add any significant overhead to the append
method. If appending to a file takes 100 microseconds in a particular
environment it should still take 100 microseconds with the new appender.
There are several possible designs. The first one is to check for the
rollover condition at each append. This is what Eirik Lygre has done. The
second one is to schedule a thread that will initiate the rollover after
the appropriate delay. This is what Roberto Leong has proposed.
The second approach seems more sound to me. One could generalize it by
using a single timer thread (as in JDring) to manage multiple time based
RollingAppenders. Your opinion/comments are welcome. Ceki
ps: I am forwarding this to the Avalon list since they are writing a
general purpose framework.
ps: I wonder how Tomcat addresses the issue.
At 21:45 18.01.2001 -0500, you wrote:
>Yes, but you need to use a different Appender than FileRolloverAppender.
>I've already written one, but haven't heard back from Ceki about adding it
>to the "package" yet...
>
>-Jim Moore
>
>-----Original Message-----
>From: Andrewt Tierney [mailto:andrewt@amcorp.com.au]
>Sent: Thursday, January 18, 2001 8:02 PM
>To: 'log4j-user@jakarta.apache.org'
>Subject: Rollover for each day ? Is this possible ??
>
>
>
>I see you can set the maxsize and have it automatically rollover the log
>file.
>
>Is it possible to force a new log file each day ????
>
>Thanks
>Andrew
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
>For additional commands, e-mail: log4j-user-help@jakarta.apache.org
---
Freedom as in the capacity to exercise choice.
Re: Rollover for each day ? Is this possible ??
Posted by "Craig R. McClanahan" <Cr...@eng.sun.com>.
Anders Kristensen wrote:
> [snip]
> Also, I think that when using rolling log files one would usually like
> to roll over on boundaries and not just with a certain periodicity [if
> that's even a word]. For example, one might want to roll over daily at
> midnight, rather than just daily at the time the server happened to be
> restarted at last.
>
Tomcat 4.0 has logic in its current loggers (not yet using log4j) to roll over on
the first logged message after midnight each day, as Anders described. This is
important in long-running server applications, so you don't have to restart them
simply to switch log files.
>
> Anders
>
Craig McClanahan
Re[2]: Rollover for each day ? Is this possible ??
Posted by Hendrik Lipka <he...@gmx.de>.
Friday, January 19, 2001, 1:00:20 PM, you wrote:
> Also, I think that when using rolling log files one would usually like
> to roll over on boundaries and not just with a certain periodicity [if
> that's even a word]. For example, one might want to roll over daily at
> midnight, rather than just daily at the time the server happened to be
> restarted at last.
I think the cron format just does that. You only need to specify:
year=*, month=*, day=*, hour=0, minute=0, second=0
Hendrik
Re: Rollover for each day ? Is this possible ??
Posted by "Craig R. McClanahan" <Cr...@eng.sun.com>.
Anders Kristensen wrote:
> [snip]
> Also, I think that when using rolling log files one would usually like
> to roll over on boundaries and not just with a certain periodicity [if
> that's even a word]. For example, one might want to roll over daily at
> midnight, rather than just daily at the time the server happened to be
> restarted at last.
>
Tomcat 4.0 has logic in its current loggers (not yet using log4j) to roll over on
the first logged message after midnight each day, as Anders described. This is
important in long-running server applications, so you don't have to restart them
simply to switch log files.
>
> Anders
>
Craig McClanahan
Re: Rollover for each day ? Is this possible ??
Posted by Anders Kristensen <ak...@dynamicsoft.com>.
A couple of comments. JDK 1.3 comes with timer classes in
java.util.Timer and TimerTask. They don't have the functionality of cron
but that could be built on top if necessary. Using the timer
infrastructure of java.util has the advantage that fewer threads will be
created overall in a system, and also it just makes sense to use JDK
functionality when it's there. Sure some folks aren't using JDK 1.3 --
maybe there's a downloadable library that implements the java.util timer
functions like there is for the collections lib.
Also, I think that when using rolling log files one would usually like
to roll over on boundaries and not just with a certain periodicity [if
that's even a word]. For example, one might want to roll over daily at
midnight, rather than just daily at the time the server happened to be
restarted at last.
Anders
Ceki Gulcu wrote:
>
> Jim,
>
> Ooops! I got a DateRollingAppender from you too? Eirik Lygre has also sent
> me one. Roberto Leong has too. Their contributions are attached.
> Jim, can you please repost your contribution on this list? I seem to have
> lost it. Sorry, I haven't been handling this item particularly well.
>
> What I would like to see is the following:
>
> 0) Keep in mind that log4j is not in the quickie business. Much of the
> success of the package can be attributed to solving problems well, not just
> solving them.
>
> 1) The new appender should have flexible way of expressing the rollover
> frequency, perhaps in the same format as in the Unix crontabs file which I
> belive is also a Posix standard. I am not aware of any library that
> supports this. JDring (http://webtools.dyade.fr/jdring/) seems to have most
> of the functionality needed except parsing the crontab format. Anyone know
> anything better?
>
> As a side note, the omission of a crontab/at functionality in Java core
> libraries seems like a major oversight. Try buying stock a day later then
> what the customer ordered. See how many customers stay with your brokerage
> house. :-)
>
> 2) The new appender should not add any significant overhead to the append
> method. If appending to a file takes 100 microseconds in a particular
> environment it should still take 100 microseconds with the new appender.
>
> There are several possible designs. The first one is to check for the
> rollover condition at each append. This is what Eirik Lygre has done. The
> second one is to schedule a thread that will initiate the rollover after
> the appropriate delay. This is what Roberto Leong has proposed.
>
> The second approach seems more sound to me. One could generalize it by
> using a single timer thread (as in JDring) to manage multiple time based
> RollingAppenders. Your opinion/comments are welcome. Ceki
>
> ps: I am forwarding this to the Avalon list since they are writing a
> general purpose framework.
> ps: I wonder how Tomcat addresses the issue.
>
> At 21:45 18.01.2001 -0500, you wrote:
> >Yes, but you need to use a different Appender than FileRolloverAppender.
> >I've already written one, but haven't heard back from Ceki about adding it
> >to the "package" yet...
> >
> >-Jim Moore
> >
> >-----Original Message-----
> >From: Andrewt Tierney [mailto:andrewt@amcorp.com.au]
> >Sent: Thursday, January 18, 2001 8:02 PM
> >To: 'log4j-user@jakarta.apache.org'
> >Subject: Rollover for each day ? Is this possible ??
> >
> >
> >
> >I see you can set the maxsize and have it automatically rollover the log
> >file.
> >
> >Is it possible to force a new log file each day ????
> >
> >Thanks
> >Andrew
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: log4j-user-help@jakarta.apache.org
>
> ---
> Freedom as in the capacity to exercise choice.
>
> ------------------------------------------------------------------------
> Name: DailyFileAppender.java
> DailyFileAppender.java Type: Plain Text (text/plain)
> Encoding: quoted-printable
>
> DailyFileAppender1.javName: DailyFileAppender1.jav
> Type: Plain Text (text/plain)
>
> ------------------------------------------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: log4j-user-help@jakarta.apache.org
Re[2]: Rollover for each day ? Is this possible ??
Posted by Hendrik Lipka <he...@gmx.de>.
Friday, January 19, 2001, 12:24:40 PM, you wrote:
> 1) The new appender should have flexible way of expressing the rollover
> frequency, perhaps in the same format as in the Unix crontabs file which I
> belive is also a Posix standard. I am not aware of any library that
> supports this. JDring (http://webtools.dyade.fr/jdring/) seems to have most
> of the functionality needed except parsing the crontab format. Anyone know
> anything better?
www.hendriklipka.de/java/gcp.html
This package includes a module "CommandScheduler" for executing
actions at specified intervals, and it uses the cron syntax for
configuration.
The class is "de.hendriklipka.gcp.module.control.CommandScheduler"
> As a side note, the omission of a crontab/at functionality in Java core
> libraries seems like a major oversight. Try buying stock a day later then
Implementing the parsing and the scheduling was not as easy as I was
thinking... And I'm still not sure that there are no bugs left in my
code -there are just too many special cases :(
> The second approach seems more sound to me. One could generalize it by
> using a single timer thread (as in JDring) to manage multiple time based
> RollingAppenders. Your opinion/comments are welcome. Ceki
I hope my code from the module can help you...
Hendrik Lipka
--
Re: Rollover for each day ? Is this possible ??
Posted by Anders Kristensen <ak...@dynamicsoft.com>.
A couple of comments. JDK 1.3 comes with timer classes in
java.util.Timer and TimerTask. They don't have the functionality of cron
but that could be built on top if necessary. Using the timer
infrastructure of java.util has the advantage that fewer threads will be
created overall in a system, and also it just makes sense to use JDK
functionality when it's there. Sure some folks aren't using JDK 1.3 --
maybe there's a downloadable library that implements the java.util timer
functions like there is for the collections lib.
Also, I think that when using rolling log files one would usually like
to roll over on boundaries and not just with a certain periodicity [if
that's even a word]. For example, one might want to roll over daily at
midnight, rather than just daily at the time the server happened to be
restarted at last.
Anders
Ceki Gulcu wrote:
>
> Jim,
>
> Ooops! I got a DateRollingAppender from you too? Eirik Lygre has also sent
> me one. Roberto Leong has too. Their contributions are attached.
> Jim, can you please repost your contribution on this list? I seem to have
> lost it. Sorry, I haven't been handling this item particularly well.
>
> What I would like to see is the following:
>
> 0) Keep in mind that log4j is not in the quickie business. Much of the
> success of the package can be attributed to solving problems well, not just
> solving them.
>
> 1) The new appender should have flexible way of expressing the rollover
> frequency, perhaps in the same format as in the Unix crontabs file which I
> belive is also a Posix standard. I am not aware of any library that
> supports this. JDring (http://webtools.dyade.fr/jdring/) seems to have most
> of the functionality needed except parsing the crontab format. Anyone know
> anything better?
>
> As a side note, the omission of a crontab/at functionality in Java core
> libraries seems like a major oversight. Try buying stock a day later then
> what the customer ordered. See how many customers stay with your brokerage
> house. :-)
>
> 2) The new appender should not add any significant overhead to the append
> method. If appending to a file takes 100 microseconds in a particular
> environment it should still take 100 microseconds with the new appender.
>
> There are several possible designs. The first one is to check for the
> rollover condition at each append. This is what Eirik Lygre has done. The
> second one is to schedule a thread that will initiate the rollover after
> the appropriate delay. This is what Roberto Leong has proposed.
>
> The second approach seems more sound to me. One could generalize it by
> using a single timer thread (as in JDring) to manage multiple time based
> RollingAppenders. Your opinion/comments are welcome. Ceki
>
> ps: I am forwarding this to the Avalon list since they are writing a
> general purpose framework.
> ps: I wonder how Tomcat addresses the issue.
>
> At 21:45 18.01.2001 -0500, you wrote:
> >Yes, but you need to use a different Appender than FileRolloverAppender.
> >I've already written one, but haven't heard back from Ceki about adding it
> >to the "package" yet...
> >
> >-Jim Moore
> >
> >-----Original Message-----
> >From: Andrewt Tierney [mailto:andrewt@amcorp.com.au]
> >Sent: Thursday, January 18, 2001 8:02 PM
> >To: 'log4j-user@jakarta.apache.org'
> >Subject: Rollover for each day ? Is this possible ??
> >
> >
> >
> >I see you can set the maxsize and have it automatically rollover the log
> >file.
> >
> >Is it possible to force a new log file each day ????
> >
> >Thanks
> >Andrew
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
> >For additional commands, e-mail: log4j-user-help@jakarta.apache.org
>
> ---
> Freedom as in the capacity to exercise choice.
>
> ------------------------------------------------------------------------
> Name: DailyFileAppender.java
> DailyFileAppender.java Type: Plain Text (text/plain)
> Encoding: quoted-printable
>
> DailyFileAppender1.javName: DailyFileAppender1.jav
> Type: Plain Text (text/plain)
>
> ------------------------------------------------------------------------
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: log4j-user-help@jakarta.apache.org
RE: Rollover for each day ? Is this possible ??
Posted by James Courtney <ja...@yahoo.com>.
I just joined the list and I know that it isn't open source but depending on
what you are doing there is a Java job scheduler available called Flux from
a company a friend of mine works for:
http://www.simscomputing.com/
I don't know much about it but they say it's designed to integrate with J2EE
and is operable with any number of the major databases. Clearly it isn't a
solution that can be integrated with a Tomcat release but, if you are trying
to do something with Tomcat an need scheduling and are willing to pay for
it... Just a suggestion:)
I am interested in finding out who I should correspond with on the subject
of the Apache plug in for tomcat and the IIS plug in for tomcat. If anyone
can point me in the right direction that would be great. I have some code
changes I'd like to propose but I need to speak to someone who knows the
designs well. I do not have submit rights yet on the CVS repository and I
don't know that I need them if I can find someone to review and hopefully
commit my proposed changes. If anyone would like to extend submit
privileges to me and point me at an explanation of the processes involved in
committing a change to the release version(s) of Tomcat then that would be
great to:)
Many thanks,
James Courtney
jamescourtney_1999@yahoo.com
-----Original Message-----
From: Peter Donald [mailto:donaldp@apache.org]
Sent: Sunday, January 21, 2001 4:47 AM
To: tomcat-dev@jakarta.apache.org
Cc: LOG4J Users Mailing List; roberto.leong@sibs.mailcom.pt;
eirik.lygre@evita.no; olivier.dedieu@inria.fr;
tomcat-dev@jakarta.apache.org;
java-apache-framework@list.working-dogs.com
Subject: RE: Rollover for each day ? Is this possible ??
At 12:24 19/1/01 +0100, Ceki Gulcu wrote:
>1) The new appender should have flexible way of expressing the rollover
>frequency, perhaps in the same format as in the Unix crontabs file which I
>belive is also a Posix standard. I am not aware of any library that
>supports this. JDring (http://webtools.dyade.fr/jdring/) seems to have most
>of the functionality needed except parsing the crontab format. Anyone know
>anything better?
Just as a FYI Avalon has a Crontab date timing device thingie. It is under
org.apache.avalon.blocks.scheduler.* and
org.apache.avalon.services.scheduler.*
These will eventually be removed from Avalon as it is not their place but
for now they remain...
>As a side note, the omission of a crontab/at functionality in Java core
>libraries seems like a major oversight. Try buying stock a day later then
>what the customer ordered. See how many customers stay with your brokerage
>house. :-)
I started implementing a cron server in java. The above was the very early
pieces of it. What I did was use the Cron time format and instead of
listing a command at the end (ie doSomething.sh) I used a job "name". Jobs
were defined in an Ant-like "jobfile" so that it would look like
<jobs>
<job name="foo-job" ... >
<task1 ... />
<task2 ... />
<task4 ... />
</job>
</jobs>
You could schedule 5-6000 jobs without any undue overhead. The only problem
occured with jobs that had short repeating periods but the actual job
execution took longer than repeat period. It was based on an old version of
avalon and a fork of ant I did ages ago.
Eventually when the direction of ants future is more clear I may update the
server to use newish versions of both toolkits. At that time I can put it
somewhere ala sourceforge if you are interested in it.
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, email: tomcat-dev-help@jakarta.apache.org
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
RE: Rollover for each day ? Is this possible ??
Posted by James Courtney <ja...@yahoo.com>.
I just joined the list and I know that it isn't open source but depending on
what you are doing there is a Java job scheduler available called Flux from
a company a friend of mine works for:
http://www.simscomputing.com/
I don't know much about it but they say it's designed to integrate with J2EE
and is operable with any number of the major databases. Clearly it isn't a
solution that can be integrated with a Tomcat release but, if you are trying
to do something with Tomcat an need scheduling and are willing to pay for
it... Just a suggestion:)
I am interested in finding out who I should correspond with on the subject
of the Apache plug in for tomcat and the IIS plug in for tomcat. If anyone
can point me in the right direction that would be great. I have some code
changes I'd like to propose but I need to speak to someone who knows the
designs well. I do not have submit rights yet on the CVS repository and I
don't know that I need them if I can find someone to review and hopefully
commit my proposed changes. If anyone would like to extend submit
privileges to me and point me at an explanation of the processes involved in
committing a change to the release version(s) of Tomcat then that would be
great to:)
Many thanks,
James Courtney
jamescourtney_1999@yahoo.com
-----Original Message-----
From: Peter Donald [mailto:donaldp@apache.org]
Sent: Sunday, January 21, 2001 4:47 AM
To: tomcat-dev@jakarta.apache.org
Cc: LOG4J Users Mailing List; roberto.leong@sibs.mailcom.pt;
eirik.lygre@evita.no; olivier.dedieu@inria.fr;
tomcat-dev@jakarta.apache.org;
java-apache-framework@list.working-dogs.com
Subject: RE: Rollover for each day ? Is this possible ??
At 12:24 19/1/01 +0100, Ceki Gulcu wrote:
>1) The new appender should have flexible way of expressing the rollover
>frequency, perhaps in the same format as in the Unix crontabs file which I
>belive is also a Posix standard. I am not aware of any library that
>supports this. JDring (http://webtools.dyade.fr/jdring/) seems to have most
>of the functionality needed except parsing the crontab format. Anyone know
>anything better?
Just as a FYI Avalon has a Crontab date timing device thingie. It is under
org.apache.avalon.blocks.scheduler.* and
org.apache.avalon.services.scheduler.*
These will eventually be removed from Avalon as it is not their place but
for now they remain...
>As a side note, the omission of a crontab/at functionality in Java core
>libraries seems like a major oversight. Try buying stock a day later then
>what the customer ordered. See how many customers stay with your brokerage
>house. :-)
I started implementing a cron server in java. The above was the very early
pieces of it. What I did was use the Cron time format and instead of
listing a command at the end (ie doSomething.sh) I used a job "name". Jobs
were defined in an Ant-like "jobfile" so that it would look like
<jobs>
<job name="foo-job" ... >
<task1 ... />
<task2 ... />
<task4 ... />
</job>
</jobs>
You could schedule 5-6000 jobs without any undue overhead. The only problem
occured with jobs that had short repeating periods but the actual job
execution took longer than repeat period. It was based on an old version of
avalon and a fork of ant I did ages ago.
Eventually when the direction of ants future is more clear I may update the
server to use newish versions of both toolkits. At that time I can put it
somewhere ala sourceforge if you are interested in it.
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, email: tomcat-dev-help@jakarta.apache.org
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
RE: Rollover for each day ? Is this possible ??
Posted by Peter Donald <do...@apache.org>.
At 12:24 19/1/01 +0100, Ceki Gulcu wrote:
>1) The new appender should have flexible way of expressing the rollover
>frequency, perhaps in the same format as in the Unix crontabs file which I
>belive is also a Posix standard. I am not aware of any library that
>supports this. JDring (http://webtools.dyade.fr/jdring/) seems to have most
>of the functionality needed except parsing the crontab format. Anyone know
>anything better?
Just as a FYI Avalon has a Crontab date timing device thingie. It is under
org.apache.avalon.blocks.scheduler.* and
org.apache.avalon.services.scheduler.*
These will eventually be removed from Avalon as it is not their place but
for now they remain...
>As a side note, the omission of a crontab/at functionality in Java core
>libraries seems like a major oversight. Try buying stock a day later then
>what the customer ordered. See how many customers stay with your brokerage
>house. :-)
I started implementing a cron server in java. The above was the very early
pieces of it. What I did was use the Cron time format and instead of
listing a command at the end (ie doSomething.sh) I used a job "name". Jobs
were defined in an Ant-like "jobfile" so that it would look like
<jobs>
<job name="foo-job" ... >
<task1 ... />
<task2 ... />
<task4 ... />
</job>
</jobs>
You could schedule 5-6000 jobs without any undue overhead. The only problem
occured with jobs that had short repeating periods but the actual job
execution took longer than repeat period. It was based on an old version of
avalon and a fork of ant I did ages ago.
Eventually when the direction of ants future is more clear I may update the
server to use newish versions of both toolkits. At that time I can put it
somewhere ala sourceforge if you are interested in it.
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*
RE: Rollover for each day ? Is this possible ??
Posted by Peter Donald <do...@apache.org>.
At 12:24 19/1/01 +0100, Ceki Gulcu wrote:
>1) The new appender should have flexible way of expressing the rollover
>frequency, perhaps in the same format as in the Unix crontabs file which I
>belive is also a Posix standard. I am not aware of any library that
>supports this. JDring (http://webtools.dyade.fr/jdring/) seems to have most
>of the functionality needed except parsing the crontab format. Anyone know
>anything better?
Just as a FYI Avalon has a Crontab date timing device thingie. It is under
org.apache.avalon.blocks.scheduler.* and
org.apache.avalon.services.scheduler.*
These will eventually be removed from Avalon as it is not their place but
for now they remain...
>As a side note, the omission of a crontab/at functionality in Java core
>libraries seems like a major oversight. Try buying stock a day later then
>what the customer ordered. See how many customers stay with your brokerage
>house. :-)
I started implementing a cron server in java. The above was the very early
pieces of it. What I did was use the Cron time format and instead of
listing a command at the end (ie doSomething.sh) I used a job "name". Jobs
were defined in an Ant-like "jobfile" so that it would look like
<jobs>
<job name="foo-job" ... >
<task1 ... />
<task2 ... />
<task4 ... />
</job>
</jobs>
You could schedule 5-6000 jobs without any undue overhead. The only problem
occured with jobs that had short repeating periods but the actual job
execution took longer than repeat period. It was based on an old version of
avalon and a fork of ant I did ages ago.
Eventually when the direction of ants future is more clear I may update the
server to use newish versions of both toolkits. At that time I can put it
somewhere ala sourceforge if you are interested in it.
Cheers,
Pete
*-----------------------------------------------------*
| "Faced with the choice between changing one's mind, |
| and proving that there is no need to do so - almost |
| everyone gets busy on the proof." |
| - John Kenneth Galbraith |
*-----------------------------------------------------*