Admins

Stan had said:
>I think the prudent thing to do is back up the core files. I was in a
>situation a few years ago where a web server's disk crashed. Every bit of
>data for that server's users was recovered, except for one user. Yup, that
>user had the dumb luck to host a web site called "core". Since that
>incident, I would just as soon back up those few core files than not. A
>better solution is to find out what's generating core files on your server
>and fix it if at all possible.

"Ouch" about the core web site!  At our site, we support several
environments, one of them being a Development environment. I agree it is
wise to determine what is causing the cores and fix it. Also, it may be
prudent to backup core files, but I see 1GB core files quite often and for
a 500 client backup domain, it probably adds up to a few terabytes of data
over the course of one year.  I know there are some good jokes I could
insert here, but that is what it is. We have a 3 year retention for full
backups, so it can save a decent amout of tapes.  One possibility is to
have a cron job find cores, email the owner of the core file and remove
ones older than 2 weeks.

>From the nsr man page and what Darren wrote, it seems like a bug with
directives. I will check with Legato and post later.

Cheers,
Pat

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=