Bug 48468

Summary:	sdsc-syslog-1.0.2.ebuild (New Package)
Product:	Gentoo Linux	Reporter:	Robert Varga <nite>
Component:	New packages	Assignee:	Gentoo Netmon project <netmon>
Status:	RESOLVED TEST-REQUEST
Severity:	enhancement	CC:	netmon, nite
Priority:	High	Keywords:	EBUILD
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---
Bug Depends on:	48467
Bug Blocks:
Attachments:	Initial ebuild Initscript, tested for some time

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.