I notice that in the dialup script, wmnet is backgrounded, but not killed on hangup. Or so it seems, I don't know Flua. So if you dial up multiple times in a given dsl "session", you get multiple wmnets. Is that the intended idea?
I can happily kill the pids, but just want to know if thats how it's supposed to be.
Apologies if this is addressed somewhere else.This feature was requested from QA yet I never received any feedback and therefore assumed all is well. Your is the first feedback on this particular feature.
This suggests to me that maybe we should consider wider beta testing or even public beta testing. I see that some of the other distros now have public beta testing and some even make formal announcments that a public beta testing version will soon be forthcomming.
I am sure that there will be some who say that our release cycles are too often. Yet in reality the cycles have not changed in frequency for a very long time. Yet too, it is not too cool to have to issue a plus .0.0.1 bug fix release, as has been done that last couple of releases.
I also realise that my contributions to DSL has increased it flexibility tremendously and therefore its complexity resulting in quite a burden for formal QA testing. I even made a formal testing grid. Its size is intimidating and nearly impossible for anyone person to test every new feature against every possible install type. I also realize that the change logs for the last couple of releases have been quite large, again a burder to test everything in a timely manner. I had completed all the major features in this release on July 26 and had been waiting for feedback. This date was choosen for two reasons. One a full week had gone by, and two I wanted to release well before LinuxWord as I will be gone attending that event and not around to fix things or may not have readily available access to even resond in a timely manner. This is not to be construed as a complaint against those who currently help QA my pre-releases. Nor is this my excuse. It is only observations that I am public expressing.
The multiple wmet is not a show-stopper, as you have mentioned you can easily kill the pids of the left over wmnets.
Thanks for reporting.
If others want to weight in on the ideas expressed, please do.
RobertYou *do* release new versions quite often, though I have a hard time thinking of that as a bad thing. After all no one is forced to upgrade to a new version (though it's so easy that I expect most folks do upgrade).
Maybe the answer is, as you suggest, a public beta release system. Really no change in the way you release except for labeling. The current 1.x releases become 1.xBeta releases, followed in a week or so by an official release with or without fixes as needed. People who don't want to deal with problems can stay away from the beta releases.
I expect enough of us will pick up the beta releases to give your code a fairly complete test. This may also reduce the load on your QA folks.
- Tom
Quote (adraker @ Aug. 03 2005,22:48)
I can happily kill the pids, but just want to know if thats how it's supposed to be.
How do you kill these multiple wmnet pids? Im using DSL 1.4 on an old laptop with a 8.5 x 6.5 inch screen, i need all the screen room i can get and when i reconnect on dial up these multiple wmnet pids are taking it up.. (i sort of miss DSL 1.3 it didnt do this) anywayz.. how do i remove these pids? im new to linux (still learning) so i dunno how to do it.. Is it done in command line? as im writing this i have 4 wmnet pids stacked across this little screen from reconnecting at different times.. yipes is there a way to stop this from even happening? some edit somewhere?Opening a terminal and typing in "top" will list all process IDs.There is also a menu item to do this. I think it is in the "system" area. Then to kill a particular PID, you can enter kill -9 <PID>. Or simply open a terminal, and enter killall wmnet. This will kill every wmnet proc that is running.Next Page...
original here.
is there a way to stop this from even happening? some edit somewhere?