SEO

Solaris 2.9 Generic_117171-09 on Ultra AX, patch 114880-06 installed
SunRay Server 2.0.

Following command:
../utresdef -a -c TEST 1024x576 TESTNAME
results in:
"This option is not yet available"

Did anybody get this command working?

Unfortunately no example in doc.

Thanks in advance...

Thorsten

"Thorsten Kubis" <altermann40@yahoo.com> wrote:
> Solaris 2.9 Generic_117171-09 on Ultra AX, patch 114880-06 installed
> SunRay Server 2.0.
>
> Following command:
> ./utresdef -a -c TEST 1024x576 TESTNAME
> results in:
> "This option is not yet available"

Last time I asked, I was told that the message is correct.


Thomas

"Thomas Dehn" <thomas-usenet@arcor.de> wrote in message news:<2tl12eF1va5fjU2@uni-berlin.de>...
> "Thorsten Kubis" <altermann40@yahoo.com> wrote:
> > Solaris 2.9 Generic_117171-09 on Ultra AX, patch 114880-06 installed
> > SunRay Server 2.0.
> >
> > Following command:
> > ./utresdef -a -c TEST 1024x576 TESTNAME
> > results in:
> > "This option is not yet available"
>
> Last time I asked, I was told that the message is correct.
>
>
> Thomas

Does that mean that I am not able to create a new resolution?
utresdef without any parameter does not show me the added resolution.

Thorsten

"Thorsten Kubis" <altermann40@yahoo.com> wrote:
> "Thomas Dehn" <thomas-usenet@arcor.de> wrote in message
news:<2tl12eF1va5fjU2@uni-berlin.de>...
> > "Thorsten Kubis" <altermann40@yahoo.com> wrote:
> > > Solaris 2.9 Generic_117171-09 on Ultra AX, patch 114880-06 installed
> > > SunRay Server 2.0.
> > >
> > > Following command:
> > > ./utresdef -a -c TEST 1024x576 TESTNAME
> > > results in:
> > > "This option is not yet available"
> >
> > Last time I asked, I was told that the message is correct.
>
> Does that mean that I am not able to create a new resolution?

I think so. There is an undocumented, complex method
to change the fallback resolution, but thats all I know.


Thomas

"Thomas Dehn" <thomas-usenet@arcor.de> wrote:
> "Thorsten Kubis" <altermann40@yahoo.com> wrote:
> > "Thomas Dehn" <thomas-usenet@arcor.de> wrote:
> > > "Thorsten Kubis" <altermann40@yahoo.com> wrote:
> > > > ./utresdef -a -c TEST 1024x576 TESTNAME
> > > > results in:
> > > > "This option is not yet available"
> > >
> > > Last time I asked, I was told that the message is correct.
> >
> > Does that mean that I am not able to create a new resolution?
>
> I think so. There is an undocumented, complex method
> to change the fallback resolution, but thats all I know.

In SRSS 2.0 there's an experimental mechanism called "altdispconfig" that
will let you define new monitor timings. It's not documented because it's
not intended to be a permanent part of the product, it will go away in the
release after 3.0. Your Sun SE should be able to get information on
altdispconfig if you need it. If you provide details of what you're
trying to do (including monitor specs or model ID) then your SE might be
also able to get a timing definition for you.

In SRSS 3.0 the utresef command does allow you to create new timings.
This went into 3.0 after the documentation cutoff so the information isn't
in the man page or the docs. As with altdispconfig, your SE should be able
to get the details for you.

OttoM.
--
ottomeister (no longer @my-deja, now @mail.com)

Disclaimer: These are my opinions. I do not speak for my employer.

ottomeister@my-deja.com (Ottomeister) wrote in message news:<ddc8b54b.0410221323.56abcd94@posting.google. com>...
> "Thomas Dehn" <thomas-usenet@arcor.de> wrote:
> > "Thorsten Kubis" <altermann40@yahoo.com> wrote:
> > > "Thomas Dehn" <thomas-usenet@arcor.de> wrote:
> > > > "Thorsten Kubis" <altermann40@yahoo.com> wrote:
> > > > > ./utresdef -a -c TEST 1024x576 TESTNAME
> > > > > results in:
> > > > > "This option is not yet available"
> > > >
> > > > Last time I asked, I was told that the message is correct.
> > >
> > > Does that mean that I am not able to create a new resolution?
> >
> > I think so. There is an undocumented, complex method
> > to change the fallback resolution, but thats all I know.
>
> In SRSS 2.0 there's an experimental mechanism called "altdispconfig" that
> will let you define new monitor timings. It's not documented because it's
> not intended to be a permanent part of the product, it will go away in the
> release after 3.0. Your Sun SE should be able to get information on
> altdispconfig if you need it. If you provide details of what you're
> trying to do (including monitor specs or model ID) then your SE might be
> also able to get a timing definition for you.
>
> In SRSS 3.0 the utresef command does allow you to create new timings.
> This went into 3.0 after the documentation cutoff so the information isn't
> in the man page or the docs. As with altdispconfig, your SE should be able
> to get the details for you.
>
> OttoM.
Thank you Otto!

