[Back]

Warpcron Features

this makes Warpcron unique

general:
Warpcron...
  • is texmode only
    This means its very small and fast and needs very low ressources
    f.g. nearly no CPU-Time
  • is configurable by an ASCII configuration file
    no problem to configure it with any editor in textmode
  • has a nice graphical configuration program, WarpcronSetup
    with which you can very easy create your events and configure your Warpcron.
    If you change something while Warpcron is active, Warpcron recognize the change and rereads the config automatically.
  • is a native, 32 Bit OS/2 program
    and uses native OS/2 functions for many things, there's no overhead for starting programs
  • can start every type of program
    OS/2 texmode, PM, DOS, ... window or fullscreen, detached or minimized, even WPS objects can be scheduled!
  • writes a comprehensive logfile
    ...to save it activities so that you can control what happened when
    The logfile is in "Binkley"-Style, so that you can use external logfile viewers
  • keeps you informed via email
    It notifies you when something happened, like an error, a trap, starting or ending. And it can send you the logfile of today via email, every day.
    So you know everyday what happened last day.
  • uses a configurable email program to send emails, f.g. warpmail or sendmail
  • can say a "hello" to its logfile in configurable time intervals
    So you can control if everythings runs fine on a remote machine
  • one event can kill another event
    If you want to make sure that a started event terminates sometime, another event can kill it.
  • can display notes on your wps
    like those yellow sticky notes
  • supports for 4os2 .btm files
  • searches files like its config or event datetime-lists in current directory or /etc
  • you can edit the config right out of a running warpcron
  • can be end itself when a specific file (semaphore) exists
  • writes its PID to a file
  • has a leveled debug mode which writes debug messages to stderr
  • can shutdown your OS/2 at end
    and can kill programs before Shutdown, so that OS/2 doesn't ask if it should terminate program XXX and block shutdown...
Events can...
  • start a program
    WPS-Objects OS/2 Textmode window or fullscreen, minimized or not
    OS/2 PM OS/2 detached DOS window or fullscreen
    Windows (is nothing else than DOS ;-) )
  • a program can be .exe, .cmd, .bat or .btm (4os2)
  • kill another event's program
  • be a note, stored in a textfile, which is displayed onto the wps
  • be unforgettable
    Warpcron saves next datetime of unforgettable events to a file when ending and reads this file at startup. When there's an event which time is past, warpcron starts it.
  • a start can be written to logfile or not
Scheduling
An event can be started...
  • on a specific time on a specific date
  • on a specific time every day
  • on a specific time every X days or X Months
  • every day every X minutes or X hours
  • every month on the last day of this month
  • when a specific file is present or a file mask with wildcards is true (=start by file semaphore)
    when on a specific file, warpcron can delete this file after starting the event when started by a semaphore, it can wait X minutes until the event really starts
  • on a list of date-times
    a textfile with a date and a time on every line
  • at startup of warpcron
  • at end of warpcron
An event can be denied from being started...
  • on specific weekdays
  • in a time interval (from one time until another)
  • when a specific file is present or a file mask with wildcards is true


Author: Julian Buss


and the famous editor MEd!