We have developers who need access to application log and configuration data,
where the application is running in a zone. The actual request is usually for
a "Read-Only Unix Account".
We had, until recently been able to push them off due to SOX compliance issues.
Then one day we had a "bril
Jerry Jelinek wrote:
Menno Lageman wrote:
Hi,
doing a dry-run attach of a detached zone fails with the message
"zoneadm: missing or invalid brand" and exit code 1. Attaching the
zone for real succeeds though. I would expect the dry-run to succeed
too because the zone was created on this syst
Jerry Jelinek wrote:
Menno,
No, this is not correct. The dry-run spec in the arc case has
the correct definition.
The man page is in error and the way you were using it is
correct. This got broken with the brandz putback.
Yeah, I noticed that when I tried it between two systems instead of
Menno Lageman wrote:
Menno Lageman wrote:
Hi,
doing a dry-run attach of a detached zone fails with the message
"zoneadm: missing or invalid brand" and exit code 1. Attaching the
zone for real succeeds though. I would expect the dry-run to succeed
too because the zone was created on this syst
Menno Lageman wrote:
Hi,
doing a dry-run attach of a detached zone fails with the message
"zoneadm: missing or invalid brand" and exit code 1. Attaching the zone
for real succeeds though. I would expect the dry-run to succeed too
because the zone was created on this system so everything (pack
Menno Lageman wrote:
Hi,
doing a dry-run attach of a detached zone fails with the message
"zoneadm: missing or invalid brand" and exit code 1. Attaching the zone
for real succeeds though. I would expect the dry-run to succeed too
because the zone was created on this system so everything (pack
Jerry,
I don't know of a way to do this when you add a file system
in zonecfg using the fs resource. However, you can do this
by adding the device instead and modifying the zones vfstab
to mount the filesystem.
Actually, the intent was to run fsck(1M) in "check mode" using the -m
argument. S
Hi,
doing a dry-run attach of a detached zone fails with the message
"zoneadm: missing or invalid brand" and exit code 1. Attaching the zone
for real succeeds though. I would expect the dry-run to succeed too
because the zone was created on this system so everything (packages,
patches, networ
Detlef Drewanz wrote:
Thanks Jerry,
that makes very much sense to do that in this way. But we should keep in
mind that checking a filesystem during zonesboot might be required
(esspecially after a crash or a cluster switch).
With "add device" the raw device is in the zone available to do the
Thanks Jerry,
that makes very much sense to do that in this way. But we should keep
in mind that checking a filesystem during zonesboot might be required
(esspecially after a crash or a cluster switch).
With "add device" the raw device is in the zone available to do the fsck.
With "add fs" the
10 matches
Mail list logo
