Summary: | The eciadsl-synch (net-dialup/globespan-adsl package ver. 0.10) leaves stale semaphore | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Arrigo Marchiori <ardovm> |
Component: | [OLD] Unspecified | Assignee: | Gentoo Dialup Developers <net-dialup> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Arrigo Marchiori
2005-12-07 15:03:18 UTC
does version 0.11 fix this? (In reply to comment #1) > does version 0.11 fix this? I don't know... I just emerged the `stable' version of the globespan-adsl package and found this problem. please try the 'unstable' version to see if it solves the problem. (In reply to comment #3) > please try the 'unstable' version to see if it solves the problem. I emerged version 0.11. eciadsl-synch now leaves no stale semaphores, but couples of shared memory areas! They can be listed with the command "ipcs -m". So the problem isn't fixed but kind of moved! :-\ I found another little bug in the latest version: the eciadsl-probe-synch, at line 81, incorrectly sets the BIN_DIR variable to "/usr/local/bin", while it should be "/usr/bin" let me get this straight. every time you run eciadsl-synch it creates a new shared memory zone? if you run for lets say 3 times, you end up with 3 new shared areas? (In reply to comment #5) > let me get this straight. every time you run eciadsl-synch it creates a new > shared memory zone? if you run for lets say 3 times, you end up with 3 new > shared areas? Actually 6 shared memory areas: 2 for each run. Please check if version 0.12 still has this problem. (In reply to comment #7) > Please check if version 0.12 still has this problem. Sorry, I switched to an ethernet modem right after I found this problem. Now I can't find the USB modem, so I can't check if the new driver works. :-( Anyway, I admire your dedication to this cause... I almost forgot I opened this bug in the end of 2005! It is on my open bug list, so it is hard to miss :) Closed with TEST-REQUEST resolution until someone having the hardware reopens it ... or confirms the problem is gone. |