Your message dated Thu, 18 Feb 2010 03:33:28 +0000
with message-id <[email protected]>
and subject line Bug#559053: fixed in boinc 6.10.17+dfsg-3
has caused the Debian Bug report #559053,
regarding boinc-client: Error when setting oom_adj
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
559053: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=559053
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: boinc-client
Version: 6.10.17+dfsg-1
Severity: normal

Hi,

Sometimes I get this message when starting BOINC:

/etc/init.d/boinc-client: 212: cannot create /proc/5517/oom_adj: Directory 
nonexistent

It turns out that BOINC calls 'uname' to determine the platform and the
pid of the 'uname' process sometimes gets included in $children, but the
'uname' process finishes before the init script has a chance to set
oom_adj. I suggest adding "2>/dev/null || true" after "echo ... > .../oom_adj".

Gabor

-- Package-specific info:
-- Contents of /etc/default/boinc-client:
# This file is /etc/default/boinc-client, it is a configuration file for the
# /etc/init.d/boinc-client init script.

# Set this to 1 to enable and to 0 to disable the init script.
ENABLED="1"

# Set this to 1 to enable advanced scheduling of the BOINC core client and
# all its sub-processes (reduces the impact of BOINC on the system's
# performance).
SCHEDULE="1"

# The BOINC core client will be started with the permissions of this user.
BOINC_USER="boinc"

# This is the data directory of the BOINC core client.
BOINC_DIR="/var/lib/boinc-client"

# This is the location of the BOINC core client, that the init script uses.
# If you do not want to use the client program provided by the boinc-client
# package, you can specify here an alternative client program.
#BOINC_CLIENT="/usr/local/bin/boinc"
BOINC_CLIENT="/usr/bin/boinc"

