Free umask software for linux

Courier-IMAP is a fast, scalable, enterprise IMAP server that uses Maildirs. Many E-mail service providers use Courier-IMAP to easy handle hundreds of thousands of mail accounts.
With the built-in IMAP and POP3 aggregation proxy in Courier-IMAP 4.0, the only practical limit to Couriers horizontal scalability is available LAN bandwidth. In proxy mode, a pool of Courier servers receive IMAP and POP3 connections from clients, wait for the clients to send a login request, look up the mail accounts server, and establish a proxy connection to the actual server that hosts the mail account.
Please note that this IMAP server does NOT handle traditional mailbox files (/var/spool/mail, and derivatives), it was written and optimized for the specific purpose of providing IMAP access to Maildirs.
"Maildir" is a directory-based mail storage format originally introduced in the Qmail mail server, and adopted as an alternative mail storage format by both Exim and Postfix. Courier-IMAP is popular on Qmail/Exim/Postfix sites that are configured to use maildirs. The primary advantage of maildirs is that multiple applications can access the same Maildir simultaneously without requiring any kind of locking whatsoever. Maildir is a faster and more efficient way to store mail. It works particularly well over NFS, which has a long history of locking-related woes.
This is the same IMAP server thats included in the Courier mail server, but configured as a standalone IMAP server that can be used with other mail servers - such as Qmail, Exim, or Postfix - that deliver to maildirs. A Courier/Postfix combination is very popular. If you already have Courier installed, you do not need to download this version. If you install this version, you must remove it if you later install the entire Courier server. Its possible to have both versions installed, but this will require a delicate juggling act that youll have to learn on your own.
Enhancements:
- A bug in quota calculation on 64-bit platforms has been fixed.
- The IMAP server will try to log the clients bandwidth usage if the server process gets killed by a signal.
- New messages created by the IMAP server will use the servers umask setting.
- Many compiler warnings, error messages, and manual page typos were fixed.

maildrop is the mail filter/mail delivery agent thats used by the Courier Mail Server. You do not need to download maildrop from here if you already have Courier installed. This is a standalone build of the maildrop mail filter that can be used with other mail servers.
maildrop is a filter for local mail delivery agent. It reads the messages and redirects them to users mailbox.
maildrop optionally reads instructions from a file, which describe how to filter incoming mail. These instructions can direct maildrop to deliver the message to an alternate mailbox, or forward it somewhere else. Unlike procmail, maildrop uses a structured filtering language.
maildrop is written in C++, and is significantly larger than procmail. However, it uses resources much more efficiently. Unlike procmail, maildrop will not read a 10 megabyte mail message into memory. Large messages are saved in a temporary file, and are filtered from the temporary file. If the standard input to maildrop is a file, and not a pipe, a temporary file will not be necessary.
maildrop checks the mail delivery instruction syntax from the filter file, before attempting to deliver a message. Unlike procmail, if the filter file contains syntax errors, maildrop terminates without delivering the message. The user can fix the typo without causing any mail to be lost.
Enhancements:
- Messages delivered by maildrop will use the processs inherited umask.
- The -f option now allows an empty return address to be specified.
- The lockmail utility now drops any group-id privileges if the setgid bit was added to lockmails permissions.

