lilproxy-project — Main List

[Lilproxy-project] Adding Performance ( parallelism )

[Buggs <bug...@sp...>]

Hoi,

To add a bit more performance to lilproxy,
we got to add some parallelism.

We could utilize:

A) forking, which is very stable on POSIX systems,
	so not as stable on Win9x.

B) threading, which has general problems with current perl versions,
	but sure is very interesting.

C) selecting, very nice aproach via select(2),
	so also problems on windows.

D) POOPing, Problem Of Other People, use a module like LWP::Parallel.

E) Something, I forgot.

F) All of the above, we then need a good switching system.


To me stability is not an issue,
since parallelism can be turned off.

Any ideas, preferences, experiences?

Buggs

[Lilproxy-project] Added lilget to docu

[Buggs <bug...@sp...>]

Hoi Hoi,

lilget is a short programm which uses Socket.pm
to fetch a HTML document from http://www.perl.com.
This is very raw, you should usually prefer IO::Socket,
the OO interface, which is much easier to use,
or even LWP::Simple.

See
https://sourceforge.net/docman/index.php?group_id=28612
http://sourceforge.net/docman/index.php?group_id=28612


Buggs

Re: [Lilproxy-project] WinCVS Docu ?

[Andy <ah...@sp...>]

@Dienstag, 10. Juli 2001 19:59 David Irvine:
> ----- Original Message -----
> From: Buggs <bug...@sp...>
> To: <Lil...@li...>
> Sent: Tuesday, July 10, 2001 12:20 AM
> Subject: Re: [Lilproxy-project] WinCVS Docu ?
>
> > @Sonntag, 8. Juli 2001 19:41 David Irvine:
> > > Will get to work to work on an idiots guide to getting
> > > stuff on and off cvs using wincvs, real cvs and the
> > > online slashdot thingy.
> >
> > Cool.
> >
> > BTW we call it "Getting started" not idiots guide,
> > although it has not such a bad meaning
> > in software buisiness one could think of,
> > just not to hurt anyone's feelings :)
>
> Hehe, will remember to
>
> use politically:correct;
>
> in the future :P
>

LOL ... fuck^H^H^H^H darn now I spilled my coffee.

Buggs

Re: [Lilproxy-project] WinCVS Docu ?

[David I. <co...@ya...>]

----- Original Message -----
From: Buggs <bug...@sp...>
To: <Lil...@li...>
Sent: Tuesday, July 10, 2001 12:20 AM
Subject: Re: [Lilproxy-project] WinCVS Docu ?


> @Sonntag, 8. Juli 2001 19:41 David Irvine:
> > Will get to work to work on an idiots guide to getting
> > stuff on and off cvs using wincvs, real cvs and the
> > online slashdot thingy.
>
> Cool.
>
> BTW we call it "Getting started" not idiots guide,
> although it has not such a bad meaning
> in software buisiness one could think of,
> just not to hurt anyone's feelings :)
>

Hehe, will remember to

use politically:correct;

in the future :P


> > Hopefully it will make sense and wont contain too many
> > outright lies :)
>
> Docu is a beast, isn't it?
> I always miss the compiler warnings ;-)
>

Started reading and fiddling today so hopefully by the weekend i'll have
something to show for it.

Cheers

David

Re: [Lilproxy-project] WinCVS Docu ?

[Buggs <bug...@sp...>]

@Sonntag, 8. Juli 2001 19:41 David Irvine:
> Will get to work to work on an idiots guide to getting
> stuff on and off cvs using wincvs, real cvs and the
> online slashdot thingy.

Cool.

BTW we call it "Getting started" not idiots guide,
although it has not such a bad meaning
in software buisiness one could think of,
just not to hurt anyone's feelings :)

> Hopefully it will make sense and wont contain too many
> outright lies :)

Docu is a beast, isn't it?
I always miss the compiler warnings ;-)


Buggs

Re: [Lilproxy-project] WinCVS Docu ?

[David I. <co...@ya...>]

Will get to work to work on an idiots guide to getting
stuff on and off cvs using wincvs, real cvs and the
online slashdot thingy.

