Free batch file software for linux

ngbatch project is a newsgroup/rmgroups batcher for INN.

SYNOPSIS

< ngbatch -n > < group > [ < flag > [ < creator > ] ]

< ngbatch -r > < group >

< ngbatch -e > [ < -D > ] [ < -w > < days > ] [ < -h > < days > ]

This program executes newgroup and rmgroup controls in a delayed way, to help against newgroup/rmgroup wars. The idea is that (a) rmgroups are remembered for some time, and (b) rmgroups get priority over newgroups, so that a newgroup will be ignored if a rmgroup for this group (from a trusted issuer) has already arrived. A newgroup is executed only after a wait period, in case it gets rmgrouped soon.

Each newgroup/rmgroup control message is written into a batch file. A cron job collects commands from this batch file and executes only those newgroups for which no rmgroup was received.

Setting Up

Change your control scripts for newgroup and rmgroup so that they call B< ngbatch > with the appropriate parameters instead of B< ctlinnd > (you probably should make that depend on hierarchies). Make sure that only trusted rmgroupers are active in the I< control.ctl > file.

Run < ngbatch -e > periodically from crontab.

OPTIONS

< -n > < group > [ < flag > [ < creator > ] ]

Batch up a newgroup control for < group >. < flag > defaults to "y", < creator > defaults to nothing.

< -r > < group >

Batch up and execute a rmgroup control for < group >.

< -e >

Execute a batch run: for all batched newgroup commands, check if the wait time has elapsed. If yes, execute the newgroup command only if no rmgroup for the same group was batched. Rewrite the batch file with the commands still to be remembered.

< -D >

Show the commands on standard output instead of executing < ctlinnd >.

< -w> < days >

Set the newgroup wait time to < days > (default 3).

< -h > < days >

Set the rmgroup remember time to < days > (default 30).

Batch Download is a plugin for Firefox that makes downloading multiple images easy.

Like FlashGets batch download,but special designed for some image site!

You will find it very useful when you download some url like

http://www.google.com/1.jpg
http://www.google.com/2.jpg
http://www.google.com/3.jpg...

or some other urls like:

http://www.google.com/0102.jpg
http://www.google.com/0203.jpg
http://www.google.com/0304.jpg...

And also you can download all images in current page at once.

BatchSystem-SBS is a simple batch system.

SYNOPSIS

a short example

#edit examples/sbsconfig-examples-1.xml to put your own local machines (it can be a good idea, if you have not a cluster, to enter your local machine with different addresses (localhost, 123.156.78.90, hostname) to see sommething a bit more realistic...

#System status #in a side term, to see every second the watch -n 1 ../scripts/sbs-scheduler-print.pl --config=sbsconfig-examples-1.xml

#to submit or dozen or so scripts on queue single
../scripts/sbs-batch-submit.pl --config=sbsconfig-examples-1.xml --queue=single --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh

#and on a higher priority queue
../scripts/sbs-batch-submit.pl --config=sbsconfig-examples-1.xml --queue=single_high --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh --command=a.sh

#to update
../scripts/sbs-scheduler-update.pl --config=sbsconfig-examples-1.xml

#to check data consistency (and solve main problems
../scripts/sbs-scheduler-check.pl

#to remove a job --config=sbsconfig-examples-1.xml
../scripts/sbs-batch-remove --config=sbsconfig-examples-1.xml yourjobid

submiting command

You can submit either comman or scripts.

Script submited on a resource of type machine will be sshed on the host