log_analysis is a log file analysis engine that extracts relevant data for any of the recognised log messages and produces a summary that is much easier to read.
Main features:
- Logs contain lots of extraneous stuff that I want to be logged, but that I dont want to sift through when I review logs (ie. routine, error-free daemon operation.)
- Logs contain a lot of repetition, which drowns out the interesting entries.
- Noting repetition can be tricky because each entry usually has extra features to make it unique, such as a date, maybe a PID (ie. for syslog), and maybe application-specific information (ie. sendmail queue IDs.)
- One needs to remember to review them. :)
- One needs to be root to looks at logs for some OSs.
- On most systems, looking at the logs for just one day can be a pain.
- If I attack each box I deal with and write a separate script to do all this, Ill waste a lot of time duplicating effort.
- Writing patterns is a pain even if you know regular expressions.
log_analysis is my solution to these problems. It goes through several different kinds of logs (currently syslog, wtmp, and sulog), over some period (defaults to yesterday). It strips out the date and PID, and throws away certain entries. Then it tries each entry against a list of perl regular expressions. Each perl regular expression is associated with a category name and a rule for extracting data. When theres a match, the data-extracting rule is applied, and filed under the category.
If a log entry is unknown, its filed under a special category for unknowns. Identical entries for a given category are sorted and counted. Theres an option to mail the output, so you can just run it out of cron. You can also save a local copy of the output. If you prefer to PGP-mail yourself the output, you can do this, too. The whole thing is designed to be easily extended, complete with an easy plug-in interface. The default mode is for reporting, but it also "real" and "gui" modes for continuous monitoring, complete with action support. Oh, and you can edit patterns in a GUI that helps write regular expressions quickly and easily.
Security
The program needs to run with permissions to read your log files in order to be useful, which usually means root. It does not default to SUID root, and I recommend not making it SUID, so just run it as root (ie. manually or out of cron). Ive tried to avoid temp files everywhere that I can, and in the one case where I do use a temp file, I make sure to use the POSIX tmpnam function instead of trying to make up my own temp file algorithm. The default umask is 077. If you use action commands, there is nothing to stop you from using parts of the log message in insecure ways, so for goodness sake, be careful.
Local extensions
log_analysis already has lots of rules, but chances are that you have log entries that arent already covered. So, log_analysis can easily be extended via a local config file, as documented in the log_analysis manpage. Theres even an easy way to do modular plug-ins.
Enhancements:
- This release includes a "find" feature in the GUI, various bugfixes, and assorted minor features.

Gfarm file system is a next-generation network shared file system.
Gfarm file system will be an alternative solution of NFS, and will meet a demand for much larger, much reliable, and much faster file system.
Enhancements:
New Features
- add -N and -D options for asynchronous file replication.
- add --errlog and --syslog options.
- add Test Suites (make check) for operations test.
- get rid of limitation in use of -a option.
- gfarmfs-exec.sh, mount.gfarmfs and umount.gfarmfs are installed by `make install.
Documentation
- README: add examples of mounting gfarmfs.
Bug fix
- fix a bug such that `umask is not effective on gfarmfs.
- fix a bug such that write(2) cannot write anymore after read(2) gets EOF.
- If filesystem nodes are added or removed, statfs(2) can calculate exactly.
- fix a bug such that f_frsize is not set.

Studs MVC Framework+ contains a port of Apaches Jakarta Struts to PHP, though the libraries included in the rest of the project are much more vast.
In order to implement the Struts port, it was necessary to build a core, object-oriented API in the style of the JDK and the Jakarta Commons, a servlet container to handle HTTP requests and to invoke servlet classes, and finally, a parsing engine for JSP-style template pages.
In the end, the result is an environment which is very similar to that provided by a J2EE Web Container, only everything is implemented in PHP.
While it was possible to carry over many of the concepts, designs and mechanisms from J2EE, some limitations do exist due to the nature of the PHP programming language, such as the lack of checked exceptions (runtime only).
Horizon: An Object-Oriented Environment and API
Horizon bootstraps PHP, cloaking it with a core object layer and adding missing functionality, such as imports based on qualified classname, classloading, runtime exception handling, logging, reflection, iterator language constructs and common libraries, such as an XML Digester. Once horizon takes over, the whole nature of programming in PHP changes dramatically.
Stratus: An HTTP Servlet Container
Stratus brings the servlet model to PHP. The two core features are the web.xml parsing and the doService() method call. PHP hands off what it knows about the request to the Stratus HTTP processor and it dispatches the request to a servlet mapped to the URL pattern, paralleling the workflow of Java Servlets. One crucial aspect of Stratus is that it retains state from one page request to the next by use of PHPs serialization, despite claims that PHP is incapable of this task.
Phase: PHP Server Pages Engine
The most exciting part about this project is the JSP compatible parser and compilation engine. There are a horde of templating engines for PHP, but nothing has topped JSP custom tag libraries when it comes to flexibility, ease of use and integration with the business layer. Phase is a servlet which parses regular JSP syntax, with the exception of scriptlets, which are handled by the PHP parser. Phase also ships with a handful of JSTL-like core tab libraries for data manipulation and output, supporting a full implementation of EL.
Studs proves that PHP is a very capable object-oriented language and that it is possible to use best design practices despite limitations in the language. The runtime exception handling layer should be proof that anything is possible.
The reason I really like PHP is because the core functions are so rich that under the covers, PHP can do operations very efficiently, relying on interfaces to hide the implementation details.
Enhancements:
- Automatic reload of Studs configuration file if changed [Studs]
- improved handling of DTD validation for web.xml and struts-config.xml
- get_qualified_class() migrated to Clazz::getQualifiedName() and optimized [Horizon]
- umask() behaves consistently, globally setting the file create permissions [General]
- confirmed that the ternary operator works in EL and documented it [Phase]
- throw exception if web.xml cannot be read in the include path [Stratus]
- it is possible to eliminate index.php from URL and use mod_rewrite instead [Stratus]
- modified EL processing so that arrays can be referenced as foo.bar or foo[bar] so that cases where native arrays are used in place of HashMap will still comply with JSTL EL syntax [Phase]
- changed from Hashtable to HashMap across application [General]
- changes are detected in the Studs config files (struts-config.xml) and the ActionServlet is automatically reloaded if their timestamps have been modified [Studs]
- fixed bug in Assert that caused assertFalse() to fail [Horizon]
- reimplemented the phase string taglib [Phase]
- fixed token handling in form taglib so that now they are usable [Studs]
- redirect taglib can take url as body [Phase]
- enabled more flexibility in specifying configuration directories [General]
- halt with better message when servlet work directory is not writable [Stratus]
- enabled handling of multivalued paramaters in Studs [Studs]
- added HtmlCheckboxTag and HtmlPasswordTag [Studs]
- ActionForm generator [Studs]

