First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 48468
Alias:
Product:
Component:
Status: RESOLVED
Resolution: TEST-REQUEST
Assigned To: Netmon Herd <netmon@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Robert Varga <nite@hq.alert.sk>
Add CC:
CC:
Remove selected CCs
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
sdsc-syslog-1.0.2.ebuild Initial ebuild text/plain Robert Varga 2004-04-20 08:35 0000 1.32 KB Details
sdscsyslogd Initscript, tested for some time text/plain Robert Varga 2004-05-07 05:37 0000 823 bytes Details
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 48468 depends on: 48467 Show dependency tree
Bug 48468 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug

Description:   Opened: 2004-04-20 08:34 0000 
This package is the SDSC syslog daemon, from
http://security.sdsc.edu/software/sdsc-syslog/

This syslog daemon supports RFC3080/RFC3081-style logging (syslog-reliable,
syslog-signed). Also it supports COOKED mode, which logs messages into easily
parsable XML format (to disk or over TCP).

For remote cooked mode, it depends on RoadRunner BEEP library (submitted as bud
#48467). I would suggest app-admin/sdsc-syslog for this ebuild.

------- Comment #1 From Robert Varga 2004-04-20 08:35:18 0000 ------- 
Created an attachment (id=29702) [edit]
Initial ebuild

------- Comment #2 From Daniel Black 2004-04-23 16:35:20 0000 ------- 
Michael - interested? otherwise I'm thinking security@gentoo.org.

------- Comment #3 From Daniel Black 2004-05-06 18:14:13 0000 ------- 
Commited version. Good ebuild generally. A few dependancies where missing and
there was no need for a /usr/share/SDSCsyslog directory with only documents.

Any change of an init script for this please? Thanks Robert

------- Comment #4 From Robert Varga 2004-05-07 05:37:34 0000 ------- 
Created an attachment (id=30924) [edit]
Initscript, tested for some time

There is an issue with rapid stop/start, because it takes some time for the
syslog to exit. I do not yet know how to handle this cleanly...

------- Comment #5 From Davin Boling 2004-06-17 07:30:40 0000 ------- 
How long does sdsc-syslog take to exit in general? I suggest the following
mechanism:

1) Determine how long the "average" wait time is.
2) Determine an acceptable "max wait time" timeout in excess of this.
3) Change the initscript so that on exit, the process is checked for running
every X seconds. When the process is no longer present, the initscript exits
successfully. If our timeout is exceeded, initscript fails.

I'll install this ebuild and try something along the lines of what I described,
and report my results.
First Last Prev Next    No search results available      Search page      Enter new bug