Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 48468 - sdsc-syslog-1.0.2.ebuild (New Package)
Summary: sdsc-syslog-1.0.2.ebuild (New Package)
Status: RESOLVED TEST-REQUEST
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Gentoo Netmon project
URL:
Whiteboard:
Keywords: EBUILD
Depends on: 48467
Blocks:
  Show dependency tree
 
Reported: 2004-04-20 08:34 UTC by Robert Varga
Modified: 2004-06-17 07:30 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments
Initial ebuild (sdsc-syslog-1.0.2.ebuild,1.32 KB, text/plain)
2004-04-20 08:35 UTC, Robert Varga
Details
Initscript, tested for some time (sdscsyslogd,823 bytes, text/plain)
2004-05-07 05:37 UTC, Robert Varga
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Varga 2004-04-20 08:34:34 UTC
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 Robert Varga 2004-04-20 08:35:18 UTC
Created attachment 29702 [details]
Initial ebuild
Comment 2 Daniel Black (RETIRED) gentoo-dev 2004-04-23 16:35:20 UTC
Michael - interested? otherwise I'm thinking security@gentoo.org.
Comment 3 Daniel Black (RETIRED) gentoo-dev 2004-05-06 18:14:13 UTC
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 Robert Varga 2004-05-07 05:37:34 UTC
Created attachment 30924 [details]
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 Davin Boling 2004-06-17 07:30:40 UTC
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.