#3860: Snoopy (command logger) and Trac
--------------------------------------------+-------------------------------
Reporter: vamancini [ at ] sbcglobal.net | Owner: jonas
Type: defect | Status: new
Priority: low | Milestone:
Component: general | Version: none
Severity: minor | Keywords:
--------------------------------------------+-------------------------------
I'm not sure if this should be a bug/defect, but it is definitely worth
noting that snoopy and trac do not like each other. What snoopy is (from
[http://sourceforge.net/project/showfiles.php?group_id=9226]):
{{{
Snoopy is designed to aid the task of a sysadmin by providing
a log of commands executed. Snoopy is completely transparent to
the user and applications. It is linked into programs to provide
a wrapper around calls to execve(). Logging is done via syslogd.
}}}
For one of our websites at DePaul University, we have apache 2.0.55,
python 2.3.5, trac 0.9.6, and debian sarge (kernel 2.4.x). By adding
snoopy, trac would fail. In the apache logs, one can see that every time
an attempt was made to access trac, an apache child process would produce
a segmentation fault similar to this:
{{{
[Sun Oct 01 02:06:55 2006] [notice] child pid 14810 exit signal
Segmentation fault (11)
}}}
Running trac-admin stand-alone while snoopy was running also produced
segmentation faults. Once snoopy was removed and apache restarted, trac
started to work again. This is easily reproducible.
Thanks,[[BR]]
Vince
--
Ticket URL: <http://trac.edgewall.org/ticket/3860>
The Trac Project <http://trac.edgewall.org/>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---
--------------------------------------------+-------------------------------
Reporter: vamancini [ at ] sbcglobal.net | Owner: jonas
Type: defect | Status: new
Priority: low | Milestone:
Component: general | Version: none
Severity: minor | Keywords:
--------------------------------------------+-------------------------------
I'm not sure if this should be a bug/defect, but it is definitely worth
noting that snoopy and trac do not like each other. What snoopy is (from
[http://sourceforge.net/project/showfiles.php?group_id=9226]):
{{{
Snoopy is designed to aid the task of a sysadmin by providing
a log of commands executed. Snoopy is completely transparent to
the user and applications. It is linked into programs to provide
a wrapper around calls to execve(). Logging is done via syslogd.
}}}
For one of our websites at DePaul University, we have apache 2.0.55,
python 2.3.5, trac 0.9.6, and debian sarge (kernel 2.4.x). By adding
snoopy, trac would fail. In the apache logs, one can see that every time
an attempt was made to access trac, an apache child process would produce
a segmentation fault similar to this:
{{{
[Sun Oct 01 02:06:55 2006] [notice] child pid 14810 exit signal
Segmentation fault (11)
}}}
Running trac-admin stand-alone while snoopy was running also produced
segmentation faults. Once snoopy was removed and apache restarted, trac
started to work again. This is easily reproducible.
Thanks,[[BR]]
Vince
--
Ticket URL: <http://trac.edgewall.org/ticket/3860>
The Trac Project <http://trac.edgewall.org/>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac Tickets" group.
To post to this group, send email to trac-tickets@googlegroups.com
To unsubscribe from this group, send email to trac-tickets-unsubscribe@googlegroups.com
For more options, visit this group at http://groups.google.se/group/trac-tickets
-~----------~----~----~----~------~----~------~--~---