Your message dated Wed, 10 Oct 2007 07:27:45 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Closing old 'oops' bugs
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: oops
Version: 1.5.19.cvs.20010818-0.1
Severity: normal
Oops's storage should be in /var/cache rather than /var/spool. To quote the
FHS:
5.5 /var/cache : Application cache data
5.5.1 Purpose
/var/cache is intended for cached data from applications. Such data is
locally generated as a result of time-consuming I/O or calculation. The
application must be able to regenerate or restore the data. Unlike
/var/spool, the cached files can be deleted without data loss. The data must
remain valid between invocations of the application and rebooting the
system.
Files located under /var/cache may be expired in an application specific
manner, by the system administrator, or both. The application must always be
able to recover from manual deletion of these files (generally because of a
disk space shortage). No other requirements are made on the data format of
the cache directories.
BEGIN RATIONALE
The existence of a separate directory for cached data allows system
administrators to set different disk and backup policies from other
directories in /var.
END RATIONALE
[and later]
5.14 /var/spool : Application spool data
5.14.1 Purpose
/var/spool contains data which is awaiting some kind of later processing.
Data in /var/spool represents work to be done in the future (by a program,
user, or administrator); often data is deleted after it has been
processed.
-- System Information
Debian Release: testing/unstable
Kernel Version: Linux arrakis 2.4.19-ck7-rmap #7 Thu Nov 14 22:55:25 EST 2002
i686 unknown unknown GNU/Linux
Versions of the packages oops depends on:
ii debconf 1.2.16 Debian configuration management system
ii libc6 2.3.1-5 GNU C Library: Shared libraries and Timezone
ii libdb2 2.7.7.0-8 The Berkeley database routines (run-time fil
ii libpcre3 3.9-1 Philip Hazel's Perl Compatible Regular Expre
--- Begin /etc/oops/oops.cfg (modified conffile)
nameserver 127.0.0.1
bind 192.168.5.1
http_port 8080
icp_port 3130
userid proxy
logfile /var/log/oops/oops.log
accesslog /var/log/oops/access.log
pidfile /var/run/oops/oops.pid
statistics /var/run/oops/oops_statfile
mem_max 64m
lo_mark 8m
default-expire-value 7
ftp-expire-value 7
max-expire-value 30
last-modified-factor 5
default-expire-interval 1
icp_timeout 1000
disk-low-free 3
disk-ok-free 5
force_http11
force_completion 75
maxresident 1m
insert_x_forwarded_for yes
insert_via yes
acl ADMINS src_ip 127.0.0.1
acl PURGE method PURGE
acl CONNECT method CONNECT
acl SSLPORT port 443
acl_deny PURGE !ADMINS
acl_deny CONNECT !SSLPORT
stop_cache ?
stop_cache cgi-bin
local-networks 10/8 192.168/16
group paco {
networks 192.168/16 127/8;
badports [0:79],110,138,139,513,[6000:6010] ;
miss allow;
http {
allow dstdomain * ;
}
}
group world {
networks 0/0;
badports [0:79],110,138,139,513,[6000:6010];
http {
deny dstdomain * ;
}
icp {
deny dstdomain * ;
}
}
storage {
path /var/spool/oops/storages/oops_storage ;
size auto;
}
module err {
# error reporting module
# template
template /etc/oops/err_template.html
# Language to use when generate Error messages
lang us
}
module passwd_file {
# password proxy-authentication module
#
# default realm, scheme and passwd file
# the only thing you really want to change is 'file' and 'template'
# you don't have to reconfigure oops if you only
# change content passwd file or template: oops authomatically
# reload file
realm oops
scheme Basic
file /etc/oops/passwd
template /etc/oops/auth_template.html
}
module pam {
realm oops
scheme Basic
service oops
template /etc/oops/auth_template.html
}
module redir {
# file - regex rules.
# each line consist of one or two fields (separated with white space)
# 1. regular expression
# 2. redirect-location
# if requested (by client) url match regex then
# if we have redirect-url then we send '302 Moved Temporary' to
# redirect-location
# if we have no redirect-location (i.e. we have no 2-nd field)
# then we send template.html (%R will be substituted by rule)
# or some default message if we have no template.
# you don't have to reconfigure oops each time
# you edit rules or template, they will be reloaded authomatically
file /etc/oops/redir_rules
template /etc/oops/redir_template.html
# This module can process requests which come on http_port
# and/or on different port. For example, you wish oops
# bind on two ports - 3128 and 3129, and all requests which come on
# port 3129 must pass through filters, and requests which come on port
# 3128 (common http_port) - not. Then you have to uncomment next line
# myport 3129
# which means exactly: bind oops to additional port 3129 and process
# requests which come on this port.
# myport can be in the next form:
# myport [{hostname|ip_addr}:]port
}
module oopsctl {
# path to oopsctl unix socket
socket_path /var/run/oops/oopsctl
# time to auto-refresh page (seconds)
html_refresh 300
}
module vary {
user-agent by_charset
accept-charset ignore
}
module berkeley_db {
##
# dbhome - directory where all DB indexes reside. Use full path
# this directory must exist.
# dbname - filename for index file. Use just filename (no full path)
##
dbhome /var/spool/oops/DB
dbname dburl
##
# This parameter specifies internal cache size of BerkeleyDB.
# Increase this parameter for best performance (if you have a lot of
memory).
# For example: db_cache_mem 64m
# Default and minimum value: 4m
#
# This memory pool is not part of memory pool, specified by mem_max
parameter.
# WARNING: the amount of RAM used by oops will be increased by the value of
# this parameter.
##
#db_cache_mem 4m
}
--- End /etc/oops/oops.cfg
--- End Message ---
--- Begin Message ---
Package: oops
Dear submitter,
Oops has been removed from debian/unstable on 19 Aug 2007 as documented
in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=438648. I'm
therefore closing the bugs as directed by the removal notification.
Thanks again for your interest in the oops package. I'm sorry that this
package was in such a bad shape, therefore I think removing it was the
best way to deal with the package.
--
Gruesse/greetings,
Reinhard Tartler, KeyID 945348A4
--- End Message ---
