Package: systemimager-client Version: 3.6.3dfsg1-3 Severity: normal If you run si_prepareclient on a system with no installed kernel, it fails to compelete and never starts the rsync daemon.
Steps to repeat. 1. Make sure that there are no kernels in installed in /boot 2. Run si_prepareclient 3. Observe that upon completion there is no rsyncd process running 4. Attempt to connect using si_getimage and observe failure to connect This sutation happened to me in a Xen domU. Since the kernel is loaded from within the dom0, there is no need to have a kernel in the domU. When si_prepareclient tries to populate the /etc/systemimager/boot directory, it cannot find a kernel and so fails. Regards, -Roberto -- System Information: Debian Release: 4.0 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-4-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages systemimager-client depends on: ii file 4.17-5etch1 Determines file type using "magic" ii perl 5.8.8-7 Larry Wall's Practical Extraction ii rsync 2.6.9-2 fast remote file copy program (lik ii systemconfigurator 2.2.2-1 Unified Configuration API for Linu ii systemimager-boot-i386-stan 3.6.3dfsg1-3 SystemImager boot binaries for i38 ii systemimager-common 3.6.3dfsg1-3 Utilities and libraries common to systemimager-client recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
