Your message dated Tue, 3 Jan 2017 23:09:11 +0100
with message-id <[email protected]>
and subject line lockfile-progs: ntp hangs on boot due to lockfile-create not 
handling long hostnames
has caused the Debian Bug report #810905,
regarding lockfile-progs: ntp hangs on boot due to lockfile-create not handling 
long hostnames
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.)


-- 
810905: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810905
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lockfile-progs
Version: 0.1.17
Severity: important

Dear Maintainer,
*** Please consider answering these questions, where appropriate ***

   * What led up to the situation?  Fresh installation of Debian 7
   * What exactly did you do (or not do) that was effective (or
     ineffective)?  Used long hostname
   * What was the outcome of this action?  lockfile-create crashes and ntp 
start hangs, debian 7 hangs on boot
   * What outcome did you expect instead? ntp to start ok

*** End of the template - remove these lines ***


-- System Information:
Debian Release: 7.9
  APT prefers oldstable-updates
  APT policy: (500, 'oldstable-updates'), (500, 'oldstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages lockfile-progs depends on:
ii  libc6         2.13-38+deb7u8
ii  liblockfile1  1.09-5

lockfile-progs recommends no packages.

lockfile-progs suggests no packages.

-- no debconf information

paul@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:~$ hostname | wc
      1       1      47
paul@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:~$ sudo su
[sudo] password for paul:
root@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx:/home/paul#  
/usr/bin/lockfile-create /var/lock/ntpdate
*** glibc detected *** /usr/bin/lockfile-create: free(): invalid next size 
(fast): 0x0000000000e6c0a0 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x75be6)[0x7f4f0d691be6]
/lib/x86_64-linux-gnu/libc.so.6(cfree+0x6c)[0x7f4f0d69698c]
/usr/lib/x86_64-linux-gnu/liblockfile.so.1(lockfile_create+0x77)[0x7f4f0d9a8f37]
/usr/bin/lockfile-create[0x4010c9]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xfd)[0x7f4f0d63aead]
/usr/bin/lockfile-create[0x401371]
======= Memory map: ========
00400000-00402000 r-xp 00000000 08:01 279442                             
/usr/bin/lockfile-create
00602000-00603000 rw-p 00002000 08:01 279442                             
/usr/bin/lockfile-create
00e6c000-00e8d000 rw-p 00000000 00:00 0                                  [heap]
7f4f08000000-7f4f08021000 rw-p 00000000 00:00 0
7f4f08021000-7f4f0c000000 ---p 00000000 00:00 0
7f4f0d406000-7f4f0d41b000 r-xp 00000000 08:01 389425                     
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4f0d41b000-7f4f0d61b000 ---p 00015000 08:01 389425                     
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4f0d61b000-7f4f0d61c000 rw-p 00015000 08:01 389425                     
/lib/x86_64-linux-gnu/libgcc_s.so.1
7f4f0d61c000-7f4f0d79d000 r-xp 00000000 08:01 389407                     
/lib/x86_64-linux-gnu/libc-2.13.so
7f4f0d79d000-7f4f0d99d000 ---p 00181000 08:01 389407                     
/lib/x86_64-linux-gnu/libc-2.13.so
7f4f0d99d000-7f4f0d9a1000 r--p 00181000 08:01 389407                     
/lib/x86_64-linux-gnu/libc-2.13.so
7f4f0d9a1000-7f4f0d9a2000 rw-p 00185000 08:01 389407                     
/lib/x86_64-linux-gnu/libc-2.13.so
7f4f0d9a2000-7f4f0d9a7000 rw-p 00000000 00:00 0
7f4f0d9a7000-7f4f0d9aa000 r-xp 00000000 08:01 263279                     
/usr/lib/x86_64-linux-gnu/liblockfile.so.1.0
7f4f0d9aa000-7f4f0dba9000 ---p 00003000 08:01 263279                     
/usr/lib/x86_64-linux-gnu/liblockfile.so.1.0
7f4f0dba9000-7f4f0dbaa000 r--p 00002000 08:01 263279                     
/usr/lib/x86_64-linux-gnu/liblockfile.so.1.0
7f4f0dbaa000-7f4f0dbab000 rw-p 00003000 08:01 263279                     
/usr/lib/x86_64-linux-gnu/liblockfile.so.1.0
7f4f0dbab000-7f4f0dbcb000 r-xp 00000000 08:01 389419                     
/lib/x86_64-linux-gnu/ld-2.13.so
7f4f0ddc0000-7f4f0ddc3000 rw-p 00000000 00:00 0
7f4f0ddc8000-7f4f0ddca000 rw-p 00000000 00:00 0
7f4f0ddca000-7f4f0ddcb000 r--p 0001f000 08:01 389419                     
/lib/x86_64-linux-gnu/ld-2.13.so
7f4f0ddcb000-7f4f0ddcc000 rw-p 00020000 08:01 389419                     
/lib/x86_64-linux-gnu/ld-2.13.so
7f4f0ddcc000-7f4f0ddcd000 rw-p 00000000 00:00 0
7ffd7fe18000-7ffd7fe39000 rw-p 00000000 00:00 0                          [stack]
7ffd7ff0d000-7ffd7ff0e000 r-xp 00000000 00:00 0                          [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0                  
[vsyscall]
Aborted

--- End Message ---
--- Begin Message ---
source: liblockfile
version: 1.09-6

Was fixed in 1.09-6, which is in jessie.

--- End Message ---

Reply via email to