Sysop: | KK4QBN |
---|---|
Location: | Chatsworth, GA |
Users: | 48 |
Nodes: | 10 (0 / 10) |
Uptime: | 95:14:52 |
Calls: | 900 |
Calls today: | 0 |
Files: | 138,634 |
U/L today: |
0 files (0K bytes) |
D/L today: |
583 files (804M bytes) |
Messages: | 26,279 |
Posted today: | 1 |
This morning I see a file in inbound folder and it was not processed so I manually ran it and it processed. I thought tickit was supposed to run automatically when there was a file in the inbound folder.
This morning I see a file in inbound folder and it was not processed so I manually ran it and it processed. I thought tickit was supposed to run automatically when there was a file in the inbound folder.
If you're also using BinkIT, TickIT must be set up as a Timed Event with an internal code of 'TICKIT'.
This is true even if you don't intend to run TickIT on a schedule. BinkIT creates/updates the semaphore
file for that event as needed.
Zazz wrote to echicken <=-
This morning I see a file in inbound folder and it was not processed so I manually ran it and it processed. I thought tickit was supposed to run automatically when there was a file in the inbound folder.
If you're also using BinkIT, TickIT must be set up as a Timed Event with an internal code of 'TICKIT'.
This is true even if you don't intend to run TickIT on a schedule. BinkIT creates/updates the semaphore
file for that event as needed.
I am using BinkIT and so I went to scfg timed events and creaed
one for TickIT. So assuming I didn't botch it, it should run.
This morning I see a file in inbound folder and it was not processed so I manually ran it and it processed. I thought tickit was supposed to run automatically when there was a file in the inbound folder.
If you're also using BinkIT, TickIT must be set up as a Timed Event with an internal code of 'TICKIT'.
This is true even if you don't intend to run TickIT on a schedule.
BinkIT creates/updates the semaphore
file for that event as needed.
I am using BinkIT and so I went to scfg timed events and creaed
one for TickIT. So assuming I didn't botch it, it should run.
When in doubt, use the Wiki. When not in doubt, use the Wiki.
Right here it shows exactly how to set that event up:
http://wiki.synchro.net/module:tickit
Zazz wrote to Gamgee <=-
I am using BinkIT and so I went to scfg timed events and creaed
one for TickIT. So assuming I didn't botch it, it should run.
When in doubt, use the Wiki. When not in doubt, use the Wiki.
Right here it shows exactly how to set that event up:
http://wiki.synchro.net/module:tickit
Yes, thank you, I had that to use as a guide to setting up
Tickit. However, there was no timed event setup for Tickit and I
had to go to scfg to set that up. I entered info Timed event for
Tickit.
Is there a log where I can see what was processed or rejected? I
have not encountered one yet.
Well, I don't know if you are running on Linux or Windows... If
Windows I don't know. If Linux, we have to know if you're running
SBBS as a daemon/service or just starting it from a command line.
Tickit stuff will be in the same log as other stuff related to
Synchronet, perhaps /var/log/messages or /var/log/syslog. Can't
really say without more information...