# Here you can specify additional options to pass to the BOINC core client.
# Type 'boinc --help' or 'man boinc' for a full summary of allowed options.
#BOINC_OPTS="--allow_remote_gui_rpc"
BOINC_OPTS=""

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (110, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.31.6 (SMP w/2 CPU cores; PREEMPT)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages boinc-client depends on:
ii  adduser                3.111             add and remove users and groups
ii  ca-certificates        20090814          Common CA certificates
ii  debconf [debconf-2.0]  1.5.28            Debian configuration management sy
ii  libc6                  2.10.2-2          GNU C Library: Shared libraries
ii  libcurl3               7.19.7-1          Multi-protocol file transfer libra
ii  libgcc1                1:4.4.2-3         GCC support library
ii  libssl0.9.8            0.9.8k-7          SSL shared libraries
ii  libstdc++6             4.4.2-3           The GNU Standard C++ Library v3
ii  lsb-base               3.2-23            Linux Standard Base 3.2 init scrip
ii  python                 2.5.4-2           An interactive high-level object-o
ii  zlib1g                 1:1.2.3.3.dfsg-15 compression library - runtime

Versions of packages boinc-client recommends:
ii  schedtool                     1.3.0-1    Queries/alters process' scheduling

Versions of packages boinc-client suggests:
pn  boinc-app-seti            <none>         (no description available)
ii  boinc-manager             6.10.17+dfsg-1 GUI to control and monitor the BOI

-- debconf information:
  boinc-client/remove_boinc_dir: false



--- End Message ---
--- Begin Message ---
Source: boinc
Source-Version: 6.10.17+dfsg-3

We believe that the bug you reported is fixed in the latest version of
boinc, which is due to be installed in the Debian FTP archive:

boinc-client_6.10.17+dfsg-3_amd64.deb
  to main/b/boinc/boinc-client_6.10.17+dfsg-3_amd64.deb
boinc-dbg_6.10.17+dfsg-3_amd64.deb
  to main/b/boinc/boinc-dbg_6.10.17+dfsg-3_amd64.deb
boinc-dev_6.10.17+dfsg-3_amd64.deb
  to main/b/boinc/boinc-dev_6.10.17+dfsg-3_amd64.deb
boinc-manager_6.10.17+dfsg-3_amd64.deb
  to main/b/boinc/boinc-manager_6.10.17+dfsg-3_amd64.deb
boinc_6.10.17+dfsg-3.diff.gz
  to main/b/boinc/boinc_6.10.17+dfsg-3.diff.gz
boinc_6.10.17+dfsg-3.dsc
  to main/b/boinc/boinc_6.10.17+dfsg-3.dsc



A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Rene Mayorga <[email protected]> (supplier of updated boinc package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 15 Jan 2010 19:34:46 -0600
Source: boinc
Binary: boinc-client boinc-manager boinc-dev boinc-dbg
Architecture: source amd64
Version: 6.10.17+dfsg-3
Distribution: unstable
Urgency: low
Maintainer: Debian BOINC Maintainers <[email protected]>
Changed-By: Rene Mayorga <[email protected]>
Description: 
 boinc-client - core client for the BOINC distributed computing infrastructure
 boinc-dbg  - debugging symbols for BOINC binaries
 boinc-dev  - development files to build applications for BOINC projects
 boinc-manager - GUI to control and monitor the BOINC core client
Closes: 559053
Changes: 
 boinc (6.10.17+dfsg-3) unstable; urgency=low
 .
   * Ignore errors when setting oom_adj for boinc client,
     Thanks to Gábor Gombás <[email protected]> for the bug report
     and the hint for the solution. (Closes: #559053)
   * Fix str_replace.h installation path on boinc-dev package
Checksums-Sha1: 
 d6e6e238f4e30973d56fb11a691b5193143c5624 2317 boinc_6.10.17+dfsg-3.dsc
 50ecf1e786f8d142e93222f1dc30d220c20f81c4 56775 boinc_6.10.17+dfsg-3.diff.gz
 3bd2299643f9dad1cc9fc786755babdc7dac6c80 448400 
boinc-client_6.10.17+dfsg-3_amd64.deb
 a6b3b8fa227fb83196a18c3be873d3f8d53cc24e 1824158 
boinc-manager_6.10.17+dfsg-3_amd64.deb
 be9957bf3962d03bd4156cf12165ce1c627e1403 526712 
boinc-dev_6.10.17+dfsg-3_amd64.deb
 a3b5b09945a9ac4e7558b204c249be733675a9ee 7999988 
boinc-dbg_6.10.17+dfsg-3_amd64.deb
Checksums-Sha256: 
 6a1c2e64d03742a5859153bbe2175d3c27183d989c3b88e5a7f64c72f3176a2d 2317 
boinc_6.10.17+dfsg-3.dsc
 be56b742852d4a9641a51c72e1a949b2736efea234a3c8b905ea2e27a5c164cf 56775 
boinc_6.10.17+dfsg-3.diff.gz
 8d70e9f767c5d8cd50b1ff54f2f2b0f1f17ad5061f6d03d11ad40514b9182e69 448400 
boinc-client_6.10.17+dfsg-3_amd64.deb
 e0f657124da0b5c9e5eaa34df7d1a7df777bd11e95b11eb1d92d0a1f015df964 1824158 
boinc-manager_6.10.17+dfsg-3_amd64.deb
 e95bb5c3e77f41f8fd9d1a7a3df1a4b3431739bb0026335ac1b98dd7dcfa146e 526712 
boinc-dev_6.10.17+dfsg-3_amd64.deb
 3a9e46bd2bf214bcabfbab1680044d5d32cd79c39cc56217f5228513072fa0e1 7999988 
boinc-dbg_6.10.17+dfsg-3_amd64.deb
Files: 
 55f3892bb9b3c181d77007d93f03d663 2317 net optional boinc_6.10.17+dfsg-3.dsc
 6c3e3314464085a380a25c891364ea5a 56775 net optional 
boinc_6.10.17+dfsg-3.diff.gz
 b1b9e74c545a581c5b3ced8e522923b2 448400 net optional 
boinc-client_6.10.17+dfsg-3_amd64.deb
 cf57afc69e0ee80e4304e1785edd2d78 1824158 x11 optional 
boinc-manager_6.10.17+dfsg-3_amd64.deb
 60804a07523c7dbd85f32c7f6d9fa340 526712 devel optional 
boinc-dev_6.10.17+dfsg-3_amd64.deb
 b2aca9fae110fe07a95a8d9ea4ab97eb 7999988 debug extra 
boinc-dbg_6.10.17+dfsg-3_amd64.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iQIcBAEBCAAGBQJLfJ2BAAoJELsgrCDgt9a+iKcP/3N4UzksuAYG/4Y37wxQv0Vi
oBL4GhJiVqwnYpr8f+LggtzKCHDzwoVbfO8AfguRn9Brm5VcYdgVUic5Vqo3OcC9
gF0HpBPA1g99L1h/Dj3jP0kdUrs8LnbNxhefdOfpqV/QxYpIglpi+B9xf7jIvscb
z/XAk79v/bMHYhzp1vgN8IrGK3NjsGWPb/yh0uYnSJ++jWWHhQ9PWeZuH+lkFkxl
3aTUgSz7QnCqop4Y8GFVwhUBuzETpkar2rOc2Q1LWkrqZILSaMA7PgJGPT+B5sof
7BdVhv12AKfdsT70b3pN2V1OUhgcxn6lKVjseKr3BtZi5iA0j3y2lLlyhbM84vIb
LJNBk/9BqpunzBB+LjBnkohVbME2aKFIzlY+YkIG+tA4hEAe9KEav3q6XWxLX3JQ
LUs/9cxF+Cs5I4syml6T0LcIu8m6DFSIRUEzKLuHD/m7hN71ikuXbKz5TEj7FFtU
gYY5+N5PF3UngbjFhbw5gqC5NyWyEH5y8sAoSnSc5Hb9NRMNNB1VqGnNsR0DXYJh
5Uv1LRReBtrPbnjCyp65Q0+OyXBC6wKINjjX03/JedKfKaL6FfUB3kznnMhl0D86
vL/yZQs7wz1I41FJtB+Lw40NRrtgFY1ylJnq/e8XtbEJBToYHpdQBN0pm3bbdenB
XEj7nSHzwXzjJFuo50Ht
=0jLA
-----END PGP SIGNATURE-----



--- End Message ---

Reply via email to