Once a resource is attributed to a job, the script is transformed, changing the following varaibles (see examples/*.sh)

$(machinefile} (for cluster type resource) ${nbmachines} (for cluster type resource) ${host} (for machine type resource) ${jobid}

At submition time, a directory with the job number (incremented integer) is created, where stdout/err will be written.

There will also have a batch.properties file (pids, start time etc. etc.)

Download Machine provides a noninteractive, nongraphical, pure Java batch file downloader.
Download Machine is pure Java daemon that watches queue files for changes. If a new entry is available, DM will download it. Queue files are just URL lists. DM fully supports the HTTP, FSP, and FTP protocols.
Main features:
- Design goals
- Non graphical
- Non interactive
- Relieable downloads
- Queued downloads
- Portability (uses Java)
- Simple to use
- Resume interrupted downloads
- Transports
- Support for HTTP/1.1 protocol
- Support for HTTP/1.0 protocol
- Support for FTP protocol
- Support for FSP protocol
- Custom headers
- Fake user-agent header
- Custom referer header, configurable per URL
- Custom cookie header, configurable per URL
- Other features
- Can check in different directories if we already have downloaded file (configurable by wildcard)
- Can move downloaded file to special directory (configurable by wildcard)

bnrt is 2 programs, a client and a server, that help render frames of animations over a network using multiple computers that all have Blender, a popular opensource 3D modeler/renderer, on them.

bnrt can run on Linux, Windows, and any other environment supported by both Java and Blender. Currently it is only set up to run on Linux and Windows, since those are the OSs I have running and active at the moment. But it is pretty trivial for me to add more OSs as long as they are supported by both Java and Blender.

To use bnrt you need to run the server on each system that you want to render frames on. This is done by either running the server shellscript or batch file. Or you can even just type in java -jar bnrtServer.jar at the command line.

After you have started a server on each system, then you need to run the client, which does not do any rendering. You can run a server and a client on the same machine. To run the client you need to run the following command from a command line:

java -jar bnrtClient.jar {file to render.blend} {first frame} {last frame} {server1} {server2} {server3....}

Please note that at the moment this is still pretty alpha code. I use it on my own network with up to 5 machines, mixed Windows and Linux as well as various processors, and it works quite well for me. YMMV, but if you run into a problem I will be happy to try to help you out as much as possible.

File::Repl is a Perl module that provides file replication utilities.

SYNOPSIS

use File::Repl;

%con = {
dira => C:/perl,
dirb => M:/perl,
verbose => 1,
age => 10,
};

$ref=File::Repl->New(%con);
$r1 = $ref->Update(.p(l|m),ab,1);
$r2 = $ref->Update(.t.*,ab,1,.tmp$);

The File:Repl provides simple file replication and management utilities. Its main functions are

File Replication

Allowing two directory structures to be maintained, ensuring files that meet selection logic criteria are mirrored and otherwise synchronized.

Bulk Renaming

Allowing files in a directory structure to be renamed according to the selection logic.

Compressing

Allowing files in a directory structure to be compressed according to a given logic.

Process

Run a common perl process against files in a directory structure according to selection logic.

Deletion

Allowing files in a directory structure to be deleted according to the selection logic.

Zenith Picture Gallery is a feature-rich picture gallery that organizes uploaded images into searchable categories, creates thumbnails, and stores individual statistics for each one.
Other features of Zenith Picture Gallery include downloadable categories and sub-categories, user accounts and profiles, batch adding via FTP and batch deleting, user comments and ratings, the ability to add languages and skins, the option to rebuild thumbnails, an IP blacklist, and a comprehensive admin control panel that provides access to a great deal of settings and formatting options.
Main features:
- Everything is done from the browser, from installation to configuration.
- Searcheable records by filters.
- Auto-resizing/resampling of images to thumbnails.
- Easy skinning.
- Categories and sub-categories with display permission options.
- User accounts, user profiles, control panels and user types.
- Easy management of languages.
- Blacklist containing IPs of troublesome users.
- Admin CP allows you to define countless settings and formatting options.
- A notice appears in the nav bar to admins when there are pictures, comments or users awaiting approval.
- Batch add pictures via FTP.
- Batch delete pictures.
- Rebuild thumbnails tool.
- Search result and display page addresses are linkable.
- Gallery can be turned on/off.
- Adding pictures can be disabled for guests.
- Sort pictures by Last comments, Most viewed, Top rated.
- ZIP and download pictures.
- User accounts, profiles and pictures can all be managed in the Admin CP.
- Option to receive an email when a picture is submitted.
- 21. Option to allow only registered users to view the gallery.
- 22. Option to set a timezone offset for picture submission dates.
- Categories are mapped to directories in the file structure.
- Users can choose a skin from the ones uploaded.
- Forgot my Password and Resend Activation Email tools.
- Admins can define custom fields for pictures.
- EXIF support.

File::chmod is a Perl module that implements symbolic and ls chmod modes.

SYNOPSIS

use File::chmod;

# chmod takes all three types
# these all do the same thing
chmod(0666,@files);
chmod("=rw",@files);
chmod("-rw-rw-rw-",@files);

# or

use File::chmod qw( symchmod lschmod );

chmod(0666,@files); # this is the normal chmod
symchmod("=rw",@files); # takes symbolic modes only
lschmod("-rw-rw-rw-",@files); # takes "ls" modes only

# more functions, read on to understand

File::chmod is a utility that allows you to bypass system calls or bit processing of a files permissions. It overloads the chmod() function with its own that gets an octal mode, a symbolic mode (see below), or an "ls" mode (see below). If you wish not to overload chmod(), you can export symchmod() and lschmod(), which take, respectively, a symbolic mode and an "ls" mode.
Symbolic modes are thoroughly described in your chmod(1) man page, but here are a few examples.

# NEW: if $UMASK is true, symchmod() applies a bit-mask found in $MASK

chmod("+x","file1","file2"); # overloaded chmod(), that is...
# turns on the execute bit for all users on those two files

chmod("o=,g-w","file1","file2");
# removes other permissions, and the write bit for group

chmod("=u","file1","file2");
# sets all bits to those in user

"ls" modes are the type produced on the left-hand side of an ls -l on a directory. Examples are:

chmod("-rwxr-xr-x","file1","file2");
# the 0755 setting; user has read-write-execute, group and others
# have read-execute priveleges

chmod("-rwsrws---","file1","file2");
# sets read-write-execute for user and group, none for others
# also sets set-uid and set-gid bits

The regular chmod() and lschmod() are absolute; that is, they are not appending to or subtracting from the current file mode. They set it, regardless of what it had been before. symchmod() is useful for allowing the modifying of a files permissions without having to run a system call or determining the files permissions, and then combining that with whatever bits are appropriate. It also operates separately on each file.

An added feature to version 0.30 is the $UMASK variable, explained below; if symchmod() is called and this variable is true, then the function uses the (also new) $MASK variable (which defaults to umask()) as a mask against the new mode. This is documented below more clearly.