Currently we are using altdispconf at our customer with SRSS 1.2.
We are going to port to 2.0.
My SE told me to use the new commands in 2.0. So I have to wait for
the undocumented informations from Sun :-(
So the question might be to use 2.0 or 3.0. But our customer will not be happy
to using a beta software.

Does anybody have experiences with performance issues on 3.0?

Thorsten

altermann40@yahoo.com (Thorsten Kubis) wrote in message news:<89d7279.0410230111.5e14c097@posting.google.c om>...
> ottomeister@my-deja.com (Ottomeister) wrote in message news:<ddc8b54b.0410221323.56abcd94@posting.google. com>...
> > In SRSS 2.0 there's an experimental mechanism called "altdispconfig" that
> > will let you define new monitor timings. It's not documented because it's
> > not intended to be a permanent part of the product, it will go away in the
> > release after 3.0.
> <snip>
> Currently we are using altdispconf at our customer with SRSS 1.2.
> We are going to port to 2.0.
> My SE told me to use the new commands in 2.0. So I have to wait for
> the undocumented informations from Sun :-(
> So the question might be to use 2.0 or 3.0. But our customer will not be happy
> to using a beta software.

You can continue to use altdispconfig with 2.0 and 3.0. It will
disappear in a release after 3.0, so at some point after your customer
has upgraded to 3.0 you should switch over to using utresdef and
utresadm. That transition should be easy because the format of the
timing definition for utresdef is the same as the format used by
altdispconfig.

OttoM.
--
ottomeister (no longer @deja.com, now @mail.com)

Disclaimer: These are my opinions. I do not speak for my employer.

ottomeister@my-deja.com (Ottomeister) wrote in message news:<ddc8b54b.0410231522.5ab6849b@posting.google. com>...
> altermann40@yahoo.com (Thorsten Kubis) wrote in message news:<89d7279.0410230111.5e14c097@posting.google.c om>...
> > ottomeister@my-deja.com (Ottomeister) wrote in message news:<ddc8b54b.0410221323.56abcd94@posting.google. com>...
> > > In SRSS 2.0 there's an experimental mechanism called "altdispconfig" that
> > > will let you define new monitor timings. It's not documented because it's
> > > not intended to be a permanent part of the product, it will go away in the
> > > release after 3.0.
> > <snip>
> > Currently we are using altdispconf at our customer with SRSS 1.2.
> > We are going to port to 2.0.
> > My SE told me to use the new commands in 2.0. So I have to wait for
> > the undocumented informations from Sun :-(
> > So the question might be to use 2.0 or 3.0. But our customer will not be happy
> > to using a beta software.
>
> You can continue to use altdispconfig with 2.0 and 3.0. It will
> disappear in a release after 3.0, so at some point after your customer
> has upgraded to 3.0 you should switch over to using utresdef and
> utresadm. That transition should be easy because the format of the
> timing definition for utresdef is the same as the format used by
> altdispconfig.
>
> OttoM.

Unfortunately I have to disagree. Please have a look at
/opt/SUNWut/lib/utdtsession and uncomment the debug line. Search for utresexec
and see what´s going on. Sigh....So in future everybody has to by a consultant
when using a piece of software. :-((

Thorsten

altermann40@yahoo.com (Thorsten Kubis) wrote in message news:<89d7279.0410242345.2cf8a3ce@posting.google.c om>...
> ottomeister@my-deja.com (Ottomeister) wrote in message news:<ddc8b54b.0410231522.5ab6849b@posting.google. com>...
> > You can continue to use altdispconfig with 2.0 and 3.0. It will
> > disappear in a release after 3.0, so at some point after your customer
> > has upgraded to 3.0 you should switch over to using utresdef and
> > utresadm. That transition should be easy because the format of the
> > timing definition for utresdef is the same as the format used by
> > altdispconfig.
>
> Unfortunately I have to disagree. Please have a look at
> /opt/SUNWut/lib/utdtsession and uncomment the debug line. Search for utresexec
> and see what´s going on. Sigh....So in future everybody has to by a consultant
> when using a piece of software. :-((

If you want to use altdispconfig with SRSS 2.0 or 3.0 then you have to
mkae utresexec non-executable, or rename it to something else so that the
utdtsession script can't find it. The reasoning was that it'd be too
confusing to have both mechanisms working simultaneously. If that's a
big problem then you could file a bug asking for both mechanisms to be
allowed. It would be straightforward to give 'utresexec' its chance and
then let 'altdispconfig' have a go if 'utresexec' did not wish to modify
the unit's monitor timing.

OttoM.
--
ottomeister (no longer @my-deja, now @mail.com)

Disclaimer: These are my opinions. I do not speak for my employer.