Bugs item #853711, was opened at 2003-12-03 16:24 Message generated for change (Comment added) made by nobody You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=432066&aid=853711&group_id=42081
Category: Interface (example) Group: None Status: Open Resolution: None Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Nobody/Anonymous (nobody) Summary: Alarm no longer works in 3.1.8.0 Initial Comment: I tried "alarm 23:58" and "alarm 00:24" - both times I was told that my timestamp could not be read. ([EMAIL PROTECTED]) ---------------------------------------------------------------------- Comment By: Nobody/Anonymous (nobody) Date: 2003-12-08 08:42 Message: Logged In: NO Thanks - that did the trick! ---------------------------------------------------------------------- Comment By: Kim Gr�sman (kimgrasman) Date: 2003-12-04 00:48 Message: Logged In: YES user_id=551308 Hi, Something changed in the alarm logic, so it now requires a message. We'll probably change this back for the final release (unless I'm missing some subtle point on why it works this way), but in the meantime you can just put in a bogus message, to make it work: alarm 23:58 . alarm 00:24 zzz Hope that helps. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=432066&aid=853711&group_id=42081 ------------------------------------------------------- This SF.net email is sponsored by: IBM Linux Tutorials. Become an expert in LINUX or just sharpen your skills. Sign up for IBM's Free Linux Tutorials. Learn everything from the bash shell to sys admin. Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click _______________________________________________ DQSD-Devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dqsd-devel
