Whether tis nobler.
Just wondering if (excepting the existing zones thread) there are any
compelling arguments to keep /var as it's own filesystem for your typical
Solaris server. Web servers and the like.
Or arguments against it.
--
This message posted from opensolaris.org
vincent_b_...@yahoo.com said:
Just wondering if (excepting the existing zones thread) there are any
compelling arguments to keep /var as it's own filesystem for your typical
Solaris server. Web servers and the like.
Well, it's been considered a best practice for servers for a lot of
years to
Vincent Fox wrote:
Whether tis nobler.
Just wondering if (excepting the existing zones thread) there are any
compelling arguments to keep /var as it's own filesystem for your typical
Solaris server. Web servers and the like.
IMHO, the *only* good reason to create a new file system
Vincent Fox wrote:
Whether tis nobler.
Just wondering if (excepting the existing zones thread) there are any
compelling arguments to keep /var as it's own filesystem for your typical
Solaris server. Web servers and the like.
Or arguments against
with zfs it's easy to set quotas so
Marion Hakanson wrote:
Personally, I'd like to place a limit on /var/core/; That's the only
consistent out of disk space cause I've seen on our Solaris-10 systems,
and that happens whether /var/ is separate or not. Maybe /var/crash/
as well.
You can specify the volsize on /rpool/dump
It just seems like in a typical ZFS root install the need for a separate /var
is difficult for me to justify now. By default there are no quotas or
reservations set on /var. Okay I set them.
I have a monitoring system able to tell me when disks are getting full. It
seems easier to say just
vf == Vincent Fox vincent_b_...@yahoo.com writes:
vf the need for a separate /var is difficult for me to justify
vf now.
so long as you keep the word ``me'' in there! great that you don't
need it, but it's not difficult to justify.
pgp8rJMe1rUqs.pgp
Description: PGP signature
Miles Nordin wrote:
ic == Ian Collins i...@ianshome.com writes:
Personally, I'd like to place a limit on /var/core/;
ic You can specify the volsize on /rpool/dump on a zfs boot
ic system.
so what? so you can truncate each core dump to make it useless before
Hello,
Slightly off-topic, but only slightly.
With ZFS I tend to configure /var/cores as a separate zfs file system
with a quota set on it + coreadm configured that way so all cores go
to /var/cores.
This is especially useful with in-house applications running on
servers.
--
Best regards,
On Fri, Dec 12, 2008 at 12:04:39AM +, Robert Milkowski wrote:
Slightly off-topic, but only slightly.
With ZFS I tend to configure /var/cores as a separate zfs file system
with a quota set on it + coreadm configured that way so all cores go
to /var/cores.
This is especially useful with
Robert Milkowski wrote:
Hello,
Slightly off-topic, but only slightly.
With ZFS I tend to configure /var/cores as a separate zfs file system
with a quota set on it + coreadm configured that way so all cores go
to /var/cores.
While this might cause some issues with programs that expect or
11 matches
Mail list logo
