Package: bastille
Version: 1:3.0.9-12
Severity: important
The problem is in /etc/init.d/bastille-firewall, which uses both the directory
/var/lock/bastille (to signal
that /etc/init.d/bastille-firewall is running) and the file
/var/lock/bastille/bastille-firewall (to signal
that the firewall is active) as lock files. What happens is that, when you run
/etc/init.d/bastille-firewall start, the firewall starts, but from then,
/etc/init.d/bastille-firewall fails
everytime, unless you delete /var/lock/bastille by hand.
Fast workaround: add the -p option to mkdir in line 63:
mkdir -p -m 0700 ${LOCKDIR} 2>/dev/null
Solution: move the lock file /var/lock/bastille/bastille-firewall somewhere
out of /var/lock/bastille/.
Anyway, neither of these two locks seems very useful to me at first sight,
unless they are used by some other
script, so perhaps you should think about dropping them completely
-- System Information:
Debian Release: 5.0.2
APT prefers stable
APT policy: (990, 'stable'), (500, 'oldstable'), (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.26-2-686 (SMP w/1 CPU core)
Locale: LANG=de_DE.UTF8, LC_CTYPE=de_DE.UTF8 (charmap=UTF-8) (ignored: LC_ALL
set to de_DE.UTF8)
Shell: /bin/sh linked to /bin/dash
Versions of packages bastille depends on:
ii libcurses-perl 1.23-1+b1 Curses interface for Perl
ii perl [perl5] 5.10.0-19 Larry Wall's Practical Extraction
Versions of packages bastille recommends:
ii bind9-host [host] 1:9.5.1.dfsg.P3-1 Version of 'host' bundled with BIN
ii psad 2.1.3-1.1 The Port Scan Attack Detector
ii whois 4.7.30 an intelligent whois client
Versions of packages bastille suggests:
ii acct 6.4~pre1-6 The GNU Accounting utilities for p
ii perl-tk 1:804.028-1+b1 Perl module providing the Tk graph
-- no debconf information
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
