Posted in
The two attributes vacationBegin and vacationEnd were defined as strings, because it was assumed, that users would want to specify vacation messages like "... back on Friday" and because LDAP did not provide a comparable date type.
In order to toggle vacation status based on a free style string, GNARWL would not only need to be able to parse strings such as:
- 13.01.01
- 01.13.01
- 01.13.2002
- 26.25.1234
- 01/01/03
- 14. Jun, 2004
- July the 14th
- Montag
- Tomorow
- Christmas
but also somehow deal with completely garbled user input. Support for this kind of thing will never be added, nor will patches for a parsing a specific datestring be accepted. If you absolutely need this kind of feature, you have to define a schema of your own, that defines timestamps for the two end dates and make CRON rewrite the gnarwl.cfg file once a day.