[go: up one dir, main page]

Menu

Tree [be923c] 0.7.0 /
 History

HTTPS access


File Date Author Commit
 doc 2014-07-05 Christian Ferrari Christian Ferrari [f845ca] Documented Use Case 17
 etc 2014-06-23 Christian Ferrari Christian Ferrari [7b15d3] Implementing resource idle lifespan
 man 2014-07-02 Christian Ferrari Christian Ferrari [bbc2d5] Fixed a bug related to incubator; intermediate ...
 src 2014-07-21 Christian Ferrari Christian Ferrari [187516] Hierarchical resource bug fixed, restarting tes...
 tests 2014-07-21 Christian Ferrari Christian Ferrari [187516] Hierarchical resource bug fixed, restarting tes...
 AUTHORS 2013-12-19 Christian Ferrari Christian Ferrari [10a33d] Code clean-up
 COPYING 2013-09-25 Christian Ferrari Christian Ferrari [72edf4] work in progress...
 ChangeLog 2014-07-22 Christian Ferrari Christian Ferrari [be923c] 0.7.0 release commit
 INSTALL 2013-09-25 Christian Ferrari Christian Ferrari [72edf4] work in progress...
 Makefile.am 2014-01-08 Christian Ferrari Christian Ferrari [691900] Adding autotest test suite...
 Makefile.in 2014-06-23 Christian Ferrari Christian Ferrari [7b15d3] Implementing resource idle lifespan
 NEWS 2013-09-25 Christian Ferrari Christian Ferrari [72edf4] work in progress...
 README 2014-07-21 Christian Ferrari Christian Ferrari [187516] Hierarchical resource bug fixed, restarting tes...
 TODO 2014-07-21 Christian Ferrari Christian Ferrari [187516] Hierarchical resource bug fixed, restarting tes...
 aclocal.m4 2014-05-02 Christian Ferrari Christian Ferrari [f14bfe] Introduced minimum glib2 level to 2.22
 config.h.in 2014-06-23 Christian Ferrari Christian Ferrari [7b15d3] Implementing resource idle lifespan
 configure 2014-07-22 Christian Ferrari Christian Ferrari [be923c] 0.7.0 release commit
 configure.ac 2014-07-22 Christian Ferrari Christian Ferrari [be923c] 0.7.0 release commit
 depcomp 2013-09-25 Christian Ferrari Christian Ferrari [72edf4] work in progress...
 doxygen.conf.in 2013-12-29 Christian Ferrari Christian Ferrari [a7952a] Implementing config files...
 install-sh 2013-09-25 Christian Ferrari Christian Ferrari [72edf4] work in progress...
 missing 2013-09-25 Christian Ferrari Christian Ferrari [72edf4] work in progress...
 valgrind.cmd 2014-07-09 Christian Ferrari Christian Ferrari [48a2e2] Intermediate commit
 valgrind.supp 2014-02-05 Christian Ferrari Christian Ferrari [264baa] Implementing IPV4 unicast connection

Read Me

	FLOM, Free LOck Manager, a free and open source lock manager

FLOM (Free LOck Manager) is an open source and free lock manager designed to
serialize ans synchronize shell command execution.

A list of well known use cases are listed at this URL: 
http://sourceforge.net/p/flom/wiki/FLOM%20by%20examples/
This is a brief list of the available features:
- synchronization of shell commands to avoid conflicts on files, directories,
  abstract resources
- enforcement of command order execution to avoid one command is executed
  before another one
- resource utilization leveling to avoid too many similar tasks run at the
  same time 
- all the synchronization features are available inside a single host or in
  a distributed environment using TCP/IP networking
- an autodiscovery feature is available to reduce deployment complexity in a
  distributed environment (every node at any time may become a "server" for
  the others node)

 * FLOM is free software: you can redistribute it and/or modify under the terms
 * of GNU General Public License version 2 as published by the Free Software
 * Foundation.
 *
 * FLOM is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
 * GNU General Public License for more details.

Install FLOM using standard GNU build chain: 
tar xvzf flom-X.Y.Z.tar.gz
cd flom-X.Y.Z
./configure
make
sudo make install
refer to INSTALL file for more details.

Use 
man flom 
to read man page and pick up Internet relevant URLs for FLOM project.

Use
make check
to perform package automatic tests.
NOTE: do *NOT* run tests on a system that's using flom because some tests
      need to kill all flom running instances and this is not acceptable if
      you are playing production workloads. DO USE A TEST SYSTEM!
NOTE: tests needs the system is NOT overloaded because they stick on timing
      and timing breaks if the system is overloaded.

If you need some help (usage tricks, hints, etc...) please post a message in
the forum: http://sourceforge.net/p/flom/discussion/
If you think you have discovered a bug, please open a ticket here:
http://sourceforge.net/p/flom/tickets/
If you avoided to send me an e-mail I would be happy: forum posts and tickets
can be seen by many people and I should not answer the same questions many
times.

Enjoy flom!
Ch.F.