TIP: Click on subject to list as thread! ANSI
echo: 4dos
to: ALL
from: mark lewis
date: 2003-11-12 11:57:58
subject: dayboot1 question

Path: internal1.nntp.ash.giganews.com!border2.nntp.ash.giganews.com!border1.nntp.ash.giganews.com!firehose2!nntp4!intern1.nntp.aus1.giganews.com!border1.nntp.aus1.giganews.com!nntp.giganews.com!newsfeed.tpinternet.pl!news.atman.pl!news.intercom.pl!f124.n480!f127.n480!f112.n480!f200.n2432!f605.n774!f500.n123!f2000.n106!f12.n3634!not-for-mail
Newsgroups: fido.4dos
Distribution: fido
From: mark lewis 
Date: Wed, 12 Nov 03 11:57:58 +0100
Subject: dayboot1 question
Message-ID: 
 2443/1181
Lines: 12
Xref: intern1.nntp.aus1.giganews.com fido.4dos:443

can dayboot handle running items on specific dates or as soon after that date?
the concept of running every X days is ok for some things but if i need
something run on the 25th, i can't just say +30 for the days between runs as it
wouldn't always run /on/ the 25th...

i'm not yet actively using dayboot in a production environment because i'm
needing this one capability... the main thing is that if the machine is locked
up on the 24th and doesn't get unstuck until the 26th, that task for the 25th
must still run...

)\/(ark

SOURCE: echoes via archive.org

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.