Hopefully it will make sense and wont contain too many
outright lies :)

HTH


David

--- Buggs <bug...@sp...> wrote:
> Hoi,
> 
> Anybody uses CVS from windows
> and could write a short text which
> explains howto checkout and update
> the lilproxy repository ?
> Ahh, that would be great :)
> 
> Uuh and I added some docu here
> https://sourceforge.net/docman/?group_id=28612
> http://sourceforge.net/docman/?group_id=28612
> and will continue the next weeks.
> 
> 
> Buggs
> 
> _______________________________________________
> Lilproxy-project mailing list
> Lil...@li...
>
http://lists.sourceforge.net/lists/listinfo/lilproxy-project


=====
"Artificial Intelligence is no match for human stupitity!"


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/

[Lilproxy-project] WinCVS Docu ?

[Buggs <bug...@sp...>]

Hoi,

Anybody uses CVS from windows
and could write a short text which
explains howto checkout and update
the lilproxy repository ?
Ahh, that would be great :)

Uuh and I added some docu here
https://sourceforge.net/docman/?group_id=28612
http://sourceforge.net/docman/?group_id=28612
and will continue the next weeks.


Buggs

[Lilproxy-project] lilproxy patch Jul 4 2001

[Buggs <bug...@sp...>]

Hoi,

this patch adds logging features and HTML error messages.
We now explicitily require perl >= version 5.6.0.

You can get the new version via cvs update.

TODO:
- switch -d to enable Daemon mode (and deamon code of course)
- fork() after ->accept to avoid queuing of reqest
   see: netstat -na | grep tcp
- cooler HTML error messages ?
- more logging options


BTW, to start lilproxy with logging and custom port enter
lilproxy -p 3131 -l


Have fun,
Buggs


--- co/lilproxy/lilproxy	Wed Jul  4 00:10:22 2001
+++ wrk/lilproxy/lilproxy	Wed Jul  4 00:15:38 2001
@@ -9,6 +9,10 @@
 # perl -h
 #
 
+require v5.6.0;
+#
+# We want perl 5.6.0 or higher.
+#
 
 use HTTP::Daemon;
 use LWP::UserAgent;
@@ -29,13 +33,35 @@
 # were hard to debug.
 #
 
+use diagnostics;
+#
+# More verbosity on errors.
+#
+
+#
+# SIGNALS
+#
+
+$SIG{PIPE} = sub { print "\ngot SIGPIPE: $!\n";};
+#
+# If browser disconnects suddenly.
+#
+
+#
+# OPTIONS
+#
 
 our( %optctl, $VERSION );
 # Global variables
 
 $VERSION = 0.2;
 
-my $result = GetOptions( \%optctl => "Port=i", "help", "version" );
+my $result = GetOptions(
+						\%optctl => "Port=i",
+						"help",
+						"version",
+						"logging"
+						);
 #
 # Get command line options
 # a "," is the same as "=>"
@@ -80,7 +106,8 @@
 
 my $proxy = HTTP::Daemon->new( LocalPort => $PORT );
 #
-# Create a new HTTP::Daemon object and store a reference to it in $proxy
+# Create a new HTTP::Daemon object and
+# store a reference to it in $proxy.
 #
 
 die "@_" unless defined $proxy;
@@ -100,7 +127,8 @@
 
 my $ua = LWP::UserAgent->new;
 #
-# Create a new LWP::UserAgent object and store a reference to it in $ua
+# Create a new LWP::UserAgent object and
+# store a reference to it in $ua
 #
 
 $ua->agent("lilproxy/$VERSION");
@@ -109,12 +137,24 @@
 # You have already seen this when we create objects ( ...->new() ).
 #
 
+$ua->timeout(15);
+#
+# Default timeout from 180 to 15 seconds.
+#
+
+
+#
+# MAIN LOOP
+#
+
 while (my $conn = $proxy->accept)
 #
 # See perldoc -f while.
-# Note that the my() will make $conn lexicaly scoped to the while() block.
+# Note that the my() will make $conn lexicaly scoped
+# to the while() block.
 #
