Re: [boinc_dev] I: Several security issues in ops html directory

___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.

[boinc_dev] [patch] mystery solved? Aw: Re: BOINC having too many open files - failure in opendir()

] BOINC having too many open files - failure in opendir() Get the list of open files (ls -l /proc/$(pidof boinc)/fd) when that happens. Does the client die after that last fopen() failure? Maybe you could write a script to log the open file list every few minutes. -- Nicolás 2013/5/16 Steffen

Re: [boinc_dev] [patch] mystery solved? Re: BOINC having too many open files - failure in opendir()

that shows open()s. It's also possible that the system is running out of file descriptors because of software other than BOINC. -- David On 18-May-2013 4:00 AM, Steffen Möller wrote: Dear all, I skimmed through all invocations of (boinc_)?fopen() in api/ and lib/, seeking

[boinc_dev] [patch] .po files with issues

Hello, Debian performs a routine check on the .po files in all its packages. The one of BOINC http://i18n.debian.org/l10n-pkg-status/b/boinc.html indicates a few issues. I then ran msgfmt -c -o /dev/null po file as indicated and for de.po prepared the attached patch. Cheers, Steffen Index:

[boinc_dev] prepared to accept patches for llvm, i.e. clang, compatibility?

Hello, The compiler LLVM (http://en.wikipedia.org/wiki/Clang) makes continuous progress, both technically and for its acceptance in the community, and is faster than gcc/g++ in some cases. They have a gcc-compatibility frontent called clang, which after a funcountable number of patches/fun I

Re: [boinc_dev] could the git comment be more descriptive or better empty ?

Hi Toralf, Yeah - I was just grumbling about a commit with the only message Include cmath instead of math.h various places nothing else - and of course gitk shows for a dozen of files such a change. Every ?!%%$$ user can see the diff using gitk - so important IMO is just a short

Re: [boinc_dev] prepared to accept patches for llvm, i.e. clang, compatibility?

Hi Charlie, Have many thanks! I can now also confirm BOINC to build with clang. A couple of warnings are left, but those also appear with the gcc. Cheers, Steffen Gesendet: Donnerstag, 30. Mai 2013 um 03:28 Uhr Von: Charlie Fenton charl...@ssl.berkeley.edu An: Steffen Möller steffen_moel

Re: [boinc_dev] Can we do shared memory with no disk usage?

of the large I/O? -- David On 16-Jun-2013 11:03 AM, Steffen Möller wrote: Hello, iostat gives rather drastic values for the amount of data that is written to disk by BOINC and/or its applications. Some good fellow once crafted a but report about it http://bugs.debian.org/cgi-bin

[boinc_dev] opendir() failures saga continues

Dear all, It took three days of rather intense compute and the opendir() error resurfaced. I (now :-) ) agree with David that my past patches would not have any effect ... that it is the older statically linked clients causing the problem. The application run was mostly rosetta, this time.

Re: [boinc_dev] Can we do shared memory with no disk usage?

this at the moment. Cheers, Steffen Gesendet: Montag, 17. Juni 2013 um 17:20 Uhr Von: Eric J Korpela korp...@ssl.berkeley.edu An: Steffen Möller steffen_moel...@gmx.de Cc: boinc_dev@ssl.berkeley.edu boinc_dev@ssl.berkeley.edu Betreff: Re: [boinc_dev] Can we do shared memory with no disk usage? We considered

Re: [boinc_dev] Can we do shared memory with no disk usage?

Gesendet: Montag, 17. Juni 2013 um 21:29 Uhr Von: David Anderson da...@ssl.berkeley.edu An: boinc_dev@ssl.berkeley.edu Betreff: Re: [boinc_dev] Can we do shared memory with no disk usage? In situations were BOINC is causing unexpectedly large ( 1 GB/hour) disk I/O, we need to figure out

Re: [boinc_dev] Can we do shared memory with no disk usage?

___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.

Re: [boinc_dev] Can we do shared memory with no disk usage?

