Bug 203840 - Threshold and sigchld patch
Summary: Threshold and sigchld patch
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: swatch
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jose Pedro Oliveira
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-08-23 22:32 UTC by Orion Poplawski
Modified: 2007-11-30 22:11 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2007-10-17 19:51:05 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
patch from gentoo (3.37 KB, patch)
2006-09-05 21:51 UTC, Orion Poplawski 		no flags Details | Diff
View All

Description Orion Poplawski 2006-08-23 22:32:04 UTC 
Description of problem:

Time for a upgrade?  Just starting to look at swatch myself...
Comment 1 Jose Pedro Oliveira 2006-09-05 21:47:08 UTC 
Adding Gavin to the CC list.
Comment 2 Jose Pedro Oliveira 2006-09-05 21:51:00 UTC 
I have just updated the development branch to version 3.2.1.  Unfortunately the
building system appears to be broken at the moment.  I will build asap.
Comment 3 Orion Poplawski 2006-09-05 21:51:17 UTC 
Created attachment 135610 [details]
patch from gentoo

On the gentoo wiki there is a patch to add a threshold and proper sigchld
handling at: http://gentoo-wiki.com/HOWTO_Protect_SSHD_with_Swatch.  This is an
updated version for 3.2.1.  I haven't submitted upstream, as somewhat like the
gentoo wiki indicates, I'm not sure this doesn't break other stuff.
Comment 4 Gavin Henry 2006-09-06 07:11:25 UTC 
See what tests are t/* and maybe add one to check this change.

Gavin.
Comment 5 Jose Pedro Oliveira 2006-09-16 20:29:47 UTC 
I have built 3.2.1-1 for FC-5 (already available in the repos) and FC-4 (to be
available after the next push).
Comment 6 Orion Poplawski 2007-10-17 19:51:05 UTC 
Upstream: http://sourceforge.net/support/tracker.php?aid=1562324

Though upstream seems pretty dead.
Note You need to log in before you can comment on or make changes to this bug.