-# The call to accept() will block ( "sleep" ) until it someone connects.
+# The call to accept() will block ( "sleep" )
+# until someone connects.
 # HTTP::Daemon::ClientConn object is returned.
 # XXX not really happy with the explanation of accept() and connection.
 # Maybe we should make another small programm which explains sockets?
@@ -130,8 +170,10 @@
    	while (my $request = $conn->get_request)
 	#
 	# While the browser issues requests
-	# on this connections and does not close() the connection we loop.
-	# get_request() returns a request object containing the parsed headers.
+	# on this connections and does not close()
+	# the connection we loop.
+	# get_request() returns a request object
+	# containing the parsed headers.
 	# A reference to this object is stored in $request.
 	#
 	{
@@ -139,18 +181,49 @@
 		#
 		# We pass the request object ( actually a reference to it )
 		# to our UserAgent object's simple request method.
-		# Not much work here because the objects returned by get_request()
-		# and the objects simple_request() needs are compatible :-)
-		# The simple_request() will then fetch the requested HTML document
+		# Not much work here because the objects
+		# returned by get_request() and the objects
+		# simple_request() needs are compatible :-)
+		# The simple_request() will then fetch
+		# the requested HTML document
 		# or image or stuff. We get a response object back
 		# referenced by $response.
 		#
-		$conn->send_response($response);
+		
+		if($response->is_success or $response->is_redirect)
+		{
+			$conn->send_response($response) || print "send_response: $!\n";
+			#
+			# We pass the response object
+			# ( like always a reference actually )
+			# to the send_response method of the conn object.
+			# This sends the HTML doc or whatever
+			# back to the browser.
+			#
+			
+			log_headers($request,$response) if($optctl{logging});
+			#
+			# Log response headers.
+			#
+		}
+		else
 		#
-		# We pass the response object ( like always a reference actually )
-		# to the send_response method of the conn object.
-		# This sends the HTML doc or whatever back to the browser.
+		# Error Handling
 		#
+		{
+			my $err_response = generate_err($response);
+			#
+			# We generate a new HTTP::Response object
+			# containing our fancy error message.
+			#
+			
+			$conn->send_response($err_response);
+			#
+			# Send response back to browser.
+			#
+			
+			log_headers($request,$err_response) if($optctl{logging});
+		}
 	}
 	$conn->close;
 	#
@@ -158,3 +231,58 @@
 	# And start again with waiting for connections.
 	#
 }
+
+
+sub log_headers
+###############
+#
+# Shall log / display the headers of the traffic.
+#
+{
+	my ($request,$response) = @_;
+	# Get arguements.
+	
+	# we just print the headers
+	print	"=" x 20,"\n",
+			"URL: ",
+			"http://", $request->uri->netloc,$request->uri->path,"\n",
+			"=" x 20,
+			"\n--------------->\n",
+			$request->headers->as_string,
+			"\n<---------------\n",
+			$response->headers->as_string,"\n\n";
+}
+
+sub generate_err
+################
+#
+# Generate a HTML-formatted error message HTTP::Response object
+#
+{
+	my $response = shift;
+	my ($status_line, $code, $message) = (
+										$response->status_line,
+										$response->code,
+										$response->message
+										);
+	chomp($status_line, $code, $message);
+	my $err_mesg = <<"EOF";
+
+<html>
+<body bgcolor="#AA0000" text="darkGray" link="darkMagenta" vlink="black">
+<h1 align="center">
+$status_line
+</h1>
+</body>
+</html>
+
+
+EOF
+;
+
+	$err_mesg =~ s/\n/\015\012/g;
+	my $err_response = HTTP::Response->new( $code , $message );
+	$err_response->content($err_mesg);
+	return $err_response;
+}
+

[Lilproxy-project] Geocrawler down ?

[Smeh L. <gro...@ya...>]

Typical it has been down everytime I tried to access it in the past =
fortnight I post about it and bingo I get in.

I read the Getopt::Long docs and Port=3Di is correct. However port 8008 =
is always the port. If anyone can think of somewhere I can look to fix =
this.

[Lilproxy-project] Distributing lilproxy

