Re: [Veritas-bu] exclude_list - exclude core file but not core directory
Dave, To exclude all files with a given name, regardless of their directory path, just enter the name without a preceding slash. For example: "example" rather than "/example" Here is an example *exclude_list* --- # this is a comment line /tmp/example/dir/all /tmp/example/dir2only/ /usr/home/*/all_tmp /*/all_temp core -- Anurag > Date: Sun, 28 Aug 2011 19:31:28 -0500 > From: da...@graniteweb.com > To: veritas-bu@mailman.eng.auburn.edu > Subject: [Veritas-bu] exclude_list - exclude core file but not core directory > > Hello, > > I'm dealing with exclude_list for the umteenth time, and stumbled into a > classic problem. > > The examples in the docs have always shown excluding "core", which > excludes all core files AND core directories. Because of how you define > things, it is possible to exclude just directories by appending / (e.g., > core/), but there is no corresponding way that I can find to exclude > ONLY files named core. > > I can more or less accomplish what I need to by using an include_list > that contains "core/", but this will obviously add processing overhead > because it's going to build the initial list, drop excluded stuff, then > go back through all the excluded directories and look for all > directories named "core". I especially don't want the include list to > go back and re-add any core directories under other directories that I > have also excluded. > > For example: > exclude_list: > core > /dev > /sys > /mnt/auto > /var/mqm/ > /u[0-9]*/ > > If I have an include_list that looks like this: > core/ > > It will pick up any directories named core under: > /dev > /sys > /mnt/auto > /var/mqm/ > /u[0-9]*/ > > Which I do NOT want it to do. > > > Does anyone know if it's possible to define JUST files named core in the > exclude_list, so that an include_list is not necessary? If an > include_list is the only way to do it, is it possible to avoid the > re-adding under the directories I _do_ want to exclude? > > Thanks. > > -- > David Rock > dave...@graniteweb.com > ___ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] exclude_list - exclude core file but not core directory
Hello, I'm dealing with exclude_list for the umteenth time, and stumbled into a classic problem. The examples in the docs have always shown excluding "core", which excludes all core files AND core directories. Because of how you define things, it is possible to exclude just directories by appending / (e.g., core/), but there is no corresponding way that I can find to exclude ONLY files named core. I can more or less accomplish what I need to by using an include_list that contains "core/", but this will obviously add processing overhead because it's going to build the initial list, drop excluded stuff, then go back through all the excluded directories and look for all directories named "core". I especially don't want the include list to go back and re-add any core directories under other directories that I have also excluded. For example: exclude_list: core /dev /sys /mnt/auto /var/mqm/ /u[0-9]*/ If I have an include_list that looks like this: core/ It will pick up any directories named core under: /dev /sys /mnt/auto /var/mqm/ /u[0-9]*/ Which I do NOT want it to do. Does anyone know if it's possible to define JUST files named core in the exclude_list, so that an include_list is not necessary? If an include_list is the only way to do it, is it possible to avoid the re-adding under the directories I _do_ want to exclude? Thanks. -- David Rock dave...@graniteweb.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Warning Beta 7.5 OpsCenter
Symantec has never, ever supported upgrading anything to beta. Beta is a chance to preview the new software on a new system. Upgrades are not supported. I thought this was pointed out in the Beta Primer but I could be wrong. Never, ever install beta software in production (obviously). dave -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of WALLEBROEK Bart Sent: Wednesday, August 24, 2011 10:38 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Warning Beta 7.5 OpsCenter Just a small warning when you try to upgrade OpsCenter to 7.5 (beta 1). The upgrade wiped out our existing db and also crashed after the installation (a clean install works). I know this is only a beta 1 version but still. An installation, even an upgrade, should work before making it (beta) available. A case has been opened with Symantec support. Best Regards, Bart WALLEBROEK Backup Admin & Systems & Applications Management & Support Specialist Enterprise Applications Delivery - Infrastructure Management S.W.I.F.T. SCRL ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
