Bristol and Bath Linux: 2014

Selasa, 30 Desember 2014

Bristol Digest, Vol 583, Issue 2

Senin, 29 Desember 2014

Bristol Digest, Vol 583, Issue 1

Send Bristol mailing list submissions to
bristol@mailman.lug.org.uk

To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.lug.org.uk/mailman/listinfo/bristol
or, via email, send a message with subject or body 'help' to
bristol-request@mailman.lug.org.uk

You can reach the person managing the list at
bristol-owner@mailman.lug.org.uk

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Bristol digest..."

Today's Topics:

1. Re: DyGraph (Pi (Peter Hemmings)
2. Re: OT: SSL / Convergence (Christopher Horler)
3. Re: DyGraph (Pi (Christopher Horler)
4. Re: DyGraph (Pi (Peter Hemmings)

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

Message: 1
Date: Sun, 28 Dec 2014 15:40:40 +0000
From: Peter Hemmings <peter@hemmings.eclipse.co.uk>
To: Bristol and Bath Linux User Group <bristol@mailman.lug.org.uk>
Subject: Re: [bristol] DyGraph (Pi
Message-ID: <54A02478.2090608@hemmings.eclipse.co.uk>
Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"

On 28/12/14 11:07, Peter Hemmings wrote:
> On 28/12/14 09:17, Chris wrote:
>> I think you may be over complicating it... did you read this: ?
>
> !
>
> I have now.
>
>>
>> http://httpd.apache.org/docs/2.2/howto/public_html.html
>>
>> Sub heading per-user web directories
>>
>> Or put the file under /var/www

(posting from pi)

I have loaded the "mod_userdir" OK but the pi apache2 does not seem to
have the same file structure.

I am trying to find where to remove the # on "#Include
conf/extra/httpd-userdir.conf" as per the first part of above link and
it is not in my apache2.conf.

I have Apache2 version 2.2.22 and am not sure if this is different or
the pi version has different configuration.

I do have a "userdir.conf" in "/etc/apache2/mods-enabled" which seems
to have relevant configuration, so maybe it should work!

Attached userdir.conf and apache2.conf for info just ic case there is
anything obvious!

Regards
--
Peter H
-------------- next part --------------
pi@raspberry /etc/apache2/mods-enabled $ cat userdir.conf
<IfModule mod_userdir.c>
UserDir public_html
UserDir disabled root

<Directory /home/*/public_html>
AllowOverride FileInfo AuthConfig Limit Indexes
Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
<Limit GET POST OPTIONS>
Order allow,deny
Allow from all
</Limit>
<LimitExcept GET POST OPTIONS>
Order deny,allow
Deny from all
</LimitExcept>
</Directory>
</IfModule>

pi@raspberry /etc/apache2/mods-enabled $

-------------- next part --------------
pi@raspberry /etc/apache2 $ cat apache2.conf
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See http://httpd.apache.org/docs/2.2/ for detailed information about
# the directives and /usr/share/doc/apache2-common/README.Debian.gz about
# Debian specific hints.
#
#
# Summary of how the Apache 2 configuration works in Debian:
# The Apache 2 web server configuration in Debian is quite different to
# upstream's suggested way to configure the web server. This is because Debian's
# default Apache2 installation attempts to make adding and removing modules,
# virtual hosts, and extra configuration directives as flexible as possible, in
# order to make automating the changes and administering the server as easy as
# possible.

# It is split into several files forming the configuration hierarchy outlined
# below, all located in the /etc/apache2/ directory:
#
# /etc/apache2/
# |-- apache2.conf
# | `-- ports.conf
# |-- mods-enabled
# | |-- *.load
# | `-- *.conf
# |-- conf.d
# | `-- *
# `-- sites-enabled
# `-- *
#
#
# * apache2.conf is the main configuration file (this file). It puts the pieces
# together by including all remaining configuration files when starting up the
# web server.
#
# In order to avoid conflicts with backup files, the Include directive is
# adapted to ignore files that:
# - do not begin with a letter or number
# - contain a character that is neither letter nor number nor _-:.
# - contain .dpkg
#
# Yet we strongly suggest that all configuration files either end with a
# .conf or .load suffix in the file name. The next Debian release will
# ignore files not ending with .conf (or .load for mods-enabled).
#
# * ports.conf is always included from the main configuration file. It is
# supposed to determine listening ports for incoming connections, and which
# of these ports are used for name based virtual hosts.
#
# * Configuration files in the mods-enabled/ and sites-enabled/ directories
# contain particular configuration snippets which manage modules or virtual
# host configurations, respectively.
#
# They are activated by symlinking available configuration files from their
# respective *-available/ counterparts. These should be managed by using our
# helpers a2enmod/a2dismod, a2ensite/a2dissite. See
# their respective man pages for detailed information.
#
# * Configuration files in the conf.d directory are either provided by other
# packages or may be added by the local administrator. Local additions
# should start with local- or end with .local.conf to avoid name clashes. All
# files in conf.d are considered (excluding the exceptions noted above) by
# the Apache 2 web server.
#
# * The binary is called apache2. Due to the use of environment variables, in
# the default configuration, apache2 needs to be started/stopped with
# /etc/init.d/apache2 or apache2ctl. Calling /usr/bin/apache2 directly will not
# work with the default configuration.

# Global configuration
#

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation (available
# at <URL:http://httpd.apache.org/docs/2.2/mod/mpm_common.html#lockfile>);
# you will save yourself a lot of trouble.
#
# Do NOT add a slash at the end of the directory path.
#
#ServerRoot "/etc/apache2"

#
# The accept serialization lock file MUST BE STORED ON A LOCAL DISK.
#
LockFile ${APACHE_LOCK_DIR}/accept.lock

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
# This needs to be set in /etc/apache2/envvars
#
PidFile ${APACHE_PID_FILE}

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 5

##
## Server-Pool Size Regulation (MPM specific)
##

# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
# MaxSpareServers: maximum number of server processes which are kept spare
# MaxClients: maximum number of server processes allowed to start
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_prefork_module>
StartServers 5
MinSpareServers 5
MaxSpareServers 10
MaxClients 150
MaxRequestsPerChild 0
</IfModule>

# worker MPM
# StartServers: initial number of server processes to start
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadLimit: ThreadsPerChild can be changed to this maximum value during a
# graceful restart. ThreadLimit can only be changed by stopping
# and starting Apache.
# ThreadsPerChild: constant number of worker threads in each server process
# MaxClients: maximum number of simultaneous client connections
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_worker_module>
StartServers 2
MinSpareThreads 25
MaxSpareThreads 75
ThreadLimit 64
ThreadsPerChild 25
MaxClients 150
MaxRequestsPerChild 0
</IfModule>

# event MPM
# StartServers: initial number of server processes to start
# MinSpareThreads: minimum number of worker threads which are kept spare
# MaxSpareThreads: maximum number of worker threads which are kept spare
# ThreadsPerChild: constant number of worker threads in each server process
# MaxClients: maximum number of simultaneous client connections
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_event_module>
StartServers 2
MinSpareThreads 25
MaxSpareThreads 75
ThreadLimit 64
ThreadsPerChild 25
MaxClients 150
MaxRequestsPerChild 0
</IfModule>

# These need to be set in /etc/apache2/envvars
User ${APACHE_RUN_USER}
Group ${APACHE_RUN_GROUP}

#
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives. See also the AllowOverride
# directive.
#

AccessFileName .htaccess

#
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
#
<Files ~ "^\.ht">
Order allow,deny
Deny from all
Satisfy all
</Files>

#
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
# It is also possible to omit any default MIME type and let the
# client's browser guess an appropriate action instead. Typically the
# browser will decide based on the file's extension then. In cases
# where no good assumption can be made, letting the default MIME type
# unset is suggested instead of forcing the browser to accept
# incorrect metadata.
#
DefaultType None

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog ${APACHE_LOG_DIR}/error.log

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

# Include module configuration:
Include mods-enabled/*.load
Include mods-enabled/*.conf

# Include list of ports to listen on and which to use for name based vhosts
Include ports.conf

#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
# If you are behind a reverse proxy, you might want to change %h into %{X-Forwarded-For}i
#
LogFormat "%v:%p %h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" vhost_combined
LogFormat "%h %l %u %t \"%r\" %>s %O \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %O" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

# Include of directories ignores editors' and dpkg's backup files,
# see the comments above for details.

# Include generic snippets of statements
Include conf.d/

# Include the virtual host configurations:
Include sites-enabled/

ServerName pi.example.com
pi@raspberry /etc/apache2 $

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

Message: 2
Date: Sun, 28 Dec 2014 16:28:01 +0000
From: Christopher Horler <cshorler@googlemail.com>
To: Bristol and Bath Linux User Group <bristol@mailman.lug.org.uk>
Subject: Re: [bristol] OT: SSL / Convergence
Message-ID:
<CAAeT8m9p6-coZ_C3WdBras-vxKsFPgUgK9wtAb8xswR8JzJhtw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On 21 December 2014 at 17:58, Christopher Horler
<cshorler@googlemail.com> wrote:
> On 21 December 2014 at 15:17, Alex Butcher (LUG) <lug@assursys.co.uk> wrote:
>>
>>
>> On 21 December 2014 13:42:45 GMT+00:00, Conor O'Neill <conor_lists@puddle.co.uk> wrote:
>>>On 19/12/14 08:38, Chris wrote:
>>>> Interesting read / software
>>>>
>>>> http://convergence.io/
>>>>
>>>
>>>Very interesting, certainly worth watching their video about it, but be
>>>aware that it is 48 minutes long:
>>>http://www.youtube.com/watch?v=Z7Wl2FW2TcA
>>>
>>>Has anyone else tried using this? I see that its from 2011, but it
>>>doesn't seem to have gained much publicity.
>>
>> I used it for a while, but disabled it when I was getting excessive memory use by Firefox, and I don't think I re-enabled it. I don't think it was Convergence's fault, though.
>>
>
> No, I was reading a related article on security.stackexchange.com - on
> a government's MITM attack on SSL, pointing out the problems with
> trusted root CAs. Convergence strikes me as a better security model,
> although I didn't listen to the talk yet... (I knew it existed
> though!)

I have now tried it... it didn't work (google.com wouldn't load,
opensuse.org only loaded partially - it's probably a mixed SSL / no
SSL content webpage), futher investigation required (wireshark...)

- but I'd hazard a guess that one or more of the notaries don't exist
any longer (I tried to add another to the default configuration
unsuccessfully).

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

Message: 3
Date: Sun, 28 Dec 2014 16:44:24 +0000
From: Christopher Horler <cshorler@googlemail.com>
To: Bristol and Bath Linux User Group <bristol@mailman.lug.org.uk>
Subject: Re: [bristol] DyGraph (Pi
Message-ID:
<CAAeT8m_KmpAK9_Ths7iiWi3oHE6eh=JW90J0Uk-BbfLn5E7dhQ@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8

On 28 December 2014 at 15:40, Peter Hemmings
<peter@hemmings.eclipse.co.uk> wrote:
>
> On 28/12/14 11:07, Peter Hemmings wrote:
>>
>> On 28/12/14 09:17, Chris wrote:
>>>
>>> I think you may be over complicating it... did you read this: ?
>>
>>
>> !
>>
>> I have now.
>>
>>>
>>> http://httpd.apache.org/docs/2.2/howto/public_html.html
>>>
>>> Sub heading per-user web directories
>>>
>>> Or put the file under /var/www
>
>
> (posting from pi)
>
> I have loaded the "mod_userdir" OK but the pi apache2 does not seem to have
> the same file structure.
>
> I am trying to find where to remove the # on "#Include
> conf/extra/httpd-userdir.conf" as per the first part of above link and it is
> not in my apache2.conf.
>
> I have Apache2 version 2.2.22 and am not sure if this is different or the pi
> version has different configuration.
>
> I do have a "userdir.conf" in "/etc/apache2/mods-enabled" which seems to
> have relevant configuration, so maybe it should work!
>
> Attached userdir.conf and apache2.conf for info just ic case there is
> anything obvious!
>

assuming you're the user pi (as per the attachments)

do you have a directory /home/pi/public_html

if you put a file test.html in the above directory - then it should be
accessible under

http://pi-ip-addr/~pi/test.html

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

Message: 4
Date: Sun, 28 Dec 2014 17:14:59 +0000
From: Peter Hemmings <peter@hemmings.eclipse.co.uk>
To: Bristol and Bath Linux User Group <bristol@mailman.lug.org.uk>
Subject: Re: [bristol] DyGraph (Pi
Message-ID: <54A03A93.6000206@hemmings.eclipse.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed

On 28/12/14 16:44, Christopher Horler wrote:
> On 28 December 2014 at 15:40, Peter Hemmings
> <peter@hemmings.eclipse.co.uk> wrote:
>>
>> On 28/12/14 11:07, Peter Hemmings wrote:
>>>
>>> On 28/12/14 09:17, Chris wrote:
>>>>
>>>> I think you may be over complicating it... did you read this: ?
>>>
>>>
>>> !
>>>
>>> I have now.
>>>
>>>>
>>>> http://httpd.apache.org/docs/2.2/howto/public_html.html
>>>>
>>>> Sub heading per-user web directories
>>>>
>>>> Or put the file under /var/www
>>
>>
>> (posting from pi)
>>
>> I have loaded the "mod_userdir" OK but the pi apache2 does not seem to have
>> the same file structure.
>>
>> I am trying to find where to remove the # on "#Include
>> conf/extra/httpd-userdir.conf" as per the first part of above link and it is
>> not in my apache2.conf.
>>
>> I have Apache2 version 2.2.22 and am not sure if this is different or the pi
>> version has different configuration.
>>
>> I do have a "userdir.conf" in "/etc/apache2/mods-enabled" which seems to
>> have relevant configuration, so maybe it should work!
>>
>> Attached userdir.conf and apache2.conf for info just ic case there is
>> anything obvious!
>>
>
> assuming you're the user pi (as per the attachments)

I am that person!

>
> do you have a directory /home/pi/public_html

Yep, I made that and chmodded it as per instructions I found on
"Userdir" page.

>
> if you put a file test.html in the above directory - then it should be
> accessible under

>
> http://pi-ip-addr/~pi/test.html

Will do later

>
> _______________________________________________
> Bristol mailing list
> Bristol@mailman.lug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/bristol
>

--
Peter H

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

_______________________________________________
Bristol mailing list
Bristol@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/bristol

End of Bristol Digest, Vol 583, Issue 1
***************************************

Minggu, 28 Desember 2014

Bristol Digest, Vol 582, Issue 3

Send Bristol mailing list submissions to
bristol@mailman.lug.org.uk

To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.lug.org.uk/mailman/listinfo/bristol
or, via email, send a message with subject or body 'help' to
bristol-request@mailman.lug.org.uk

You can reach the person managing the list at
bristol-owner@mailman.lug.org.uk

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Bristol digest..."

Today's Topics:

1. Re: DyGraph (Pi) (Peter Hemmings)
2. Re: DyGraph (Pi) (Chris)
3. Re: DyGraph (Pi) (Peter Hemmings)
4. Re: DyGraph (Pi (Chris)
5. Re: DyGraph (Pi (Peter Hemmings)

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

Message: 1
Date: Sat, 27 Dec 2014 12:32:53 +0000
From: Peter Hemmings <peter@hemmings.eclipse.co.uk>
To: Bristol and Bath Linux User Group <bristol@mailman.lug.org.uk>
Subject: Re: [bristol] DyGraph (Pi)
Message-ID: <549EA6F5.5030608@hemmings.eclipse.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed

Seasons Greetings to all lurkers and active members.

Update:

Pi continues to work outputting humidity/temperature data into
"temp.log" so the first script and cron job is OK.
As Apache does not accept symlinks I copied data into a static
"temp.log" to test scripts before looking at apache.

I still could not get it to work on the Pi.
I copied data csv file (temp.log), html file "temp.html" (dygraph
script) and dygraph-combined.js from Pi to fc19 laptop and took it to KT
last week and it worked!

The files are in /var/www/html/ on fc19 and in /var/www/ on Raspian Pi.

To keep things simple and try to avoid typos, I deleted files on Pi and
copied them back from fc19 that worked!

Pi comes with two "cut-down" browsers "Epiphany" and "NetSurf".

Checked local IP address and that apache2 was running OK on Pi, but got
nothing on both Browsers (just blank page, no graphs or errors).

As my Pi is now on a larger SD card, I installed "Chromium".

Tried it, and it works!!

So why could this be, is it to do with font characters, I did see an
error on a concole stating html not defined (or something like that!)?

I can now manually change the csv file and see the graph change but only
on "Chromium".

I have been looking at the "Alias" command in apache on the Pi but it
fails to point to my temp.log file.

What I am trying to do is serve my dynamic /home/pi/temp.log by making
it available in /var/www/.

I tried to put something in /etc/apache2/sites-enabled/000-default but
no luck atm so if there is a Pi/Apache2 expert on the list, I would
appreciate any pointers!?

Regards

--
Peter H

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

Message: 2
Date: Sat, 27 Dec 2014 19:02:02 +0000
From: Chris <cshorler@googlemail.com>
To: Bristol and Bath Linux User Group <bristol@mailman.lug.org.uk>
Subject: Re: [bristol] DyGraph (Pi)
Message-ID: <CD8D4975-FFA9-4EF7-AB78-CE6E8F5FC5FA@googlemail.com>
Content-Type: text/plain; charset=UTF-8

On 27 December 2014 12:32:53 GMT+00:00, Peter Hemmings <peter@hemmings.eclipse.co.uk> wrote:
>Seasons Greetings to all lurkers and active members.
>
>Update:
>
>Pi continues to work outputting humidity/temperature data into
>"temp.log" so the first script and cron job is OK.
>As Apache does not accept symlinks I copied data into a static
>"temp.log" to test scripts before looking at apache.
>
>I still could not get it to work on the Pi.
>I copied data csv file (temp.log), html file "temp.html" (dygraph
>script) and dygraph-combined.js from Pi to fc19 laptop and took it to
>KT
>last week and it worked!
>
>The files are in /var/www/html/ on fc19 and in /var/www/ on Raspian Pi.
>
>To keep things simple and try to avoid typos, I deleted files on Pi
>and
>copied them back from fc19 that worked!
>
>Pi comes with two "cut-down" browsers "Epiphany" and "NetSurf".
>
>Checked local IP address and that apache2 was running OK on Pi, but got
>
>nothing on both Browsers (just blank page, no graphs or errors).
>
>As my Pi is now on a larger SD card, I installed "Chromium".
>
>Tried it, and it works!!
>
>So why could this be, is it to do with font characters, I did see an
>error on a concole stating html not defined (or something like that!)?
>
>I can now manually change the csv file and see the graph change but
>only
>on "Chromium".
>
>I have been looking at the "Alias" command in apache on the Pi but it
>fails to point to my temp.log file.
>
>What I am trying to do is serve my dynamic /home/pi/temp.log by making
>it available in /var/www/.
>
>I tried to put something in /etc/apache2/sites-enabled/000-default but
>no luck atm so if there is a Pi/Apache2 expert on the list, I would
>appreciate any pointeresource
19

If the pi is running a web server (Apache), you don't need to fire up a web browser on the pi to access it. You can use your laptop browser and enter the pi as the server.

http://pi-ip-addr/path/to/resource
(Note if your page is not the default index, then you will need to specify a filename e.g. test.html if that's what you called your example)

If it doesn't work you can dig deeper by watching the network interactions and for JavaScript errors in the console in the browser development tools (Firefox or Chromium as we saw at the LUG)

If it points to a resource issue, you might need to tweak something on the pi (move a resource or tweak the Apache config). Perhaps the sub-directory on your FC19 is important.

>Regards

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

Message: 3
Date: Sat, 27 Dec 2014 20:55:47 +0000
From: Peter Hemmings <peter@hemmings.eclipse.co.uk>
To: Bristol and Bath Linux User Group <bristol@mailman.lug.org.uk>
Subject: Re: [bristol] DyGraph (Pi)
Message-ID: <549F1CD3.5080204@hemmings.eclipse.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed

>> I tried to put something in /etc/apache2/sites-enabled/000-default
>> but no luck atm so if there is a Pi/Apache2 expert on the list, I
>> would appreciate any pointeresource
> 19
>
> If the pi is running a web server (Apache), you don't need to fire up
> a web browser on the pi to access it. You can use your laptop
> browser and enter the pi as the server.
>
> http://pi-ip-addr/path/to/resource

Yep that is no problem, I can see it on the laptop OK, I was using the
pi browser for ease of use.

> (Note if your page is not the default index, then you will need to
> specify a filename e.g. test.html if that's what you called your
> example)

I have now added the following in 000-default in an attempt for apache2
to find my data now cronned into /home/pi/www/temp.log but its not
finding it:

Alias /var/www/ "home/pi/www/"
<Directory "/home/pi/www/">
order allow,deny
Allow from all
Require all granted
Options Indexes FollowSymLinks
<Directory>

Restarted apache and tried "Local IP/temp.html thinking it would then
find the temp.log data in /home/pi/www/ but it doesn't and I need to check.

There were no errors when I restarted apache so my additions seem OK
syntax wise!

I am attempting to use the original Dygraph program and the script to
generate the graph from /var/www/ and pick up the data from /home/pi/www/

I renamed the temp.log (the static one that worked) from /var/www/ so
that I it would look in /home/pi/www/, but it didn't.
>
> If it doesn't work you can dig deeper by watching the network
> interactions and for JavaScript errors in the console in the browser
> development tools (Firefox or Chromium as we saw at the LUG)
>
> If it points to a resource issue, you might need to tweak something
> on the pi (move a resource or tweak the Apache config). Perhaps the
> sub-directory on your FC19 is important.

Used Chrome JS console on laptop and it reported failed to find resource
"temp.log".

So I am now satisfied that all is working except configuring the server
to pick up the temp.log file generated by my new cron job.

This is no longer a priority as I have cured the damp problem I was
going to use it on!

However it would be a shame to stop now as I have almost got it all to
work.

I will do some more reading on configuring apache to read other
directories (symlinks were not recommended).

>
>> Regards
>
>
>
> _______________________________________________ Bristol mailing list
> Bristol@mailman.lug.org.uk
> https://mailman.lug.org.uk/mailman/listinfo/bristol
>

PS: just realized that only "temp.log" is specified in "temp.html" to
generate the graph. I assume I will either need to add the path or put
everything in /home/pi/www/

Regards
--
Peter H

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

Message: 4
Date: Sun, 28 Dec 2014 09:17:34 +0000
From: Chris <cshorler@googlemail.com>
To: Bristol and Bath Linux User Group <bristol@mailman.lug.org.uk>
Subject: Re: [bristol] DyGraph (Pi
Message-ID: <F70A7567-5E93-40E6-96A4-BBFE6D2C980F@googlemail.com>
Content-Type: text/plain; charset=UTF-8

On 27 December 2014 20:55:47 GMT+00:00, Peter Hemmings <peter@hemmings.eclipse.co.uk> wrote:
>
>>> I tried to put something in /etc/apache2/sites-enabled/000-default
>>> but no luck atm so if there is a Pi/Apache2 expert on the list, I
>>> would appreciate any pointeresource
>> 19
>>
>> If the pi is running a web server (Apache), you don't need to fire up
>> a web browser on the pi to access it. You can use your laptop
>> browser and enter the pi as the server.
>>
>> http://pi-ip-addr/path/to/resource
>
>Yep that is no problem, I can see it on the laptop OK, I was using the
>pi browser for ease of use.
>
>> (Note if your page is not the default index, then you will need to
>> specify a filename e.g. test.html if that's what you called your
>> example)
>
>I have now added the following in 000-default in an attempt for apache2
>
>to find my data now cronned into /home/pi/www/temp.log but its not
>finding it:
>
>Alias /var/www/ "home/pi/www/"
><Directory "/home/pi/www/">
>order allow,deny
>Allow from all
>Require all granted
>Options Indexes FollowSymLinks
><Directory>
>
>Restarted apache and tried "Local IP/temp.html thinking it would then
>find the temp.log data in /home/pi/www/ but it doesn't and I need to
>check.
>
>There were no errors when I restarted apache so my additions seem OK
>syntax wise!
>
>I am attempting to use the original Dygraph program and the script to
>generate the graph from /var/www/ and pick up the data from
>/home/pi/www/
>
>I renamed the temp.log (the static one that worked) from /var/www/ so
>that I it would look in /home/pi/www/, but it didn't.
>>
>> If it doesn't work you can dig deeper by watching the network
>> interactions and for JavaScript errors in the console in the browser
>> development tools (Firefox or Chromium as we saw at the LUG)
>>
>> If it points to a resource issue, you might need to tweak something
>> on the pi (move a resource or tweak the Apache config). Perhaps the
>> sub-directory on your FC19 is important.
>
>Used Chrome JS console on laptop and it reported failed to find
>resource
>"temp.log".
>
>So I am now satisfied that all is working except configuring the server
>
>to pick up the temp.log file generated by my new cron job.
>
>This is no longer a priority as I have cured the damp problem I was
>going to use it on!
>
>However it would be a shame to stop now as I have almost got it all to
>work.
>
>I will do some more reading on configuring apache to read other
>directories (symlinks were not recommended).
>
>>
>>> Regards
>>
>>
>>
>> _______________________________________________ Bristol mailing list
>> Bristol@mailman.lug.org.uk
>> https://mailman.lug.org.uk/mailman/listinfo/bristol
>>
>
>PS: just realized that only "temp.log" is specified in "temp.html" to
>generate the graph. I assume I will either need to add the path or put
>
>everything in /home/pi/www/
>
>
>
>Regards

I think you may be over complicating it... did you read this: ?

http://httpd.apache.org/docs/2.2/howto/public_html.html

Sub heading per-user web directories

Or put the file under /var/www

I doubt you need to configure alias

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

Message: 5
Date: Sun, 28 Dec 2014 11:07:26 +0000
From: Peter Hemmings <peter@hemmings.eclipse.co.uk>
To: Bristol and Bath Linux User Group <bristol@mailman.lug.org.uk>
Subject: Re: [bristol] DyGraph (Pi
Message-ID: <549FE46E.5090005@hemmings.eclipse.co.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed

On 28/12/14 09:17, Chris wrote:
> I think you may be over complicating it... did you read this: ?

!

I have now.

>
> http://httpd.apache.org/docs/2.2/howto/public_html.html
>
> Sub heading per-user web directories
>
> Or put the file under /var/www

I assume you mean cron job it to /var/www/.

I had not tried that because I was not sure if there would be permission
problems.

>
> I doubt you need to configure alias
>

Agreed

It seems that if I am testing with Fedora I also need to set SELinux to
allow htppd to read any files in my directory, so will go back and try
on pi only!

I will check to find if module "mod_userdir" is loaded as well.

Will have another go at it later.

Regards
--
Peter H

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

_______________________________________________
Bristol mailing list
Bristol@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/bristol

End of Bristol Digest, Vol 582, Issue 3
***************************************

Bristol and Bath Linux

Selasa, 30 Desember 2014

Bristol Digest, Vol 583, Issue 2

Senin, 29 Desember 2014

Bristol Digest, Vol 583, Issue 1

Minggu, 28 Desember 2014

Bristol Digest, Vol 582, Issue 3

Selasa, 23 Desember 2014

Bristol Digest, Vol 582, Issue 2

Senin, 22 Desember 2014

Bristol Digest, Vol 582, Issue 1

Minggu, 21 Desember 2014

Bristol Digest, Vol 581, Issue 8

Sabtu, 20 Desember 2014

Bristol Digest, Vol 581, Issue 7

Jumat, 19 Desember 2014

Bristol Digest, Vol 581, Issue 6

Bristol Digest, Vol 581, Issue 5

Kamis, 18 Desember 2014

Bristol Digest, Vol 581, Issue 4