Thanks for your attention to this, Emil! I've attached the /etc/darkstat/init.cfg file (in the state it was when it generated the errors you noted above) as you requested. As an update to this bug/thread, I should say that I have been able to resolve this to the point of being able to completely remove darkstat via Synaptic. Here are a few details that may help any darkstat developers come up with a more user-friendly (read 'noob-friendly) package:
1. Came across darkstat program and decided to install it, as it looked like it could fit my needs. 2. As per instructions, opened the init.cfg file to change the START_DARKSTAT value from 'no' to 'yes'. Also made sure that the INTERFACE value matched my network device name. Tried to start it from the terminal, but couldn't get it to work (sorry, didn't make a note of the errors at the time). Went back into init.cfg file to see if I could figure out whether some of the other settings needed to be changed and what to change them to. In this step, I'm pretty sure the only thing I did was uncomment the PORT and DNS value lines, but if necessary the file could be compared with one on a fresh install of this version of darkstat to see if there were other differences. When I still couldn't start the program, I came up with an alternative way of doing the basic one-time monitoring I wanted to do. 3. Decided to completely remove darkstat (via Synaptic) to avoid unnecessary clutter, which is when the above errors were generated and I was prompted to report this here. 4. Since the initial bug report, I did some unrelated installs of other packages via the terminal and noticed some similar (but slightly different ) errors related to darkstat (presumably because it remained flagged for removal, but the removal always failed). Here are the relevant lines (my comments in [brackets]): 1 not fully installed or removed [in the initial listing of package stats, presumably referring to darkstat] [after the unpacking of the package(s) I was actually installing, but before their being set up:] /etc/darkstat/init.cfg: 13: Syntax error: Unterminated quoted string invoke-rc.d: initscript darkstat, action "restart" failed. dpkg: error processing darkstat (--configure): subprocess post-installation script returned error exit status 2 [following this, the other package was set up w/o a problem and apt-get exited to the command prompt] 5. When I saw the above line about the syntax error in the init.cfg file, I wondered whether it was some of my changes there that had made the removal of the program impossible. So I went back into the file and decided to try commenting the lines I had previously uncommented (also noting that one of those lines was line 13, which I believe is what the 13 in the error message is referring to. However, it didn't seem to me that there was an 'unterminated quoted string' in that line or in any of the other lines, unless that is an unintuitive phrase) to see if this would allow me to remove the package. 6. Out of curiosity, before trying again to remove the package, I looked at its status in Synaptic. There it was reported as being installed (green box) and there was no indication that there was anything wrong with it or that it was marked for removal. However when I ran an apt-get update in the terminal, the package stats reported '1 not fully installed or removed'. 7. Opened Synaptic, marked darkstat for complete removal, applied it, no errors, and a report that all changes had been applied. Ran another apt- get update in the terminal, and the previously mentioned message didn't come up. So, I'm assuming this problem has been resolved in regards to my system, but it would probably be good for the developers to make whatever changes are necessary to avoid this happening in the future. I think darkstat is probably a good program, and I assume I could have gotten it to work if I would have a bit more scripting/programming experience and/or had more time to research it, work with the settings, etc. But probably the main thing I would suggest is that, if the basic operation of the program is dependent on changing the settings in this init.cfg file, then these changes shouldn't be allowed to stop the program from being removed. Thanks to each of the developers who continue to contribute to developing darkstat, and Emil, once again thank you for your time and interest in this. I hope the above information will be helpful to users/developers of this package, and I will stay subscribed to this bug, in case any of you have any further questions about my experience with darkstat that could be helpful. ** Attachment added: "init.cfg" http://launchpadlibrarian.net/30440214/init.cfg -- unable to completely remove darkstat with Synaptic Package Manager https://bugs.launchpad.net/bugs/413876 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
