diff options
| -rw-r--r-- | src/log.h | 8 | ||||
| -rw-r--r-- | src/reqs.c | 4 |
2 files changed, 6 insertions, 6 deletions
@@ -1,4 +1,4 @@ -/* $Id: log.h,v 1.9 2002-04-22 19:34:19 rjkaes Exp $ +/* $Id: log.h,v 1.10 2002-05-26 18:55:19 rjkaes Exp $ * * See 'log.c' for a detailed description. * @@ -36,10 +36,10 @@ * Level Description * ----- ----------- * LOG_CRIT This is catastrophic. Basically, tinyproxy can not recover - * from this and will either close the thread (if we're lucky), + * from this and will either close the child (if we're lucky), * or the entire daemon. I would relegate this to conditions * like unable to create the listening socket, or unable to - * create a thread. If you're going to log at this level provide + * create a child. If you're going to log at this level provide * as much information as possible. * * LOG_ERR Okay, something bad happened. We can recover from this, but @@ -56,7 +56,7 @@ * * LOG_NOTICE This is for a special condition. Nothing has gone wrong, but * it is more important than the common LOG_INFO level. Right - * now it is used for actions like creating/destroying threads, + * now it is used for actions like creating/destroying children, * unauthorized access, signal handling, etc. * * LOG_CONN This additional level is for logging connections only, so @@ -1,7 +1,7 @@ -/* $Id: reqs.c,v 1.75 2002-05-24 04:45:32 rjkaes Exp $ +/* $Id: reqs.c,v 1.76 2002-05-26 18:54:56 rjkaes Exp $ * * This is where all the work in tinyproxy is actually done. Incoming - * connections have a new thread created for them. The thread then + * connections have a new child created for them. The child then * processes the headers from the client, the response from the server, * and then relays the bytes between the two. * If TUNNEL_SUPPORT is enabled, then tinyproxy will actually work |