[Smeh L. <gro...@ya...>]

I managed to get hold of lilproxy 0.2 and got it to work with some =
debugging.
There has to be a better way than CVS for distribution.=20
I think FTP would be much better.

Also the geocities archive has fallen over for a long time now, like two =
weeks and says it will be back in fifteen minutes.

My last point of business is the port option, it does not work for me. I =
tried the 'help' and it worked fine.
but Port=3D80 does not work. The line below is correct or should =
Port=3Di, read Port=3D$i ?

my $result =3D GetOptions( \%optctl =3D> "Port=3Di", "help", "version" =
);

Re: [Lilproxy-project] Looking to the future. and Perl for Windows

[Buggs <bug...@sp...>]

@Montag, 25. Juni 2001 23:07 David Irvine:
> I guess you can go in either two directions,
> a)
> Store the binary data as blob (Binary Large OBjects) inside the database
> which is fine except when you start to get a lot of big files your database
> grows and becomes slower.

ya that's the problem.
I'd estimate that most traffic is stuff you'd put in a blob. 

> B)
> Store a path to the binary files in the database.

And that causes problems too.

Buggs

Re: [Lilproxy-project] Looking to the future. and Perl for Windows

[David I. <co...@ya...>]

----- Original Message -----
From: Buggs <bug...@sp...>
To: <Lil...@li...>
Cc: David Irvine <co...@ya...>
Sent: Monday, June 25, 2001 8:30 PM
Subject: Re: [Lilproxy-project] Looking to the future. and Perl for Windows


> @Montag, 25. Juni 2001 16:43 David Irvine:
>
> > Anyway in the future I would be looking to develop a small gui front
end,
> > even if it just executes lil-proxy with the specified command line args,
> > (The preferred way) something similar to what i think win32 users will
see
> > if they start or stop a service, they get a small dialog box up from
> > control panel. Just a simple introduction to a widget set and how it can
be
> > used under perl and that sort of thing.
>
> Do you think of Tk or something more win32 specific?
>
> > And secondly some sort of DBI gadget to store details of the sites
visited
> > etc. and perhaps if we are really good at databases and gui's we could
make
> > a site statistics screen.
>
> I'd like to have the cache thingies work as modules.
> And I think that our first cache module should use a DB.
> But there is a a issue about binary data and DB's ( images, flash ... ).
>
I guess you can go in either two directions,
a)
Store the binary data as blob (Binary Large OBjects) inside the database
which is fine except when you start to get a lot of big files your database
grows and becomes slower.

B)
Store a path to the binary files in the database.



> > Also, i'm now away from home for a while, and no longer have access to
my
> > *nix boxes, although i do have linux on my laptop, but no net access
yet.
> > So, i'm looking for a perl suite for windows, I had a look at
activestates
> > perl, but it appears to need interdev, which I do not have. (to my
> > knowledge.)  Are there any other good suites, and or packages I should
> > have?
>
> Activestate's Perl distribution should install,
> you may need a newer msi.
>
> There is also
> http://www.indigostar.com
>
> Cygwin
> http://www.cygwin.com
>
> and you could also compile from sources.
>
>
> Buggs
>
> _______________________________________________
> Lilproxy-project mailing list
> Lil...@li...
> http://lists.sourceforge.net/lists/listinfo/lilproxy-project

Re: [Lilproxy-project] Looking to the future. and Perl for Windows

[David I. <co...@ya...>]

> @Montag, 25. Juni 2001 16:43 David Irvine:
>
> > Anyway in the future I would be looking to develop a small gui front
end,
> > even if it just executes lil-proxy with the specified command line args,
> > (The preferred way) something similar to what i think win32 users will
see
> > if they start or stop a service, they get a small dialog box up from
> > control panel. Just a simple introduction to a widget set and how it can
be
> > used under perl and that sort of thing.
>
> Do you think of Tk or something more win32 specific?

