Re: [Server-devel] [XSCE] Re: Weekly log rotation

2013-09-19 Thread Jon Nettleton
Had to take a look at my server to evaluate.  The problem is that in
/etc/logrotate.d/ there is a symlink '*' pointing to /usr/share/xs


On Thu, Sep 19, 2013 at 7:56 AM, Anna ascho...@gmail.com wrote:

 On Thu, Sep 19, 2013 at 12:48 AM, Jon Nettleton 
 jon.nettle...@gmail.comwrote:

 Does it work if you run /etc/cron.daily/logrotate by hand as root?


 Nope:

 [root@schoolserver] ~ cd /etc/cron.daily/
 [root@schoolserver] cron.daily ./logrotate
 error: failed to open config file *: No such file or directory
 error: found error in file *, skipping

 So this is weird to see this in there:
 [root@schoolserver] ~ ls /etc/cron.daily/
 etckeeper  logrotate  man-db.cron  mlocate.cron

 [root@schoolserver] cron.daily cat logrotate
 #!/bin/sh

 /usr/sbin/logrotate /etc/logrotate.conf
 EXITVALUE=$?
 if [ $EXITVALUE != 0 ]; then
 /usr/bin/logger -t logrotate ALERT exited abnormally with
 [$EXITVALUE]
 fi
 exit 0
 [root@schoolserver] cron.daily whereis logger
 logger: /bin/logger /usr/bin/logger /usr/share/man/man1p/logger.1p.gz

 And there's nothing here:

 [root@schoolserver] ~ ls /etc/cron.weekly/
 [root@schoolserver] ~ 






 On Thu, Sep 19, 2013 at 7:40 AM, Anna ascho...@gmail.com wrote:

 On Thu, Sep 19, 2013 at 12:38 AM, Jon Nettleton jon.nettle...@gmail.com
  wrote:

 What does your /etc/logrotate.conf look like?  One option for logrotate
 is to only rotate if the logs have reached a certain size.


 My understanding was it was supposed to rotate weekly no matter what.

 [root@schoolserver] ~ cat /etc/logrotate.conf
 # see man logrotate for details
 # rotate log files weekly
 weekly

 # keep 4 weeks worth of backlogs
 rotate 4

 # create new (empty) log files after rotating old ones
 create

 # use date as a suffix of the rotated file
 dateext

 # uncomment this if you want your log files compressed
 #compress

 # RPM packages drop log rotation information into this directory
 include /etc/logrotate.d

 # no packages own wtmp and btmp -- we'll rotate them here
 /var/log/wtmp {
 monthly
 create 0664 root utmp
 minsize 1M
 rotate 1
 }

 /var/log/btmp {
 missingok
 monthly
 create 0600 root utmp
 rotate 1
 }

 # system-specific logs may be also be configured here.





___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] [XSCE] Re: Weekly log rotation