Hello, Gesendet: Mittwoch, 19. Juni 2013 um 21:39 Uhr Von: Nicolás Alvarez nicolas.alva...@gmail.com 2013/6/18 Heinz-Bernd Eggenstein heinz-bernd.eggenst...@aei.mpg.de: Hi all, Interesting. I guess it would be useful to run BOINC on a dedicated partition (e.g. ext hard disk/ USB

Re: [boinc_dev] Can we do shared memory with no disk usage?

and Yoyo@Home, which was seen in iotop, albeit performing equally and always a tolerable 1KB/s rate. I'll go and try geeting the original situation back with a self-compiled graphics-enabled SETI over the course of next week. Cheers, Steffen On 17-Jun-2013 11:14 AM, Steffen Möller wrote

Re: [boinc_dev] boinc libstdc++ linking

Hello, Gesendet: Montag, 08. Juli 2013 um 12:53 Uhr Von: Alyssa Milburn amilb...@math.leidenuniv.nl An: Gianfranco Costamagna costamagnagianfra...@yahoo.it Cc: boinc_dev@ssl.berkeley.edu boinc_dev@ssl.berkeley.edu Betreff: Re: [boinc_dev] boinc libstdc++ linking On Mon, Jul 08, 2013 at

Re: [boinc_dev] addressing some clang warnings

Gesendet: Dienstag, 09. Juli 2013 um 11:47 Uhr Von: Gianfranco Costamagna costamagnagianfra...@yahoo.it An: Alyssa Milburn amilb...@math.leidenuniv.nl Cc: steffen_moel...@gmx.de steffen_moel...@gmx.de, boinc_dev@ssl.berkeley.edu boinc_dev@ssl.berkeley.edu Betreff: Re: [boinc_dev]

Re: [boinc_dev] boinc libstdc++ linking

Gesendet: Montag, 08. Juli 2013 um 21:46 Uhr Von: David Anderson da...@ssl.berkeley.edu The programs in samples/ are examples of how to build applications that will run on as many Linux machines as possible, including those that have old or missing libstdc++. That's why they statically link

Re: [boinc_dev] addressing some clang warnings

Gesendet: Dienstag, 09. Juli 2013 um 00:36 Uhr Von: David Anderson da...@ssl.berkeley.edu An: Gianfranco Costamagna costamagnagianfra...@yahoo.it Cc: boinc_dev@ssl.berkeley.edu boinc_dev@ssl.berkeley.edu Betreff: Re: [boinc_dev] addressing some clang warnings Are these changes all

Re: [boinc_dev] GLIBC 2.15 required for BOINC Manager?

Hi Jon, Debian 7.3 (stable) uses glibc v2.13, Debian Jessie (testing) uses v2.17, and Debian Sid (unstable) uses v2.18 so it looks like they've changed their minds. However, at present, the only way to run the current BOINC client on the current Debian version is to use either the testing

Re: [boinc_dev] GLIBC 2.15 required for BOINC Manager?

. Januar 2014 um 21:08 Uhr Von: Rom Walton r...@romwnet.org An: Steffen Möller steffen_moel...@gmx.de, Jon Sonntag j...@thesonntags.com Cc: BOINC Developers Mailing List @berkeley.edu boinc_dev@ssl.berkeley.edu Betreff: RE: [boinc_dev] GLIBC 2.15 required for BOINC Manager? At this point, our

Re: [boinc_dev] GLIBC 2.15 required for BOINC Manager?

Hello, Gesendet: Mittwoch, 29. Januar 2014 um 19:41 Uhr Von: Jon Sonntag j...@thesonntags.com My only hesitation with backports is the warning on the home page which states: Backports cannot be tested as extensively as Debian stable, and backports are provided on an as-is basis, with risk of

Re: [boinc_dev] Problems with crypt_prog

Hi Crit/Randolph, I cannot recall to have run into this issue myself. This is how it looks for us, following (and improving) the Debian Wiki page: moeller@twin1a:~ $ dpkg -L boinc-server-maker | grep crypt /usr/lib/boinc-server-maker/lib/crypt_prog moeller@twin1a:~ $ dpkg -l boinc-server-maker

Re: [boinc_dev] Boinc and shared dynamic libraries

___ boinc_dev mailing list boinc_dev@ssl.berkeley.edu http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.

Re: [boinc_dev] providing BOINC through the Apple App Store

Homebrew has a $ brew search boinc Caskroom/cask/boinc and it might make some good sense to interact with those folks a bit more, also for local compilations of scientific apps. But how many will find that by chance who would not go and install from the website. No idea. Steffen On 23/05/16

[boinc_dev] Astonishing effect of Link Time Optimisation on BOINC client

Dear all, some of you may be aware of the BOINC client shipping with Debian, Ubuntu, Mint and the other .deb-based Linux distributions [1]. While updating to 7.6.32 we have revised our invocation of the Link Time Optimisation (LTO) [2]. This had the effect of a notable reduction of the disk-space

Re: [boinc_dev] Suspected cpid hash collisions for newly installed clients on Linux

effect comes and goes, > and I can think I have an effective way to avoid it (as with buying new USB > dongles) then that can fall in a heap. I cannot (yet) produce a definitive > recipe to reliably demonstrate this effect, so up to know I have not filed > a bug report. Do you think I

Re: [boinc_dev] [boinc_projects] keywords

Don't know how much it is worth, but as a part-time contributor to _many_ Open Source projects (and once having worked with a computer science degree as a software engineer for a software company that does software environments for software development) I would like to express my wholehearted

Re: [boinc_dev] [boinc_projects] keywords

On 22.07.17 10:13, David Anderson wrote: > > On 7/21/2017 1:26 AM, David Wallom wrote: >> the responsibility for functions to different community groups. As >> such it will be essential that we move to a multi branch development >> methodology in some form of public repository. I use this in a

Re: [boinc_dev] Software development and branches, was Re: [boinc_projects] keywords

> > On 8/7/2017 7:21 AM, Steffen Möller wrote: >> Well, git makes one's "senses reeling", at least when one has started a >> career with CVS. Linus had helped us escape, and he possibly gets more >> respect from me for that than for his kernel work. For me, i

Re: [boinc_dev] Software development and branches, was Re: [boinc_projects] keywords

On 07.08.17 17:51, Oliver Bock wrote: > On 07.08.2017 16:21, Steffen Möller wrote: >> So, please find a way to stop this so very outdated discussion. > This discussion is meant to help reaching a consensus on how to do > things in the future - the very things you asked for

Re: [boinc_dev] Software development and branches, was Re: [boinc_projects] keywords

Well, git makes one's "senses reeling", at least when one has started a career with CVS. Linus had helped us escape, and he possibly gets more respect from me for that than for his kernel work. For me, it was the git repository for BOINC _packaging_ that had forced me into it, long before BOINC

Re: [boinc_dev] master broken

On 12/05/2017 12:16, Christian Beer wrote: > On 12.05.2017 12:05, Vitalii Koshura wrote: >> Hello Gianfranco, >> >> We have Travis CI for continuous builds and it is not failed. >> Could you please take a look why Travis built it ok and you got errors? > My guess is that there is a compiler

Re: [boinc_dev] release 7.8.3?

On 16.10.17 15:07, Laurence wrote: > Hi Jord, > > On 16/10/17 12:24, Jord van der Elst wrote: >> On Mon, Oct 16, 2017 at 12:06 PM, Richard Haselgrove >> > >> wrote: >> >>     Berkeley has outsourced the distribution of Linux

Re: [boinc_dev] release 7.8.3?

On 16.10.17 23:07, Laurence Field wrote: > Hi Steffen, > > On 16/10/17 16:46, Steffen Möller wrote: >> >> And he also builds the complete packages together with the server side >> components afterwards that go to the experimental section of Debian - >> see the bo

[boinc_dev] Separation of BOINC client and server source tree

Hello, We cannot distribute the BOINC server package in Debian since it is not allowed to have code redundancy between packages of the distribution, and be it for the source packages, so we cannot have the server and client releases in parallel. The server side is on me, so this is somewhat fine

Re: [boinc_dev] release 7.8.3?

Hi Laurence, On 22.10.17 23:04, Laurence wrote: > The BOINC client v7.8.3 is available for testing on Linux > > For Debian/Ubuntu > > sudo apt-add-repository ppa:costamagnagianfranco/boinc > sudo apt-get update > sudo apt-get install boinc-manager kind of :) For the regular user of

Re: [boinc_dev] release 7.8.3?

ccessibility, if that is of any help. Best, Steffen > > On 10/16/2017 7:46 AM, Steffen Möller wrote: >> On 16.10.17 15:07, Laurence wrote: >>> Hi Jord, >>> >>> On 16/10/17 12:24, Jord van der Elst wrote: >>>> On Mon, Oct 16, 2017 at 12:06 PM,

[boinc_dev] BOINC has a SciCrunch "Research Resource IDentifier" (RRID)

Is is BOINC - Berkeley Open Infrastructure for Network Computing, RRID:SCR_015896 These RRIDs have become pretty much accepted as a help to orchestrate the zoo of tools in computational biology. So, whenever a finding that was produced with the help of BOINC is announced, be it online or in

Re: [boinc_dev] Linux build issues

On 16.11.17 22:53, Kathryn Marks wrote: > Installing the ssl lib worked. Thanks. > > > BTW: Just doing this for the pure fun of it (yes I'm strange) > > > That said, I'm stuck again. > > checking for LIBNOTIFY... no > configure: error: Package requirements (libnotify) were not met: > > No