-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, 20 Oct 2004, Laszlo 'GCS' Boszormenyi wrote:
* Nelson A. de Oliveira [EMAIL PROTECTED] [2004-10-04 18:40:53 -0300]:
Laszlo, it´s OK. You may take the package. I saw it and it´s good. ;-)
Well, if you need something and I could help you, please, you contact me,
OK?
I forgot to ask you what's good. The packaging or the way it works (if
it even works for you)? What do you miss from it?
Hi
Sorry for taking a long time to answer. I was travelling.
Well, just one thing to correct on your package (I only saw this):
Epylog should also depends on libxml2-python2.3
Depends: python2.3, libxml2-python2.3
Installing tha package and withou having libxml2-python2.3 installed gives
an error about not loading a XML module.
Also, I installed the package at a test machine. It´ s giving error.
[EMAIL PROTECTED]:~# epylog
Invoking: Initializing epylog...
Could not init logfile for entry /var/log/secure[.#]
Could not init logfile for entry /var/log/maillog[.#]
Could not init logfile for entry /var/log/secure[.#]
Could not init logfile for entry /var/log/secure[.#]
Could not init logfile for entry /var/log/maillog[.#]
Could not init logfile for entry /var/log/maillog[.#]
Module Mail Report disabled
(Hanging from Initializing epylog)done
Invoking: Restoring log offsets...
Restoring log offsets...done
Invoking the module execution routines:
Invoking: Processing internal modules...
/var/log/messages[.#]: [ 13 of 77 lines parsed ]
Telling all threads to quit
Waiting for threads to finish: [ all threads done ]
Invoking: Finished all matching, now finalizing...
Invoking: Finalizing Logins...
Finalizing Logins...done
Invoking: Finalizing Packet Filter...
Finalizing Packet Filter...done
Invoking: Finalizing Notices...
Finalizing Notices...done
Invoking: Finalizing Weedeater...
Finalizing Weedeater...done
(Hanging from Finished all matching, now finalizing)done
(Hanging from Processing internal modules)done
Finished processing modules
Invoking: Making the report...
Making the report...done
Invoking: Publishing the report...
Traceback (most recent call last):
File /usr/sbin/epylog, line 300, in ?
main(sys.argv)
File /usr/sbin/epylog, line 284, in main
epylog.publish_report()
File /usr/lib/python2.3/site-packages/epylog/__init__.py, line 369, in
publish_report
self.report.publish(rawfh, unparsed)
File /usr/lib/python2.3/site-packages/epylog/report.py, line 245, in
publish
rawfh)
File /usr/lib/python2.3/site-packages/epylog/publishers.py, line 296,
in publish
self._mk_html_nologs()
File /usr/lib/python2.3/site-packages/epylog/publishers.py, line 450,
in _mk_html_nologs
alt_mw.startmultipartbody('alternative')
File /usr/lib/python2.3/MimeWriter.py, line 153, in startmultipartbody
self._boundary = boundary or mimetools.choose_boundary()
File /usr/lib/python2.3/mimetools.py, line 130, in choose_boundary
hostid = socket.gethostbyname(socket.gethostname())
socket.gaierror: (-2, 'Name or service not known')
[EMAIL PROTECTED]:~#
It is looking an error from Python 2.3
Take a look here:
http://mail.python.org/pipermail/python-bugs-list/2003-September/020458.html
So, I could not test Epylog... :-/
Thank you
Nelson
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: For info see http://quantumlab.net/pine_privacy_guard/
iD8DBQFBllB6AQwuptkwlkQRAkapAJwM8Fmaeekek8bAkBvPdzZ4//vzAQCdGjiS
4amePswLoE+4sQ26iUOeBNc=
=JtCx
-END PGP SIGNATURE-