2013-09-19 Thread Jon Nettleton
sorry cramped typing space.  There is a symlink of '*' pointing to
/usr/share/xs-config/cfg/etc/logrotate.d/*  This must be an error in the
image generation script.

-Jon


On Thu, Sep 19, 2013 at 8:37 AM, Jon Nettleton jon.nettle...@gmail.comwrote:

 Had to take a look at my server to evaluate.  The problem is that in
 /etc/logrotate.d/ there is a symlink '*' pointing to /usr/share/xs


 On Thu, Sep 19, 2013 at 7:56 AM, Anna ascho...@gmail.com wrote:

 On Thu, Sep 19, 2013 at 12:48 AM, Jon Nettleton 
 jon.nettle...@gmail.comwrote:

 Does it work if you run /etc/cron.daily/logrotate by hand as root?


 Nope:

 [root@schoolserver] ~ cd /etc/cron.daily/
 [root@schoolserver] cron.daily ./logrotate
 error: failed to open config file *: No such file or directory
 error: found error in file *, skipping

 So this is weird to see this in there:
 [root@schoolserver] ~ ls /etc/cron.daily/
 etckeeper  logrotate  man-db.cron  mlocate.cron

 [root@schoolserver] cron.daily cat logrotate
 #!/bin/sh

 /usr/sbin/logrotate /etc/logrotate.conf
 EXITVALUE=$?
 if [ $EXITVALUE != 0 ]; then
 /usr/bin/logger -t logrotate ALERT exited abnormally with
 [$EXITVALUE]
 fi
 exit 0
 [root@schoolserver] cron.daily whereis logger
 logger: /bin/logger /usr/bin/logger /usr/share/man/man1p/logger.1p.gz

 And there's nothing here:

 [root@schoolserver] ~ ls /etc/cron.weekly/
 [root@schoolserver] ~ 






 On Thu, Sep 19, 2013 at 7:40 AM, Anna ascho...@gmail.com wrote:

 On Thu, Sep 19, 2013 at 12:38 AM, Jon Nettleton 
 jon.nettle...@gmail.com wrote:

 What does your /etc/logrotate.conf look like?  One option for
 logrotate is to only rotate if the logs have reached a certain size.


 My understanding was it was supposed to rotate weekly no matter what.

 [root@schoolserver] ~ cat /etc/logrotate.conf
 # see man logrotate for details
 # rotate log files weekly
 weekly

 # keep 4 weeks worth of backlogs
 rotate 4

 # create new (empty) log files after rotating old ones
 create

 # use date as a suffix of the rotated file
 dateext

 # uncomment this if you want your log files compressed
 #compress

 # RPM packages drop log rotation information into this directory
 include /etc/logrotate.d

 # no packages own wtmp and btmp -- we'll rotate them here
 /var/log/wtmp {
 monthly
 create 0664 root utmp
 minsize 1M
 rotate 1
 }

 /var/log/btmp {
 missingok
 monthly
 create 0600 root utmp
 rotate 1
 }

 # system-specific logs may be also be configured here.






___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


Re: [Server-devel] [XSCE] Re: Weekly log rotation

2013-09-19 Thread James Cameron
Ouch.

I was looking at what might go into /etc/logrotate.d but had neglected
to consider a symlink '*'.

On Thu, Sep 19, 2013 at 08:37:31AM +0200, Jon Nettleton wrote:
 Had to take a look at my server to evaluate.  The problem is that in /etc/
 logrotate.d/ there is a symlink '*' pointing to /usr/share/xs
 
 
 On Thu, Sep 19, 2013 at 7:56 AM, Anna ascho...@gmail.com wrote:
 
 On Thu, Sep 19, 2013 at 12:48 AM, Jon Nettleton jon.nettle...@gmail.com
 wrote:
 
 Does it work if you run /etc/cron.daily/logrotate by hand as root?
 
 
 Nope:
 
 [root@schoolserver] ~ cd /etc/cron.daily/
 [root@schoolserver] cron.daily ./logrotate 
 error: failed to open config file *: No such file or directory
 error: found error in file *, skipping
 
 So this is weird to see this in there:
 [root@schoolserver] ~ ls /etc/cron.daily/
 etckeeper  logrotate  man-db.cron  mlocate.cron
 
 [root@schoolserver] cron.daily cat logrotate 
 #!/bin/sh
 
 /usr/sbin/logrotate /etc/logrotate.conf
 EXITVALUE=$?
 if [ $EXITVALUE != 0 ]; then
     /usr/bin/logger -t logrotate ALERT exited abnormally with 
 [$EXITVALUE]
 
 fi
 exit 0
 [root@schoolserver] cron.daily whereis logger
 logger: /bin/logger /usr/bin/logger /usr/share/man/man1p/logger.1p.gz
 
 And there's nothing here:
 
 [root@schoolserver] ~ ls /etc/cron.weekly/
 [root@schoolserver] ~ 
 
 
  
 
 
 
 On Thu, Sep 19, 2013 at 7:40 AM, Anna ascho...@gmail.com wrote:
 
 On Thu, Sep 19, 2013 at 12:38 AM, Jon Nettleton 
 jon.nettle...@gmail.com wrote:
 
 What does your /etc/logrotate.conf look like?  One option for
 logrotate is to only rotate if the logs have reached a certain
 size.
 

 
 My understanding was it was supposed to rotate weekly no matter
 what.
 
 [root@schoolserver] ~ cat /etc/logrotate.conf 
 # see man logrotate for details
 # rotate log files weekly
 weekly
 
 # keep 4 weeks worth of backlogs
 rotate 4
 
 # create new (empty) log files after rotating old ones
 create
 
 # use date as a suffix of the rotated file
 dateext
 
 # uncomment this if you want your log files compressed
 #compress
 
 # RPM packages drop log rotation information into this directory
 include /etc/logrotate.d
 
 # no packages own wtmp and btmp -- we'll rotate them here
 /var/log/wtmp {
     monthly
     create 0664 root utmp
 minsize 1M
     rotate 1
 }
 
 /var/log/btmp {
     missingok
     monthly
     create 0600 root utmp
     rotate 1
 }
 
 # system-specific logs may be also be configured here.
  
 
 
 
 
 
 

-- 
James Cameron
http://quozl.linux.org.au/
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel


[Server-devel] XSCE IRC Scrum Minutes - September 17

2013-09-19 Thread Anish Mangal
Hi all,

Apologies for the delay in sending the minutes, we had our second XSCE IRC
Scrum this Tuesday/September-17. Here are the highlights:

*=This is the rolling agenda document = *
https://docs.google.com/document/d/1o6QtzLb6e58YKWqMf_junux2XyBRLFm31un8YLcYslg/edit

*=Key highlights/minutes=*

*==XSCE-0.4 RC-2 status==*

1. The release-0.4 branch has been created, and builds are being
automatically created from git commits

Path for rpm packages:
http://xsce.activitycentral.com/repos/xsce/release-0.4/RPMS/noarch/

Path for release-0.4 git repository:
https://sugardextrose.org/projects/xsce/repository/show?rev=release-0.4

2. RC-2 release is expected this within this week. Get your testing arsenal
ready! :-)


*==OLPC SF proposal ideas==*

1. There is talk about getting a XSCE-0.4 server running on a trimslice (
http://utilite-computer.com/web/trim-slice) and a cubox-i (
http://cubox-i.com/) for the conference

2. Deployment experiences : Bhagmalpur, Haiti

3. XSCE-0.5 Sprint (in SF and then Malaysia) -
http://wiki.laptop.org/go/XS_Community_Edition/0.5/Sprint

4. Sprint location in SF: http://sftechcenter.org/free-meeting-space/


*==Malaysia progress==*

In Adam's words, we're still aligning the stars, but for anyone interested
in hacking on the server, both the OLPC-SF and Malaysia events will feature
XSCE (with hopefully productive hacksprints). Please make your way to
either/both of these conference if you can. :-)

Also, here's the Malaysia blog which is updated very regularly -
http://olpcbasecamp.blogspot.com/


*==Squid caching on AP's in mesh mode==*

There has been talk around working with the OpenWRT based SECN firmware for
routers. We are exploring whether a wireless mesh network can be deployed,
and finding ways in which overall network capacity may be improved. One of
the ways to do that is to provide data caching on the Access Points itself.
Modern routers have decent amounts of RAM and a USB port (for additional
memory), so something like squid might potentially work wonders.

Relevant links:
http://villagetelco.org/2011/04/small-enterprise-campus-network-secn/


*==XSCE: featured pilot deployments==*

One of the fundamental premises behind the XSCE project is engaging the
deployment community in every possible step possible. As we move forward,
we would REALLY benefit from working with deployments on specific features
we are developing. For example, we could really benefit from real world
data while refining the mesh networking proposal. This would add value to
deployments, in that it will make it much easier and cost effective for
them to deploy wireless networking, while still being able to meet
performance requirements.

The XSCE community is willing to throw it's weight behind supporting
deployments' needs if there is a willingness to work together. So, if
you're interested, please get in touch :-)


*==NYC Sept 21-22 showcase==*

XSCE-0.4 RC-2 running on a trimslice will be featured during the NYC
Makerfaire event at NYC Sept 21-22. If you're in the area, feel free to
drop in and give it a spin.


*==XSCE-0.5 dreams==*

With the approaching release of 0.4 and upcoming conferences, 0.5 plans are
quickly taking shape. Here are some of the things that were suggested:

* Basing on Ansible, and providing an admin GUI (through Ajenti)
* Passwordless client authentication
* Youtube video caching for squid
* XSCE as a vnc multicast reflector
* Setting up different default configs based hardware heuristics and number
of users
* Take advantage of crypto hardware if available for https/ssh/vpn
* your idea here

I think in terms of next steps, we need to get the wiki in shape so these
ideas may be properly documented, and a meaningful discussion results.

*=Here are the minutes as recorded by the bot=*
https://sugardextrose.org/issues/4687

*=Here are the full logs=*
https://sugardextrose.org/attachments/3146/schoolserver.2013-09-17-16.04.log.txt

Best,
Anish
___
Server-devel mailing list
Server-devel@lists.laptop.org
http://lists.laptop.org/listinfo/server-devel