Preferably something platform independant, since afaik perl is by default
platform independant.
>
> > And secondly some sort of DBI gadget to store details of the sites
visited
> > etc. and perhaps if we are really good at databases and gui's we could
make
> > a site statistics screen.
>
> I'd like to have the cache thingies work as modules.
> And I think that our first cache module should use a DB.
> But there is a a issue about binary data and DB's ( images, flash ... ).
>
> > Also, i'm now away from home for a while, and no longer have access to
my
> > *nix boxes, although i do have linux on my laptop, but no net access
yet.
> > So, i'm looking for a perl suite for windows, I had a look at
activestates
> > perl, but it appears to need interdev, which I do not have. (to my
> > knowledge.)  Are there any other good suites, and or packages I should
> > have?
>
> Activestate's Perl distribution should install,
> you may need a newer msi.
>
> There is also
> http://www.indigostar.com
>
> Cygwin
> http://www.cygwin.com
>
> and you could also compile from sources.
>
>
> Buggs

Re: [Lilproxy-project] Looking to the future. and Perl for Windows

[Buggs <bug...@sp...>]

@Montag, 25. Juni 2001 16:43 David Irvine:

> Anyway in the future I would be looking to develop a small gui front end,
> even if it just executes lil-proxy with the specified command line args,
> (The preferred way) something similar to what i think win32 users will see
> if they start or stop a service, they get a small dialog box up from
> control panel. Just a simple introduction to a widget set and how it can be
> used under perl and that sort of thing.

Do you think of Tk or something more win32 specific?

> And secondly some sort of DBI gadget to store details of the sites visited
> etc. and perhaps if we are really good at databases and gui's we could make
> a site statistics screen.

I'd like to have the cache thingies work as modules.
And I think that our first cache module should use a DB.
But there is a a issue about binary data and DB's ( images, flash ... ). 

> Also, i'm now away from home for a while, and no longer have access to my
> *nix boxes, although i do have linux on my laptop, but no net access yet.
> So, i'm looking for a perl suite for windows, I had a look at activestates
> perl, but it appears to need interdev, which I do not have. (to my
> knowledge.)  Are there any other good suites, and or packages I should
> have?

Activestate's Perl distribution should install,
you may need a newer msi.

There is also
http://www.indigostar.com

Cygwin
http://www.cygwin.com

and you could also compile from sources.


Buggs

Re: [Lilproxy-project] Getting started

[Buggs <bug...@sp...>]

@Montag, 25. Juni 2001 02:29 David Irvine:

> *Unless of course anybody wants to write a java cvs client :)


There is jcvs and probably some more ( JBuilder has one integrated )
http://www.jcvs.org/

Have fun,
Buggs

[Lilproxy-project] Looking to the future. and Perl for Windows

[David I. <co...@ya...>]

I was having a small ponder on what we should be looking to do in the future
with lil-proxy to bring new functions and things to learn, and also what we
would want to get out of this as developers, personally as a developer I
would be looking to learn perl to the state I could use it to develop
applications that clients ask me for. In general, and I think this is pretty
much the same all round, the application would have some sort of database in
it if not completely database driven, and will at some point have some sort
of gui, I'm not a big fan of point and drool interfaces myself, but
unfortunatly clients are.

So perhaps in the future, once we are all familiar with the tools we will be
using to create lil-proxy, such as cvs and a an editor etc.  And also perl
itself, since it is by no way a standard language, and has a lot of
brilliant features that take a bit of getting used to, especially if you
come from a very rigid or strongly typed language.

Anyway in the future I would be looking to develop a small gui front end,
even if it just executes lil-proxy with the specified command line args,
(The preferred way) something similar to what i think win32 users will see
if they start or stop a service, they get a small dialog box up from control
panel. Just a simple introduction to a widget set and how it can be used
under perl and that sort of thing.

And secondly some sort of DBI gadget to store details of the sites visited
etc. and perhaps if we are really good at databases and gui's we could make
a site statistics screen.

Also, i'm now away from home for a while, and no longer have access to my
*nix boxes, although i do have linux on my laptop, but no net access yet.
So, i'm looking for a perl suite for windows, I had a look at activestates
perl, but it appears to need interdev, which I do not have. (to my
knowledge.)  Are there any other good suites, and or packages I should have?

