commit - c1244d9dc79a525fc0be990c931eefd1c8fd6a81
commit + 22b423a4d20e57704ecbbd27b2ffc2becde0fb40
blob - ff0ea7228a001196d512121544491fe9f8d61d33
blob + 4a81475dd3fe66d1d3df198951652cae9f6e1ae2
--- README.md
+++ README.md
@@ -1,6 +1,6 @@
 Auteur :       Vincent <vincent.delft@gmail.com>

 licence :      BSD

-version :      0.5

+version :      0.6

 Description :  Execute scheduled commands without assuming that the machine runs permanently

 Dependencies : Is is based on the BSD's date command. 

 Config file :  ~/.vdcron/vdcron.conf or /etc/vdcron.conf

@@ -23,7 +23,9 @@ What makes vdcron special? :

 - vdcron is not planned to run permanently as a daemon, but an external program will trigger Vdcron. It can be you normal cron, it can be your .profile script, it can be your .login script. In my case vdcron is triggered by the resume process of apmd. Thus each time I open the lid of my laptop, vdcron is triggered and execute commands that he must run. 

 - Since vdcron is not a daemon, the config file and the schedule are a little bit different from what we are used to use in cron programs. 

 

+vdcron has been developped on OpenBSD, but I've tested it on Debian and DragonFlyBSD 5.2.2

 

+

 # Optional parameters

 

 vdcron accept the following optional parameters: 

@@ -144,7 +146,7 @@ On a weekly basis (ideally on Friday), I sync my local
 # How to trigger vdcron ?

 

 As said, to my eyes, the ideal is to trigger the execution of vdcron at each lid's open of my laptop. 

-To do that I’ve added the following file in /etc/apm:

+To do that, on my openbsd machine, I’ve added the following file in /etc/apm:

 

 	cat /etc/apm/resume

 	#!/bin/sh