Your message dated Tue, 7 Mar 2006 14:21:29 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Package removed from the archive
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: aspseek
Version: 1.2.10-1.1
Severity: normal
Hi.
Once I tried to start aspseek with its init.d script, it didn't come up.
While searching for the cause of the problem, I noticed that aspseek's
logfile is located in /var/lib/aspseek/dlog.log instead of /var/log/...
Hopefully the 'searchd' will uncover the actual location of the logfile
when it's started with no arguments. Otherwise I would have searched
much longer. The problem was that I hadn't started mysql.
As a quick workaround a symbolic link could be created:
# cd /var/log
# ln -s ../lib/aspseek/dlog.log .
Take care.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.5-1-686
Locale: LANG=C, LC_CTYPE=C
Versions of packages aspseek depends on:
ii aspseek-common 1.2.10-1.1 Advanced Internet search engine (C
ii aspseek-libmysqldb 1.2.10-1.1 Advanced Internet search engine (M
ii libc6 2.3.2.ds1-13 GNU C Library: Shared libraries an
ii libgcc1 1:3.3.4-1 GCC support library
ii libstdc++5 1:3.3.4-1 The GNU Standard C++ Library v3
ii zlib1g 1:1.2.1.1-3 compression library - runtime
-- no debconf information
--- End Message ---
--- Begin Message ---
See #321328.
--- End Message ---
