bravisimo
04-24-2007, 02:40 AM
Hello people..
Now, i've been searching for an answer for this for a few hours, and i've tried a few things.. but it seems my AlcoBot just wont announce no mather what i do..
- First thing.. yesterday it was working fine.. but after i started my box today, it just wont.
(I use ioFTPD 6.0.4, nxTools and AlcoBot 1.2.0)
[Sections]
# Channel sections
DEFAULT = "#xxx" "approve close credits request dir"
STAFF = "#xxx" "error login sysop wipe"
# Path Sections
TESTiNG = "/TESTiNG/" "#xxx" "!wipe all"
[09:36] [?AlcoBot?] Debug :: ModReadLogs - Received event: LOGIN (log: 0).
[09:36] [?AlcoBot?] Debug :: ModReadLogs - No variable definition for event, skipping announce.
[09:36] [?AlcoBot?] Debug :: ModReadLogs - Received event: LOGOUT (log: 0).
[09:36] [?AlcoBot?] Debug :: ModReadLogs - No variable definition for event, skipping announce.
this is all i get, and its on NEWDIR and so on too.. anyone got any idea what this might be caused by? thanks
EDIT: problem fixed.. seems the service didnt work properly when logged on with windows remote service... thanks anyway ppl :)
Now, i've been searching for an answer for this for a few hours, and i've tried a few things.. but it seems my AlcoBot just wont announce no mather what i do..
- First thing.. yesterday it was working fine.. but after i started my box today, it just wont.
(I use ioFTPD 6.0.4, nxTools and AlcoBot 1.2.0)
[Sections]
# Channel sections
DEFAULT = "#xxx" "approve close credits request dir"
STAFF = "#xxx" "error login sysop wipe"
# Path Sections
TESTiNG = "/TESTiNG/" "#xxx" "!wipe all"
[09:36] [?AlcoBot?] Debug :: ModReadLogs - Received event: LOGIN (log: 0).
[09:36] [?AlcoBot?] Debug :: ModReadLogs - No variable definition for event, skipping announce.
[09:36] [?AlcoBot?] Debug :: ModReadLogs - Received event: LOGOUT (log: 0).
[09:36] [?AlcoBot?] Debug :: ModReadLogs - No variable definition for event, skipping announce.
this is all i get, and its on NEWDIR and so on too.. anyone got any idea what this might be caused by? thanks
EDIT: problem fixed.. seems the service didnt work properly when logged on with windows remote service... thanks anyway ppl :)