Hi,
probably /etc/sysconfig/cron is what you are looking for:
## Path: System/Cron
## Description: days to keep old files in tmp-dirs, 0 to disable
## Type: integer
## Default: 0
## Config:
#
# cron.daily can check for old files in tmp-dirs. It will delete all files
#
Dear Linux on z community,
a few years ago we've introduced execute in place, which can be used to
save some memory by using z/VM DCSS segments. Since the size of
main memory for virtual servers has increased much faster than the size
of binary executables and libraries since, this technique has
Thanks for asking, Carsten.
I would expect, without samples to cite, that DCSS itself is often
used, XIP less so.
In my own experience, the lack of interest in XIP follows lack of
interest in shared R/O filesystems of any type. (XIP is technically
just as easy to maintain, if less well
a few years ago we've introduced execute in place, which can be used to
save some memory by using z/VM DCSS segments. Since the size of main
memory for virtual servers has increased much faster than the size of binary
executables and libraries since, this technique has become less attractive.
Our reason for not using it is the really high pressure of a very standardized
server farm.
In order to get this costeffective and useful you should have perhaps only
three versions
of readonly root filesystems used by all servers.
It would be only three systems to upgrade, maximum.
Since it is
Dear Carsten,
We are using DCSS as replacement of a paging device on physical DASD. Works
great. I also run the production environment from a DCSS with root and /usr
filesystem loaded.
So I consider it as a very valuable facility.
Kind regards,
Florian
On Tue, Feb 12, 2013 at 10:36 AM, Carsten
Hi Florian,
please note that the DCSS block device and its use for paging and/or
storing
file systems on it is not at risk of being discontinued.
Are any of your filesystems ext2 with -o xip?
with kind regards
Carsten Otte
System z firmware development / Boeblingen lab
---
Every revolution was
I have been wondering if appliances like Texas Memory System (TMS) changes
the requirements/direction of items like this?
http://www.ramsan.com/
Kurt Acker
IBM Smarter Planet, Smarter Data Centers
Virtualization and Enterprise System Management Technologies
On Tuesday, 02/12/2013 at 09:57 EST, David Boyes dbo...@sinenomine.net
wrote:
We don't use it due to the difficulty of creating and maintaining the
DCSS from
Linux over time.
Since neither of the major distros on Z integrated it into the system
management tooling, I suspect that it never got
IMO, as long as the user has to maintain the DCSS it will never catch on.
Exactly. It's beneficial, but the lack of tooling and implementation
integration makes it a PITA. We got plenty of those.
The software vendor must decide what should/shouldn't go into the DCSS,
not the sysprog. When
As a followup to a posting over on the IBM/VM mailing list about using
dasd_configure to bring a device online and create the necessary udev
rules, I wanted to contribute this as I think having a separate rule file
for every disk device attached to my guests is just wrong.
Personally, I haven't
Agreed.
-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
Alan Altmark
Sent: Tuesday, February 12, 2013 10:29 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Who's using execute in place?
On Tuesday, 02/12/2013 at 09:57 EST, David Boyes
Will your solution preserve read only attributes? I.e. if you bring all dasd
online with a single udev rule, will those linked as read only have the correct
read only attributes so the kernel knows that it cannot write to them?
Example of what I mean by correct read only attributes:
vmcp q v
13 matches
Mail list logo