Anyway just a few thoughts, on where I would like to see Lil-proxy going in
the future.  Anybody else care to share some ideas?


Thanks

David

Re: [Lilproxy-project] Getting started

[Kevin G. <ce...@ya...>]

I say we use the cvs repository at sourceforge, since
that repository is browser accessible, and can also be
accessed from just about anywhere else with a cvs
client.  Somewhere, if needed, we can post a simple
cvs tutorial to assist those who need help with using cvs.

__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail
http://personal.mail.yahoo.com/

Re: [Lilproxy-project] Getting started

[David I. <co...@ya...>]

Hi everybody,

I think it would be a good idea to have the files available via, either
http, or FTP as well as cvs, as it makes things very easy when you find
yourself using lots of different computers.

Cheers

D

*Unless of course anybody wants to write a java cvs client :)


----- Original Message -----
From: Buggs <bug...@sp...>
To: <Lil...@li...>
Cc: Smeh Larat <gro...@ya...>
Sent: Sunday, June 24, 2001 9:17 PM
Subject: Re: [Lilproxy-project] Getting started


> @Samstag, 23. Juni 2001 01:05 Smeh Larat:
> > How about probs like being unable to get Lil Proxy?
>
> Ya, I'd say that was one of them.
>
> If you have a CVS client, like cvs and WinCVS,
> you can follow the instructions these sites
> http://sourceforge.net/cvs/?group_id=28612
> https://sourceforge.net/cvs/?group_id=28612
>
> You could also use CVS via a web interface
> http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/lilproxy/
>
> You should also try to login into the sourceforge shell server
> ssh -l SFID lilproxy.sourceforge.net
>
> A shell is the command line terminal like interface to a UNIX system.
>
> We will work with CVS, but I could also publish the files
> on our project homepage if this is desired.
> Is this demanded?
>
> Does that help?
>
> Buggs
>
> _______________________________________________
> Lilproxy-project mailing list
> Lil...@li...
> http://lists.sourceforge.net/lists/listinfo/lilproxy-project

Re: [Lilproxy-project] Getting started

[Buggs <bug...@sp...>]

@Samstag, 23. Juni 2001 01:05 Smeh Larat:
> How about probs like being unable to get Lil Proxy?

Ya, I'd say that was one of them.

If you have a CVS client, like cvs and WinCVS,
you can follow the instructions these sites
http://sourceforge.net/cvs/?group_id=28612
https://sourceforge.net/cvs/?group_id=28612

You could also use CVS via a web interface
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/lilproxy/

You should also try to login into the sourceforge shell server
ssh -l SFID lilproxy.sourceforge.net

A shell is the command line terminal like interface to a UNIX system.

We will work with CVS, but I could also publish the files
on our project homepage if this is desired.
Is this demanded?

Does that help?

Buggs

Re: [Lilproxy-project] Getting started

[Smeh L. <gro...@ya...>]

How about probs like being unable to get Lil Proxy?
----- Original Message -----
From: "Buggs" <bug...@sp...>
To: "Kevin Gryczan" <ce...@ya...>
Cc: <Lil...@li...>
Sent: Wednesday, June 20, 2001 5:29 AM
Subject: Re: [Lilproxy-project] Getting started


> @Sonntag, 17. Juni 2001 02:58 Kevin Gryczan:
> > It wouldn't hurt to go over everything.  I'm new to
> > just about everything we are working on here with
> > lilproxy.  I just started learning Perl last month,
> > and in what little spare time I had, I just was able
> > to cover the basics.
>
> Uuh, I hoped we could get a little more
> detailed than "everything". LOL
>
> I will provide a "Getting Started" paper,
> covering "everything", but this will cost
> a bunch of time and so I hoped I
> could at least answer the most
> pressuring questions now.
>
> I expect to finish the "Getting Started" paper in about two weeks.
> Specific questions will also help the quality of that paper
> ( maybe it even gets helpful ;) ).
>
> Problems that really need solving now are
> when you still can't run lilproxy ( because of OS / CVS / perl ports
... ).
>
> Have fun,
> Buggs
>
> _______________________________________________
> Lilproxy-project mailing list
> Lil...@li...
> http://lists.sourceforge.net/lists/listinfo/lilproxy-project

