KP Kirchdörfer wrote:
snip
Long Term:
I'd also like to see the configuration directory approach taken to
logrotate (similar to my RedHat distributions, which already do
this), and even inetd (switch to xinetd?). Using files in a
configuration directory makes the seperation of configuration
Charles Steinkuehler wrote:
For instance, just because your /var/cache maybe full, do you want to
arbitrarily purge /var/log files?
Not for an instant do I suggest that such complexity is insurmountable;
rather, it should be clear that this is far more involved and requires a
new
I will at least apply the one line fix in the next release. For the
future,
I'd like to see support for a configuration directory. There would be
some
default entries, while add-on packages could drop entries into the
/etc/purge.d (or whatever) directory, with customizations for any
Am Dienstag, 22. Januar 2002 19:39 schrieb Michael D. Schleif:
KP Kirchdörfer wrote:
Am Dienstag, 22. Januar 2002 19:21 schrieben Sie:
KP Kirchdörfer wrote:
Am Montag, 21. Januar 2002 15:54 schrieb Charles Steinkuehler:
I will at least apply the one line fix in the next release.
Charles Steinkuehler wrote:
I will at least apply the one line fix in the next release. For the
future,
I'd like to see support for a configuration directory. There would be
some
default entries, while add-on packages could drop entries into the
/etc/purge.d (or whatever)
I think ideally, checkfreespace would have to determine which filesystem
the
purge-able files reside on. One of my major goals for a new
distribution is
to gracefully support flexible mount-points. While the purge-able files
may
not change, and so could be included as part of the
Build a single sed command to delete any un-desired file specs, and strip
off the purge-level...start with /^1/!d (where one is the desired purge
level), add delete commands for each sub-mount point (ie
\:var/log/httpd:d),
and end with a substute command to strip the leading field ( s/^[0-9
For instance, just because your /var/cache maybe full, do you want to
arbitrarily purge /var/log files?
Not for an instant do I suggest that such complexity is insurmountable;
rather, it should be clear that this is far more involved and requires a
new paradigm, other than:
KP Kirchdörfer wrote:
Am Sonntag, 20. Januar 2002 03:18 schrieb Michael D. Schleif:
KP Kirchdörfer wrote:
Am Donnerstag, 17. Januar 2002 04:15 schrieb Michael D. Schleif:
I'll probably try to get the script to check *ALL* currently
mounted, writable file-systems...maybe
Am Donnerstag, 17. Januar 2002 04:15 schrieb Michael D. Schleif:
Charles Steinkuehler wrote:
Following problem:
Using Dachstein and creating a separate ramdisk /dev/ram1 for
/var/log malfunctions lrp.conf spacecheck.
I think the spacecheck intention is to monitor /var/log, cause
Charles Steinkuehler wrote:
Following problem:
Using Dachstein and creating a separate ramdisk /dev/ram1 for
/var/log malfunctions lrp.conf spacecheck.
I think the spacecheck intention is to monitor /var/log, cause there
are the most changes in file size during the routers lifetime
Following problem:
Using Dachstein and creating a separate ramdisk /dev/ram1 for
/var/log malfunctions lrp.conf spacecheck.
I think the spacecheck intention is to monitor /var/log, cause there
are the most changes in file size during the routers lifetime and
running out of space in /var/log
Hello;
Following problem:
Using Dachstein and creating a separate ramdisk /dev/ram1 for
/var/log malfunctions lrp.conf spacecheck.
I think the spacecheck intention is to monitor /var/log, cause there
are the most changes in file size during the routers lifetime and
running out of space in
13 matches
Mail list logo
