Free weekly software for linux

EventCal project is a calendar class that allows events to be managed and output to HTML in daily, weekly, and monthly views.
Classes
class Calendar
Methods defined here:
__init__(self, language=en)
Creates an empty event list and sets the language
add(self, event)
cell(self, type=free, s=)
dayview(self, day, month=1, year=2007, smallify=False)
Generates a two-column table for the specific day with one column
holding the hours and the other holding any events
eventlist(self)
Generates an unordered list with all events listed
monthview(self, month=1, year=2007, smallify=False)
setlang(self, language)
Sets the months and week day names to the appropriate language
weekview(self, day, month=1, year=2007, smallify=False)
class Event
Events are only specific down to the hour. start and length are hours.
Methods defined here:
__cmp__(self, other)
Comparison method. Returns true if the day, month and year match
__init__(self, message, start, length, day, month, year)
__repr__(self)
Functions
am_pm(x)
Convert 24hour integer to 12hour string i.e. 13 becomes 1pm
geteventdayname(event)
interval(startHour, length)
Returns a string: startHour(am/pm) to startHour+length(am/pm). 12 noon is replaced with noon
shiftday(day)
Shifts from Sun-Sat to Mon-Sun
today(smallify=False)
weekday(day, month, year)
Returns the day of the week from 0-6 starting from Monday
Data
daynames = [Sunday, Monday, Tuesday, Wednesday, Thursday, Friday, Saturday]
mdays = [31, 28, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31]
months = [January, February, March, April, May, June, July, August, September, October, November, December
Enhancements:
- All strings were converted to use Unicode.
- Spanish translations for day and month names were added.
- __getattr__ was replaced with properties.
- String replacer body were replaced with calls to re.sub so the $ can be escaped with a backslash.
- The first week of monthview was fixed to properly replace format.
- About 20 lines of code that generated the first week in the monthview were removed.

Beanie is a flexible, distributed accounting system for medium-sized companies.
It includes back-end batch processing as well as a GTK GUI and provides automated purchases, sales, and nominal ledgers as well as automated invoicing (via email).
Beanie project also supports payroll and VAT.
Installation:
STEP ONE:
You must create a user on the system called beanie. This unprivileged user will own all the accounting files and executables. The home directory of this user will be the main location for all accounting files so choose wisely. Examples are /v/beanie or
/var/accounts.
This is an example of the password entry:
beanie:*:101:20:The Accounting System:/v/beanie:/bin/csh
Make sure you set the BEANIEROOT environment variable in the file beanie.mk to the home directory of the beanie user.
STEP TWO:
You must create a MySQL database called beanie. You then need to create a user also called beanie with a 8 to 10 character password which has full access to this database. Check that you can access the new database using the following command:
% mysql -h -u beanie -p beanie
You will be prompted for a password. Enter the password you set on the account and youre now ready to create a config.h file.
STEP THREE:
Copy the file config.h.sample to config.h and edit it. You will find information on how to configure this file in the comment blocks of the file. Note that the MAIN_DBHOST and DBPWD_CHARxx values need to match what you entered above.
STEP FOUR:
Edit the file beanie.mk and make sure that the defaults are OK.
Once you have completed these steps, compile the source by running the following commands:
% make clean all
% make install
You may need to run the second make as root in order to have permissions to create directories and some binary files (such as xeparse which needs to be installed in /usr/libexec).
STEP FIVE:
You need to create a cron(8) entry for the beanie user. There is a sample cron entry in the file crontab.sample. Edit this file and change $BEANIEROOT to be the home directory of the beanie user. Then, either logged in as beanie or as root, run the following command:
% crontab -u beanie < crontab.sample
This makes sure the overnight processing is performed every evening at 11PM. Each day, the databases will be backed up and the daily operations (such as invoicing, etc) will be performed. Each Sunday, the end of week tasks will be performed and on the last day of the month, the monthly, quarterly and annual tasks will be performed.
You can examine these scripts to see what they do:
overnight/acct.prolog
overnight/acct.daily
overnight/acct.weekly
overnight/acct.monthly
overnight/acct.epilog
Edit the tmac source files for your specific information. The key one here is lhead.tmac because this is the source for your company letterhead. Its written in troff.
Youre Done!! Now you just need to run the newcompany program.
Enhancements:
- In this initial release, the billing functionality is very complete and the general ledger functionality is pretty much all there.
- A VAT system was added with a payroll check-in due very shortly.

Health Tip Buddy Email System is a nice tool you can add to your web site that will allow your visitors to sign up for an automatic health-tip email list.
Its easy to change the look and feel of the e-mails to match your web site, and the system allows for e-mail restrictions so that you dont make your hosting provider unhappy.
Main features:
- Installation is easy, just upload the script and run the install file to automatically install your database tables and set up your configuration.
- Set the time between mailings. Want a weekly e-mailing? Daily? No problem you set the length.
- Easily set how many e-mails can be sent in a day or hour to avoid getting on your hosting providers bad side. The e-mails are stored and those that cant be sent right away will be sent later.
- Add custom health tips of your own!
- Visitor sign-up script includes a Captcha device to avoid automated signups by spammers.

NewSyslog is a highly configurable program for managing and archiving log files.
Main features:
- It is more portable (using GNU Autoconf) and it can be compiled and installed on most any modern Unix or Unix-like system.
- It has support for fixed time-of-day daily archiving with a command-line option to identify the daily roll-over invocation (which may be at midnight, or at any other regular daily time).
- It supports the FreeBSD feature that allows specification of the log roll-over time as a daily, weekly, or monthly interval (with optional time-of-day specification for the last two). [The other overly flexible, ISO 8601 interpretation of the interval "@" option is not supported -- it is too generic and not meaningful enough in the context of log file management.]
- It supports optional PID files so that non-standard daemons can be told to re-open their logfiles after archiving has taken place. (Including /dev/null which disables signalling of any daemon when the specified log file is rolled over.)
- It can send a signal other than SIGHUP to the daemon associated with a given log file.
- It can leave the most recently archived log file uncompressed, which is necessary for daemons like httpd and smail because they continue to write to the current log file until their current jobs have completed. (This also makes it much easier to review recent log data with normal Unix tools.) [NetBSD now has this feature.]
- It supports the FreeBSD feature of being able to restrict processing to just those log files specified on the command line.
- Unlike the NetBSD version it first parses the config file before taking any action, meaning that if any errors are encountered it will report them and quit without doing anything.
- Unlike the FreeBSD version, it will roll a log file if either the interval or size limits have been reached (FreeBSDs version makes it too easy to have a rapidly growing log file overflow the filesystem).
- Unlike the NetBSD version it always creates any missing log file (though this can be disabled on a per-file basis).
- It uses an advisory lock on the current configuration file to prevent multiple invocations from tripping over each other.
- The documentation is far better!

This is a small Perl script to create backup CDs out of images. I like to organize my digital pictures into a directory structure based on image content and subject. I dont store them by date. This makes it nice to find pictures, but difficult to back them up without using traditional incremental backup software and/or backing up some images more than once.

Although this program is made to work well with AutoScrapbook, it can work with any directory of images. You run the program and specify a base directory. The directory is processed recursively and any images are mirrored into a staging area.

Once enough images are in the staging area, the program will (optionall) run AutoScrapbook to create a set of web pages specifically for that disc of images. It will then create an ISO image that you can burn to CD when convenient. This script is made to work on Linux, but could work on other systems with a bit of modification.

Once a disc has been created, the list of images that were on that disc is stored in a hidden data file in the base directory specified. You can then run ImageBackup on that directory again. Any images not included in any previous backups will be mirrored to the (now empty) staging directory.

If the directory fills, another ISO will be generated. If not, the staging directory will remain partially-filled. You can then run ImageBackup regularly (i.e. from cron even) and new images will be added to the staging directory as they are found. Whenever the disc is full enough, an ISO is generated, and the whole process starts over.
Installation/Use

To use the program, simply download the program below and place it somewhere on your system. If your Perl interpreter is not in /usr/bin/perl, you will have to edit the first line of the file.

Edit the program and change any of the variables near the top that need to be changed.

Then, simply run the program with a directory name as a parameter. You should always enter the same base directory name for good results. If, for example, you run ImageBackup on ~/pictures and created a backup CD, you should always run it on the same directory from then on.

Automatic Runs

You can have this script run automatically -- say once per week. Just run this script from cron (on Red Hat Linux, for example, just place this in /etc/cron.weekly):

#!/bin/bash

email="kirk@kaybee.org"
image_backup="/home/kirk/projects/misc/image_backup.pl"
DIRS="/export/share/pictures"
TEMPDIR="/home/kirk/tmp"

mkdir -p "$TEMPDIR"

for dir in $DIRS ; do
echo "Processing directory $dir"
echo
iso=`$image_backup $dir 2> "$TEMPDIR/image_backup.errors" | grep ^ISO Image Ready:`
if [ $? == 0 ] ; then
echo "$iso"
mail -s "$iso" $email < /dev/null
exit 0
elif [ $? == -1 ] ; then
echo "Not enough images yet..."
exit -1
else
echo "ERROR running image backup!" >&2
mail -s Image backup errors! $email < "$TEMPDIR/image_backup.errors"
exit 1
fi
done

Now you will receive an email whenever a new ISO image is available or if there are any errors.

Note that if you configure ImageBackup to use AutoScrapbook to create an index on the backup CDs, you must have already run AutoScrapbook on the source directories if you are running ImageBackup non-interactively.

If you havent, then picture descriptions will be requested during the cron job, which wont work too well.

ComputeMode project is an Icatis product that extends an organizations Computational Grid through aggregation of unused computing resources.
For instance, ComputeMode lets a virtual cluster to be built using employees PCs at their idle times. Practically most PCs in large companies are not used at night, on weekends, and during employee vacations, training periods or business trips.
So ComputeMode allows you to take the benefits of the powerful computation infrastructure you already have, but you are not aware of!
Another interesting use of ComputeMode is within computer classrooms, where PCs can be automatically harnessed into a virtual cluster when they are not being used (night, week-ends, holidays).
ComputeMode relies on a ComputeMode Server that keeps track of the availability of some dedicated PCs on the local network. Each PC Owner has a weekly availability Schedule, identifying periods when he or she is not using his/her PC. For instance, a PC owner can declare working periods from 8:00 to 18:00, Monday to Friday.
In the remainder of this document, we will refer to PCs handled by ComputeMode as Processing Nodes.
The ComputeMode Administrator can easily manage the computing PCs through a Web-based interface, accessed through the ComputeMode Server.
A Grid User can submit some computational Jobs to the system through the use of a classical Batch Manager (also called "Job Management System", "Distributed Resource Managers", or "Queuing System").
The Grid User can log onto the Batch Manager from any machine of the local network (usually through the "ssh" secure shell). The Batch Manager will then reserve appropriate resources for the computations, Schedule the execution of the Jobs depending on the overall load on the Computing Grid and allocate Jobs to available computing resources.
The OAR Batch Manager is installed by default with ComputeMode, even though other products such as Platform LSF, OpenPBS or Sun Grid Engine are supported by ComputeMode.
ComputeMode can monitor the load on the Batch Manager, and detect overloads. In such cases it can allocate available Processing Nodes to computational tasks.
Each Processing Node has two different operating modes:
- The User Mode, in which the machine is working in its standard way under Microsoft Windows for instance. The Owner of the machine will not even notice that his or her PC is managed as a ComputeMode Processing Node. In particular, the computational resources of the PC will not be used while in User Mode.
- The Computation Mode (this is where the name of our product comes from) is activated when the machine is in a time period where the PC is declared as "idle". In case the ComputeMode Server detects some computational peak, the PC can be remotely switched to Computation Mode. The switch from user mode is done through an automatic reboot of the machine and proceeds to a remote boot. The remote boot is handled by the ComputeMode Server with the "Preboot eXecution Environment" (PXE) protocol, which is natively available from the BIOS of PCs since 1999. While in Computation Mode, the machine is running under the Linux Operating System, and does not have any access to any local hard disk.
When the ComputeMode Server detects that some given Processing Node is no longer available for computation, it restores the machine back to its User Mode, so that the Owner will not even notice that his or her PC has been used by ComputeMode.
The submitted Jobs can take advantage of the NFS distributed file system, which is made available from the ComputeMode Server. Each Grid User has his or her own private directory and can use it for data required by the computational Jobs, as well as to retrieve the produced output files.
A specific case may happen if a PC Owner comes back and needs his or her PC while a computational Job is being processed. This can happen, for instance, if the Owner has an urgent need and comes back at night to work on his/her PC. In such a situation, the owner always has priority over the machine. Just by using the keyboard, the Owner can abort any ongoing computational activity on his/her PC, and ComputeMode will restore the machine to its User Mode in about one minute.
Enhancements:
- UI usability improvements, code cleanup, and fixes were made.
- The client and server system were upgraded.
- New, simpler node import/export was added.
- It is available as a virtual appliance.

Getbinnews is a newsreader developed in C using the GTK user interface (for Linux, FreeBSD and OpenBSD OS) .
The aim of Getbinnews is to extract in some newsgroups a binary file (mp3, jpg, gif,mpg, asf, avi, divx...) splited in articles with mime, uuencode or yenc format.
Main features:
Connection support
- definition of name and port of news server
- definition of user and password to connect the news server
- times reconnection in some cases (timeout, connection error or connection reject)
- number of connections
- bandwidth throttle
Dialer
- connection and deconnection to internet
Filter
- filter by fields
- filter by size
- filter by size of articles
- filter if incomplete
- filter if part 1 is missing
- filter if more than n articles
Search newsgroups
- search newsgroups on server
- search/filter newsgroups by regex expression
- search by wildmat
Search for article
- selection of all articles of a file (right click)
- search for subject
- filter for subject
- number of articles to download.
- number of selected articles (right click)
Decode methods
- yenc support
- uuencode support
- base64 support
- mime support
Files
- definition of files directory
- definition of articles directory
- cleanup articles
- cleanup files
- behavior if files exist.
- behavior if not enough space
- dont delete articles.
Newsgroups
- download list of newsgroups
Group List
- Definition of newsgroups list to search articles.
- personnalisation of search for a particular newsgroups
Scheduler
- Schedule periodic search (daily, weekly, or monthly)
- Schedule non periodic search
- hang up internet connection at end of the search.
History
- Creation of an history file to stop download articles already download
hide button to stop search.