Fwd: Re: [Lilproxy-project] simple daemonology

[Dominik B. <ki...@we...>]

Seems like Buggs has only replied to me instead to the list... 
Greets Dominik 

----- Forwarded message from Buggs <bug...@sp...> -----
Date: Tue, 19 Jun 2001 21:46:48 +0200
From: Buggs <bug...@sp...>
Reply-To: Buggs <bug...@sp...>
Subject: Re: [Lilproxy-project] simple daemonology
To: Dominik Berner <ki...@we...>

@Dienstag, 19. Juni 2001 16:20 Dominik Berner:

> shouldn't we redirect the STD's into 'real' .log files instead to
> /dev/null?

Good point.
We should at least have a command line switch for
redirecting STDERR to a logfile.

Anybody read about daemon mode for Win32?

Anybody uses / tests an other OS then Linux / Win32?
*BSD, UNIX, OS2, Plan9, Mac ... anybody?


The daemon mode specific thingies need to be in
a sub, so we can activate it on demand ( command line switch ).
Something like

sub daemonize
{
	print "Starting Lilproxy Daemon...\n";
	fork() && exit();
}


Have fun,
Buggs

----- End forwarded message -----



-- 
If you only have a hammer, you tend to see every problem as a nail.

Re: [Lilproxy-project] Getting started

[Kevin G. <ce...@ya...>]

When I said everything, I was referring to all of the
items that you listed in your previous post to the
mailing list on things to cover.

I am able to run lilproxy without any problems through
Cygwin, so when I develop my code, that is the
platform I will be using.  I feel that there shouldn't
be any other problems with my code running on other platforms.

__________________________________________________
Do You Yahoo!?
Spot the hottest trends in music, movies, and more.
http://buzz.yahoo.com/

Re: [Lilproxy-project] Getting started

[Buggs <bug...@sp...>]

@Sonntag, 17. Juni 2001 02:58 Kevin Gryczan:
> It wouldn't hurt to go over everything.  I'm new to
> just about everything we are working on here with
> lilproxy.  I just started learning Perl last month,
> and in what little spare time I had, I just was able
> to cover the basics.

Uuh, I hoped we could get a little more
detailed than "everything". LOL

I will provide a "Getting Started" paper,
covering "everything", but this will cost
a bunch of time and so I hoped I
could at least answer the most
pressuring questions now.

I expect to finish the "Getting Started" paper in about two weeks.
Specific questions will also help the quality of that paper
( maybe it even gets helpful ;) ).

Problems that really need solving now are
when you still can't run lilproxy ( because of OS / CVS / perl ports ... ).

Have fun,
Buggs

[Lilproxy-project] simple daemonology

[Dominik B. <ki...@we...>]

Hi,

I've experimentated a wee bit with fork() and produced this

fork() && exit(); 
creating the child and exit afterwards, however because I haven't much sparetime at the moment I've done nothing to redirect STDIN/OUT/ERR.
BTW: shouldn't we redirect the STD's into 'real' .log files instead to /dev/null?

Greets Dominik

//Patch//

--- lilproxy.pl.origThu Jun 14 15:01:46 2001
+++ lilproxy.plTue Jun 19 16:10:19 2001

@@ -109,6 +110,9 @@
 # You have already seen this when we create objects ( ...->new() ).

+print "Entering Daemon-Mode...\n";
+fork() && exit();
+
 while (my $conn = $proxy->accept)
 #
 # See perldoc -f while.

//end patch//
-- 
If you only have a hammer, you tend to see every problem as a nail.

Re: [Lilproxy-project] Getting started

[Kevin G. <ce...@ya...>]

It wouldn't hurt to go over everything.  I'm new to
just about everything we are working on here with
lilproxy.  I just started learning Perl last month,
and in what little spare time I had, I just was able
to cover the basics.

__________________________________________________
Do You Yahoo!?
Spot the hottest trends in music, movies, and more.
http://buzz.yahoo.com/