Package: cpm Version: 0.32-1 Severity: important Dear Maintainer,
After increasing the system memlock limit to avoid cpm's startup
warning, cpm will fail to start with an error. Reducing the limit will
allow cpm to start, but with the original warning message.
Here is a sample session illustrating the issue:
$ ulimit -l
512
$ cpm
memlock:Cannot allocate memory
$ ulimit -l 256
$ cpm
Running without root privileges: yes
Memory protection from core dumps: yes
Memory protection from swap writings: no
Max. memory lock ok: no (256 kB)
Memory protection from ptrace spying: yes
Validation of environment variables: yes
Cracklib dictionary (/var/cache/cracklib/cracklib_dict):yes
Maximum security level not reached. Your database will be less protected
while CPM is running.
Are you sure you want to continue?
Thanks.
-- System Information:
Debian Release: 8.0
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages cpm depends on:
ii libassuan0 2.1.2-2
ii libc6 2.19-13
ii libcdk5 5.0.20060507-4
ii libcrack2 2.9.2-1
ii libdotconf0 1.3-0.2
ii libgpg-error0 1.17-3
ii libgpgme11 1.5.1-6
ii libncursesw5 5.9+20140913-1+b1
ii libtinfo5 5.9+20140913-1+b1
ii libxml2 2.9.1+dfsg1-4
ii libxml2-utils 2.9.1+dfsg1-4
ii zlib1g 1:1.2.8.dfsg-2+b1
cpm recommends no packages.
cpm suggests no packages.
-- no debconf information
--
Regards,
Scott Leggett
signature.asc
Description: Digital signature