Etcsvn is a command line program for managing system configurations in subversion. Etcsvn doesnt make a working copy out of your /etc, but uses a temporary workspace. Etcsvn will preserve ownership/permissions of the files being tracked.
Suppose you want to keep track of important config files on a system in a subversion repository. There are a few problems with using svn directly. One problem is that you need to keep track of ownership and permission modes of files and directories that you are tracking. It is somewhat difficult to manage the repository without access to a working copy, but a working copy is twice as big as what it works on. Also there is the possibility that you want to track some files in /var or somewhere else.
Etcsvn tries to provide a simple command line interface to manage files on you system. What it does is make a temporary working copy on the system. Etcsvn must be run as root, and it sets a umask of 077 before creating any file or directory. This makes the working copy as secure as possible. This is also true when restoring files, as the ownership and permissions are set after the file is created.
I am trying to make etcsvn a bridge between your system and the working copy. The goal is to provide only what is necessary to aid a system admin in being able to edit system configuration files in a convenient manner with tools that may not be available on the system your configuring.
Version restrictions:
- I am currently working on getting etcsvn to handle symbolic links. I am also adding an option to track directories recursively.
- There is no revision support yet.
- There is should be a little work done on the repository layout. It should be possible to place many systems in one repository, or have separate repositories for clients, networks, etc.
- Etcsvn makes no attempt to authenticate to your repository. This will probably not change anytime soon, because I feel that it should be the job of the script or administrator to handle this.
- Currently there needs to be a ini style config file in the root of your repository named "etcsvn.conf". There is only one section used in this file currently, and it is called "main". In the "main" section there is only one option supported, and it is called "files". The "files" option is a list of absolute path files separated with newlines.

ntfs-3g driver is an open source, GPL licensed, third generation Linux NTFS driver for 32-bit, little-endian architectures which was implemented by the Linux-NTFS project. It provides full read-write access to NTFS, excluding access to encrypted files, writing compressed files, changing file ownership, access right.

Technically its based on and a major improvement to the third generation Linux NTFS driver, ntfsmount. The improvements includes functionality, quality and performance enhancements.

The driver currently is in BETA status: before release of this software we havent experienced any driver crashes or data loss during our heavy quality testing, however we are aware of some minor issues which will be resolved in the near future. We listed all of them in a below section.

Installation:

Make sure you have the basic Linux development tools and FUSE (http://fuse.sourceforge.net) is correctly installed on your computer then type:

./configure
make
make install # or sudo make install if you arent root.

Usage:

If there was no error during installation then you can mount NTFS volumes for read-write access (unmount them if they were already mounted by another NTFS driver.)

ntfs-3g /dev/hda1 /mnt/windows

If you want to give full access for all users, ignore permission related driver messages, and make national characters visible then use (drop or replace the below hu_HU.utf8 with the appropriate setting, and also the device and mount points, if needed).

ntfs-3g /dev/hda1 /mnt/windows -o silent,umask=0,locale=hu_HU.utf8

Please see the ntfs-3g manual page for more options and examples.

You can also make NTFS to be mounted during boot by ensuring that the FUSE kernel module is automatically loaded and by putting the below line into /etc/fstab

/dev/hda1 /mnt/windows ntfs-3g silent,umask=0,locale=hu_HU.utf8 0 0