Code: Select all
[19:07] *** ChanServ sets mode: +v Ouija
[19:07] <Ouija> eu nao disse?
[19:07] <Ouija> tao a ver
[19:08] <troncao> LOOL
Code: Select all
[19:07] *** ChanServ sets mode: +v Ouija
[19:07] <Ouija> eu nao disse?
[19:07] <Ouija> tao a ver
[19:08] <troncao> LOOL
Well, if they look like this (i.e. time takes 7 sybols -> then space -> then nikname enclosed in <> -> then space -> then text) the module can convert it to html, but i think it'll not because if you are not using standart logs, i think then you not use statements "logfile", "logfile-suffix" and "keep-all-logs" in your eggdrop.conf file... and if you not using them then the module will be unable to find path to your logfiles, and to determine the format of your logfilenames.. that's why it'll not convert your logs..Thunderdome wrote:they are made in my case to be like mIRC logs.
Code: Select all
[19:07] *** ChanServ sets mode: +v Ouija [19:07] <Ouija> eu nao disse? [19:07] <Ouija> tao a ver [19:08] <troncao> LOOL
Only 1 log per channel? you want to say that there is no separate log for every day? this case module'll not convert files..Thunderdome wrote:I am now using besise the mel logs, the eggdrop default logs... but I put stuff so there is only 1 log per channel.
Will logs2html accept this?
But somehow it is not working... No pages are built!
Code: Select all
#channel.log.25Jul2005
Code: Select all
#channel.log.25072005
Code: Select all
Can't load modules logs2html: Shared object "libc.so.6" not found, required by "logs2html.so"
how in that file it separate by days?Thunderdome wrote: It would be cool if it worked with just one file, but probably impossible right?
well look: output file (generated page) will have format "channel20050725.html".. i.e. channel+year+month+day...Thunderdome wrote: And can the logs be like
Code:
#channel.log.25Jul2005
or must they be:
Code:
#channel.log.25072005
?
I ask this because of the filenames in your site that has the logs.
okay. )well look: output file (generated page) will have format "channel20050725.html".. i.e. channel+year+month+day...
but your logfile may have any format you like.. you wrote your preffered format in tcl variable "logfile-suffix".
Code: Select all
Can't load modules logs2html: Shared object "libc.so.6" not found, required by "logs2html.so"
i mean how does it separate inside file? what chars using for this?Thunderdome wrote:"how in that file it separate by days? " - hum, pisg seems to see the days... maybe the irc log style adds the days and the eggdrop style does not?
i found this:Thunderdome wrote:and what about this?Code: Select all
Can't load modules logs2html: Shared object "libc.so.6" not found, required by "logs2html.so"
well.. i'm thinking...You probably know that libc is the library that includes all the standard C commands (such as printf, read, open, etc.and so on) as well as system calls. Up until 1997, the only library available was the GNU libc v1, which since the move to ELF binary format was given major number 5 (/lib/libc.so.5). In 1997, the Free Software Foundation developed GNU libc v2, with the intention of being cleaner, more portable, and more standard (POSIX compliant). Under Linux, this version got major number 6, hence it's called libc6. These two libraries are incompatible -- if a program is compiled with one libc's headers and stubs, it can't be used with the other. Some of the distributions (RedHat since version 5, Debian since 2, SuSE since 6, and Slackware since 4) have moved to libc6 (meaning that most binaries are compiled with libc6, and the development environment contains libc6 headers and produces programs that work only with libc6). The distributions still contain libc5, as well as other libraries that are linked with libc5, in order to run libc5 binaries, which will usually be programs where the source is not available (such as Quake, etc). The problem is that if a user of the system wants to use a new version of one of thoese libraries, s/he can't compile them, because only libc6 programs or libraries can be produced.
I think you are not right.. i'm very weak in unix-like systems, but if for example you use system with kernel 2.4, and try to install on it device driver written for system with kernel 2.6 or vice versa - I think you may fall.. will you write in this case to the producer of driver, what in its driver terrible bug?iamdeath wrote:I think this version has bugs and the written of module should wakeup and fix them..
peace