On 13/03/2014 1:11, Donald Likens wrote:
We have 4 different non-sysplex LPARs all maintained by a sand box LPAR. We
install on the sand box LPAR and then copy volumes and files to the other
systems to roll out the maintenance. I recently installed a serverpac and
decided to make the /etc and /var filesystems SYS1 residing on the SYSRES. In
this way, whenever IBM updates these directories with maintenance it will
automatically be implemented on the other systems with the SYSRES volume copy.
My concern is that any changes to these directories will be lost as new SYSRES
copies are rolled out. So far looking at what is on these directories it is
either static or updated all the time (like a pid number).
My question is how do you handle these file systems in your shop. Note: Sharing
them is not an option, so if you share these directories across LPARs please do
not respond.
I personally wouldn't put them on the sysres. My preference would be to
follow conventional unix practices as much as possible for filesystems.
That should allow future software installations with minimum surprises.
Conceptually, /etc is like SYS1.PARMLIB - it contains system
configuration. I think it could live on the sysres in the same way that
SYS1.PARMLIB can live on the sysres, but it means that processes need to
be developed to manage that. It's probably simpler off the sysres.
/var is a data directory. It contains program data, log files, temporary
files that should survive an IPL and so on. On conventional unix systems
it is often the default location for databases, websites and mail
waiting to be delivered etc.
Regularly or occasionally replacing the contents of /var seems like it
is setting yourself up for trouble if you ever install software that
assumes conventional usage of the /var filesystem.
I would also suggest that only read-only filesystems should be on the
sysres. That probably rules out /var.
Regards
Andrew Rowley
--
[email protected]
+61 413 302 386
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
