Summary: | socklog-0.9.1.ebuild (New package) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Stoyan Zhekov (RETIRED) <zhware> |
Component: | New packages | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | RESOLVED FIXED | ||
Severity: | enhancement | ||
Priority: | Highest | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
socklog.tar.gz (New package socklog-0.9.1.ebuild)
socklog control file socklog-0.10.0.ebuild |
Description
Stoyan Zhekov (RETIRED)
2002-07-10 03:05:29 UTC
Created attachment 2101 [details]
socklog.tar.gz (New package socklog-0.9.1.ebuild)
Created attachment 2381 [details]
socklog control file
Please use the attached socklogctl file instead of files/socklogctl from
the submitted before tarball.
This socklogctl check if the /dev/log and /dev/klog devices present before
starting services - sometimes /dev/klog does not present in the user-mode
linux.
Sorry, forgot about previous my post - better is to use the file from the submitted tarball. Sorry again :( Hey guys, I'm waiting already 15 days for approving :( So for this time new version of package is released - socklog-0.10.0 The new .tar.bz2 attachement include ebuild for this version. Also I finally find the reason for for confusion in the previous posts about klog device. So from the socklog package pages: "read kernel messages from /proc/kmsg on Linux, or /dev/klog on BSD" The socklog-conf utility create by default /etc/socklog/klog/run script for running ON BSD! That's way it displayed error about non-existing device. I correct this in my control script (/usr/bin/socklogctl) with replacing (using sed) occurance of /dev/klog to /dev/kmsg in /etc/socklog/klog/run. The exact line from /usr/bin/socklogctl: if [ ${1} == "klog" ]; then KLOG="/etc/socklog/klog" sed -e 's:/dev/klog:/proc/kmsg:g' ${KLOG}/run > ${KLOG}/run.$$ \ && mv ${KLOG}/run.$$ ${KLOG}/run && chmod 755 ${KLOG}/run fi I hope this ebuild to be approved ASAP. P.S. How to upload the new tar file? Like a different bug? I tryed to add it with "Create a New Attachement" but it tell me that I'm not authorized. Regards, Stoyan Created attachment 2595 [details]
socklog-0.10.0.ebuild
I successed with uploading the tar.bz2 file. The authorization was forbidden only to obsolete the old tarball and control file. db fix db fix |