Your message dated Mon, 31 Oct 2011 20:59:59 +0100
with message-id <[email protected]>
and subject line Re: Bug#646782: binc-client obsolated OOM api
has caused the Debian Bug report #646782,
regarding boinc-client: fails to start becasue it is using obsolated OOM api
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.)


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

Dear Maintainer,

It looks boinc-client initscript is using deprecated
Out-Of-Memmory adjustment api, which for some
reasons on debian kernel is already disabled.
(previously it worked, but printed warning in kernel message
log).

initscript should migrate to new oom adjustment scheme.

Without it, it shows lots of errors in script.

please look at linux kernel Documentation/ dir for informations.

Regards,
Witek

-- 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: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 3.0.0-2-686-pae (SMP w/1 CPU core)
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages boinc-client depends on:
ii  adduser                3.113           
ii  ca-certificates        20111025        
ii  debconf [debconf-2.0]  1.5.41          
ii  libc6                  2.13-21         
ii  libcurl3               7.21.7-3        
ii  libgcc1                1:4.6.2-1       
ii  libssl1.0.0            1.0.0e-2        
ii  libstdc++6             4.6.2-1         
ii  python                 2.7.2-9         
ii  zlib1g                 1:1.2.3.4.dfsg-3

boinc-client recommends no packages.

Versions of packages boinc-client suggests:
ii  boinc-app-seti     <none>       
ii  boinc-manager      6.13.6+dfsg-2
ii  x11-xserver-utils  7.6+3        

-- Configuration Files:
/etc/boinc-client/global_prefs_override.xml changed:
<global_preferences>
   <run_on_batteries>0</run_on_batteries>
   <run_if_user_active>0</run_if_user_active>
   <run_gpu_if_user_active>0</run_gpu_if_user_active>
   <idle_time_to_run>2.000000</idle_time_to_run>
   <suspend_cpu_usage>25.000000</suspend_cpu_usage>
   <start_hour>0.000000</start_hour>
   <end_hour>0.000000</end_hour>
   <net_start_hour>0.000000</net_start_hour>
   <net_end_hour>0.000000</net_end_hour>
   <leave_apps_in_memory>0</leave_apps_in_memory>
   <confirm_before_connecting>0</confirm_before_connecting>
   <hangup_if_dialed>0</hangup_if_dialed>
   <dont_verify_images>0</dont_verify_images>
   <work_buf_min_days>0.000000</work_buf_min_days>
   <work_buf_additional_days>0.250000</work_buf_additional_days>
   <max_ncpus_pct>100.000000</max_ncpus_pct>
   <cpu_scheduling_period_minutes>90.000000</cpu_scheduling_period_minutes>
   <disk_interval>600.000000</disk_interval>
   <disk_max_used_gb>100.000000</disk_max_used_gb>
   <disk_max_used_pct>50.000000</disk_max_used_pct>
   <disk_min_free_gb>1.000000</disk_min_free_gb>
   <vm_max_used_pct>75.000000</vm_max_used_pct>
   <ram_max_used_busy_pct>50.000000</ram_max_used_busy_pct>
   <ram_max_used_idle_pct>90.000000</ram_max_used_idle_pct>
   <max_bytes_sec_up>118394.880000</max_bytes_sec_up>
   <max_bytes_sec_down>318720.000000</max_bytes_sec_down>
   <cpu_usage_limit>100.000000</cpu_usage_limit>
   <daily_xfer_limit_mb>0.000000</daily_xfer_limit_mb>
   <daily_xfer_period_days>0</daily_xfer_period_days>
</global_preferences>

/etc/boinc-client/gui_rpc_auth.cfg [Errno 13] Brak dostępu: 
u'/etc/boinc-client/gui_rpc_auth.cfg'

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



--- End Message ---
--- Begin Message ---
Hello,

On 10/31/2011 07:22 PM, Witold Baryluk wrote:

> it looks my raport is actually invalid,
> I cannot reproduce it anymore.
> It is possible that some other service was using it,
> and output when booting was messed (interleaved)
> due to the concurrent starting of various other services.
> 
> It looks it is not a bug in boinc-client.
> 
> Thanks.

you made me go through
  http://lwn.net/Articles/317814/
so I learned something.

So, have many thanks anyway

Steffen


--- End Message ---

Reply via email to