<html>
<body>
<font face="Courier New, Courier">Hi there Gianfranco! I'm glad to be
onboard :)<br><br>
Yes, my script was for personal use, for my particular use case, and
definately not intended for a general audience. For starters, it uses
gksudo, which I'm not sure it is availavle in every distro/DE. I wish XDG
tools had a platform-independent command for a graphical sudo.<br><br>
The script can, at best, give some insights on what a general solution
could do. Also, it is important to notice that it tackles on 2 very
distinct issues: A) boinc init not finding a GPU, and B) Manager not
starting boinc if user previously "Exit (Ctrl+Q)" and chose to
shut down tasks. He can shut down boinc client via Manager GUI, but no
GUI way to (re-)start it.<br><br>
Judging by the other emails I've received from this list, I guess you
guys are focusing on the harder issue, (A). But (B) is also annoying, and
I assume it is an easy fix on Manager itself.<br><br>
Btw, how can Manager stop the boinc client and shut down tasks without
asking for a password? Can a similar approach be used to re-start
it?<br><br>
As for (A), I remember reading somewhere (changelogs perhaps?) that the
init script was already changed to "$all" or something, meaning
it was already supposed to run only after all other scripts run. So maybe
trying to find a better order is a dead-end approach, and we could
consider either moving from SysV init to upstart, or perhaps even X
startup.<br><br>
Last but not least, neither (A) nor (B) issues are related to [Bug
1140597 "New version is available" notification should be
disabled], so maybe we should change the email subject to whatever issue
we focus on?<br><br>
Regards,<br>
ML<br><br>
At 08:02 10/03/2013, you wrote:<br><br>
<blockquote type=cite class=cite cite="">Hi MestreLion, I think this is
the right place to discuss to.<br><br>
Unfortunately you script has a bad behaviour for people that DON'T have
an usable GPU...<br><br>
I don't like to restart boinc to everybody just because the might suffer
from bug #1140597<br><br>
What do you think about?<br><br>
My opinion is that there should a way for giving the right order to init
scripts, but I don't know at the moment how to change the script right
now...<br><br>
Gianfranco<br><br>
<br>
</font><font face="Courier New, Courier" size=2><b>From: </b>MestreLion
<launchpad@rodrigosilva.com>; <br>
<b>To: </b><pkg-boinc-devel@lists.alioth.debian.org>; <br>
<b>Subject: </b>[Bug 1140597] Re: "New version is available"
notification should be disabled <br>
<b>Sent: </b>Sun, Mar 10, 2013 12:05:22 AM <br>
</font><font face="Courier New, Courier"><br>
Whatever mailing list you guys use to continue this discussion, sign
me<br>
in! :)<br><br>
My C++ skills are a bit rusty, but I may be able to help, if not in<br>
programming, at least in discussing strategies, approaches and<br>
packaging.<br><br>
Also, I've created a script (wrapper for boincmgr) as a workaround
for<br>
some of the annoying boinc bugs: not detecting a GPU at boot and not
re-<br>
starting boinc client after shutting its tasks, so maybe it will be<br>
useful for you guys:
<a href="https://github.com/MestreLion/scripts/blob/master">
https://github.com/MestreLion/scripts/blob/master</a><br>
/boinc-manager<br><br>
-- <br>
You received this bug notification because you are a member of
Debian<br>
BOINC Maintainers, which is subscribed to boinc in Ubuntu.<br>
<a href="https://bugs.launchpad.net/bugs/1140597">
https://bugs.launchpad.net/bugs/1140597</a><br><br>
Title:<br>
"New version is available" notification should be
disabled<br><br>
To manage notifications about this bug go to:<br>
<a href="https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1140597/+subscriptions">
https://bugs.launchpad.net/ubuntu/+source/boinc/+bug/1140597/+subscriptions</a>
<br><br>
-- <br>
pkg-boinc-devel mailing list<br>
pkg-boinc-devel@lists.alioth.debian.org<br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-boinc-devel">
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-boinc-devel</a>
</font></blockquote></body>
</html>