jim fisher on 20 Jun 2008 11:03:22 -0700


[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] plug Digest, Vol 43, Issue 40


On 6/20/08, plug-request@lists.phillylinux.org
<plug-request@lists.phillylinux.org> wrote:
> Send plug mailing list submissions to
> 	plug@lists.phillylinux.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://lists.netisland.net/mailman/listinfo/plug
> or, via email, send a message with subject or body 'help' to
> 	plug-request@lists.phillylinux.org
>
> You can reach the person managing the list at
> 	plug-owner@lists.phillylinux.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of plug digest..."
>
>
> Today's Topics:
>
>    1. Re: Apache 2 configuration on Debian (JP Vossen)
>    2. Philly Wireless Rev. 2....? (Brian Vagnoni)
>    3. Re: Apache 2 configuration on Debian (James Barrett)
>    4. Re: Apache 2 configuration on Debian (Michael Lazin)
>    5. Load killer ? (Glenn Kelley)
>    6. Re: Load killer ? (David A. Harding)
>    7. Re: Load killer ? (Stephen Gran)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Thu, 19 Jun 2008 16:30:13 -0400
> From: JP Vossen <jp@jpsdomain.org>
> Subject: Re: [PLUG] Apache 2 configuration on Debian
> To: plug@lists.phillylinux.org
> Message-ID: <485AC1D5.5080701@jpsdomain.org>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> From: "Michael Lazin" <microlaser@gmail.com>
> Subject: [PLUG] Apache 2 configuration on Debian
>
>> I was given a server in my company's datacenter to use for testing
>> purposes. I have imaged it with a minimal debian etch and installed
>> apache 2. I created user accounts for everyone in my department, and
>> installed apache2. I am interested in giving everyone webspace in
>> their home directory. I have used httpd.conf before and simply
>> uncommented a line to get this done, but this apache 2 install only
>> has an apache2.conf and an empty httpd.conf. Anyone know of any good
>> resources for configuring apache2 on debian? apache2.conf looks like
>> the correct configuration file but I don't see a line that I can
>> uncomment to get this done. I believe I have to add the necessary
>> line. Anyone with experience with apache2 on debian able to give me
>> some pointers? Thanks.
>
> I'm not an expert, but Debian/Ubuntu use the
> /etc/apache2/sites-available/ and sites-enabled/ directories to control
> a lot of things like that.  I'm pretty sure you can just create a file
> in sites-available/ and then symlink it in sites-enabled/ to activate it.
>
> I like the O'Reilly _Apache Cookbook_ (very short for a cookbook, at <
> 230 pages), though you will have to translate the solutions into
> Debian-ese a bit.  The _Linux Cookbook_ also has a bit on this,
> including "22.8 Giving Users Individual Web Directories" though the
> Apache book "5.4 Giving Users Their Own URL" has more discussion.
>
> One of the possible solutions both books cover is just to add "UserDir
> public_html" to the config file.  Then create 'public_html/' dirs in
> each user's $HOME and they can put HTML in there.  Which config file to
> add that to is a good question.  If you put it in apache2.conf, your
> changes might get nuked on upgrades.  (Actually dpkg-reconfigure will
> ask you about them, but...)
>
> I'd probably try something creating
> /etc/apache2/sites-available/user_dirs.conf with that entry, then
> symlinking that into sites-available.
>
> HTH, and good luck,
> JP
> ----------------------------|:::======|-------------------------------
> JP Vossen, CISSP            |:::======|        jp{at}jpsdomain{dot}org
> My Account, My Opinions     |=========|      http://www.jpsdomain.org/
> ----------------------------|=========|-------------------------------
> "Microsoft Tax" = the additional hardware & yearly fees for the add-on
> software required to protect Windows from its own poorly designed and
> implemented self, while the overhead incidentally flattens Moore's Law.
>
>
> ------------------------------
>
> Message: 2
> Date: Thu, 19 Jun 2008 18:25:20 -0400
> From: "Brian Vagnoni" <bvagnoni@v-system.net>
> Subject: [PLUG] Philly Wireless Rev. 2....?
> To: "Philadelphia Linux User's Group Discussion List"
> 	<plug@lists.phillylinux.org>
> Message-ID: <20080619222520.c4974393@macserver.v-system.net>
> Content-Type: text/plain;	charset="us-ascii"
>
> http://www.wirelessphiladelphia.org/blog_detail.cfm/blog/72
>
> IT"S ALIVE!!!!! again?
>
>
>
>
> --------------------------------------------------
> Brian Vagnoni
> PGP Digital Fingerprint
> F076 6EEE 06E5 BEEF EBBD  BD36 F29E 850D FC32 3955
> --------------------------------------------------
>
>
>
> ------------------------------
>
> Message: 3
> Date: Thu, 19 Jun 2008 18:56:47 -0400
> From: "James Barrett" <jadoba@jadoba.net>
> Subject: Re: [PLUG] Apache 2 configuration on Debian
> To: "Philadelphia Linux User's Group Discussion List"
> 	<plug@lists.phillylinux.org>
> Message-ID:
> 	<dde847cf0806191556y6880ff42w4b0a637fe5cd84f6@mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> On Thu, Jun 19, 2008 at 4:30 PM, JP Vossen <jp@jpsdomain.org> wrote:
>> From: "Michael Lazin" <microlaser@gmail.com>
>> Subject: [PLUG] Apache 2 configuration on Debian
>>
>>> I was given a server in my company's datacenter to use for testing
>>> purposes. I have imaged it with a minimal debian etch and installed
>>> apache 2. I created user accounts for everyone in my department, and
>>> installed apache2. I am interested in giving everyone webspace in
>>> their home directory. I have used httpd.conf before and simply
>>> uncommented a line to get this done, but this apache 2 install only
>>> has an apache2.conf and an empty httpd.conf. Anyone know of any good
>>> resources for configuring apache2 on debian? apache2.conf looks like
>>> the correct configuration file but I don't see a line that I can
>>> uncomment to get this done. I believe I have to add the necessary
>>> line. Anyone with experience with apache2 on debian able to give me
>>> some pointers? Thanks.
>>
>> I'm not an expert, but Debian/Ubuntu use the
>> /etc/apache2/sites-available/ and sites-enabled/ directories to control
>> a lot of things like that.  I'm pretty sure you can just create a file
>> in sites-available/ and then symlink it in sites-enabled/ to activate it.
>>
>> I like the O'Reilly _Apache Cookbook_ (very short for a cookbook, at <
>> 230 pages), though you will have to translate the solutions into
>> Debian-ese a bit.  The _Linux Cookbook_ also has a bit on this,
>> including "22.8 Giving Users Individual Web Directories" though the
>> Apache book "5.4 Giving Users Their Own URL" has more discussion.
>>
>> One of the possible solutions both books cover is just to add "UserDir
>> public_html" to the config file.  Then create 'public_html/' dirs in
>> each user's $HOME and they can put HTML in there.  Which config file to
>> add that to is a good question.  If you put it in apache2.conf, your
>> changes might get nuked on upgrades.  (Actually dpkg-reconfigure will
>> ask you about them, but...)
>>
>> I'd probably try something creating
>> /etc/apache2/sites-available/user_dirs.conf with that entry, then
>> symlinking that into sites-available.
>>
>> HTH, and good luck,
>
> You probably want to put configurations anywhere you please and then
> symlink to them from /etc/apache2/conf.d/
>
> I use the sites-available and sites-enabled way more for virtualhost
> and site-specific configurations.  Since you are working 'in-house' it
> seems like you probably will not be needing virtualhosts, so conf.d is
> probably what you want.
>
> --
> James Barrett
>
>
> ------------------------------
>
> Message: 4
> Date: Thu, 19 Jun 2008 22:05:28 -0400
> From: "Michael Lazin" <microlaser@gmail.com>
> Subject: Re: [PLUG] Apache 2 configuration on Debian
> To: "Philadelphia Linux User's Group Discussion List"
> 	<plug@lists.phillylinux.org>
> Message-ID:
> 	<6bb38bb80806191905n6acce46cked3836179151b837@mail.gmail.com>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Thanks all.  Got it working.  I am not used to Apache2.  I am learning.
> Part of the fun of this project is the learning experience.  We have CentOS
> images with plesk available at work, but I went with the minimal debian
> because I thought I would learn more, and I like the Debian way, I use
> Kubuntu at home.  Thanks.
>
> On Thu, Jun 19, 2008 at 6:56 PM, James Barrett <jadoba@jadoba.net> wrote:
>
>> On Thu, Jun 19, 2008 at 4:30 PM, JP Vossen <jp@jpsdomain.org> wrote:
>> > From: "Michael Lazin" <microlaser@gmail.com>
>> > Subject: [PLUG] Apache 2 configuration on Debian
>> >
>> >> I was given a server in my company's datacenter to use for testing
>> >> purposes. I have imaged it with a minimal debian etch and installed
>> >> apache 2. I created user accounts for everyone in my department, and
>> >> installed apache2. I am interested in giving everyone webspace in
>> >> their home directory. I have used httpd.conf before and simply
>> >> uncommented a line to get this done, but this apache 2 install only
>> >> has an apache2.conf and an empty httpd.conf. Anyone know of any good
>> >> resources for configuring apache2 on debian? apache2.conf looks like
>> >> the correct configuration file but I don't see a line that I can
>> >> uncomment to get this done. I believe I have to add the necessary
>> >> line. Anyone with experience with apache2 on debian able to give me
>> >> some pointers? Thanks.
>> >
>> > I'm not an expert, but Debian/Ubuntu use the
>> > /etc/apache2/sites-available/ and sites-enabled/ directories to control
>> > a lot of things like that.  I'm pretty sure you can just create a file
>> > in sites-available/ and then symlink it in sites-enabled/ to activate
>> > it.
>> >
>> > I like the O'Reilly _Apache Cookbook_ (very short for a cookbook, at <
>> > 230 pages), though you will have to translate the solutions into
>> > Debian-ese a bit.  The _Linux Cookbook_ also has a bit on this,
>> > including "22.8 Giving Users Individual Web Directories" though the
>> > Apache book "5.4 Giving Users Their Own URL" has more discussion.
>> >
>> > One of the possible solutions both books cover is just to add "UserDir
>> > public_html" to the config file.  Then create 'public_html/' dirs in
>> > each user's $HOME and they can put HTML in there.  Which config file to
>> > add that to is a good question.  If you put it in apache2.conf, your
>> > changes might get nuked on upgrades.  (Actually dpkg-reconfigure will
>> > ask you about them, but...)
>> >
>> > I'd probably try something creating
>> > /etc/apache2/sites-available/user_dirs.conf with that entry, then
>> > symlinking that into sites-available.
>> >
>> > HTH, and good luck,
>>
>> You probably want to put configurations anywhere you please and then
>> symlink to them from /etc/apache2/conf.d/
>>
>> I use the sites-available and sites-enabled way more for virtualhost
>> and site-specific configurations.  Since you are working 'in-house' it
>> seems like you probably will not be needing virtualhosts, so conf.d is
>> probably what you want.
>>
>> --
>> James Barrett
>> ___________________________________________________________________________
>> Philadelphia Linux Users Group         --
>> http://www.phillylinux.org
>> Announcements -
>> http://lists.phillylinux.org/mailman/listinfo/plug-announce
>> General Discussion  --
>> http://lists.phillylinux.org/mailman/listinfo/plug
>>
>
>
>
> --
> Michael Lazin
> Dell Precision Workstation 380n 3ghz 1 gig RAM dual boot Kubuntu Hardy Heron
> 64 bit and Solaris 10
> Dell Dimension E521 2ghz 512 meg RAM Kubuntu Hardy Heron 64 bit
> Blue & White Mac G3 400mhz 512 meg RAM OSX Tiger
> SGI O2 180mhz 192 meg RAM OpenBSD 4.3
> Everex Stepnote NC-1501 1.5ghz 1 gig RAM Nairbuntu Hardy Heron
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL:
> http://lists.netisland.net/pipermail/plug/attachments/20080619/8bf44d1a/attachment.htm
>
> ------------------------------
>
> Message: 5
> Date: Thu, 19 Jun 2008 23:15:42 -0400
> From: Glenn Kelley <glenn@typo3usa.com>
> Subject: [PLUG] Load killer ?
> To: Philadelphia Linux User's Group Discussion List
> 	<plug@lists.phillylinux.org>
> Message-ID: <7946A339-A88D-4CC2-B4F8-BA07CBB9FB49@typo3usa.com>
> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
>
> Greetings
>
> I am wondering if anyone can help me here...
> Don't know python - but perhaps that would help...
>
> in short we want to measure httpd
>
> when this service goes over say 6 on load
> we want to kill it and restart
>
> #!/usr/bin/perl -w
> #use strict;
> $|++;
> open(LOAD,"/proc/loadavg") || die "couldn't open /proc/loadavg: $!\n";
> my @load=split(/ /,<LOAD>);
> close(LOAD);
> if ($load[0] > 9) {
> `/sbin/service httpd restart`;
> }
>
>
> was my first attempt except of course - that will kill whenever any
> load happens
>
> any suggestions...
>
>
> glenn
>
>
>
> ------------------------------
>
> Message: 6
> Date: Fri, 20 Jun 2008 01:08:29 -0400
> From: "David A. Harding" <dave@dtrt.org>
> Subject: Re: [PLUG] Load killer ?
> To: Philadelphia Linux User's Group Discussion List
> 	<plug@lists.phillylinux.org>
> Message-ID: <20080620050829.GA11414@localhost.localdomain>
> Content-Type: text/plain; charset=us-ascii
>
> On Thu, Jun 19, 2008 at 11:15:42PM -0400, Glenn Kelley wrote:
>> I am wondering if anyone can help me here...
>> [...]
>> when this service goes over say 9 on load we want to kill it
>> and restart
>
> Your program was a good start.  I cleaned it up and made it loop:
>
>   #!/usr/bin/perl -w
>   use strict;
>
>   open(LOAD, "/proc/loadavg") or die "couldn't open /proc/loadavg: $!\n";
>
>   $_ = <LOAD>;
>   s/^(.*?) .*/$1/;
>
>   if ( $_ > 9 ) {
>           print "The Enterprise, NCC-1701D, may not go faster than warp
> 10.\n"
> 	  # (And if a Voyager shuttle goes warp 10, you get one crappy episode.)
>           ##`/sbin/service httpd restart`;
>           }
>
>   sleep 1;  # NB: The kernel won't update the loadavg more than once a
> second
>   exec $0;
>
> You can stop it from looping by pressing control-c.
>
> I suggest that you consider turning off Apache when the load is above 9
> and don't turn it back on until the load drops below 9.
>
> -Dave
> --
> David A. Harding            Website:  http://dtrt.org/
> 1 (609) 997-0765              Email:  dave@dtrt.org
>                         Jabber/XMPP:  dharding@jabber.org
>
>
> ------------------------------
>
> Message: 7
> Date: Fri, 20 Jun 2008 11:19:31 +0100
> From: Stephen Gran <steve@lobefin.net>
> Subject: Re: [PLUG] Load killer ?
> To: plug@lists.phillylinux.org
> Message-ID: <20080620101931.GB27320@www.lobefin.net>
> Content-Type: text/plain; charset="us-ascii"
>
> On Thu, Jun 19, 2008 at 11:15:42PM -0400, Glenn Kelley said:
>> in short we want to measure httpd
>>
>> when this service goes over say 6 on load
>> we want to kill it and restart
>
> Instead of reinventing the wheel, use monit, which was designed for this
> and can do what you want.
> --
>  --------------------------------------------------------------------------
> |  Stephen Gran                  | I've got an IDEA!!  Why don't I STARE   |
> |  steve@lobefin.net             | at you so HARD, you forget your SOCIAL  |
> |  http://www.lobefin.net/~steve | SECURITY NUMBER!!                       |
>  --------------------------------------------------------------------------
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: not available
> Type: application/pgp-signature
> Size: 189 bytes
> Desc: Digital signature
> Url :
> http://lists.netisland.net/pipermail/plug/attachments/20080620/a7a5a3e8/attachment.pgp
>
> ------------------------------
>
> _______________________________________________
> plug mailing list
> plug@lists.phillylinux.org
> http://lists.netisland.net/mailman/listinfo/plug
>
>
> End of plug Digest, Vol 43, Issue 40
> ************************************
>
___________________________________________________________________________
Philadelphia Linux Users Group         --        http://www.phillylinux.org
Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
General Discussion  --   http://lists.phillylinux.org/mailman/listinfo/plug