Re: [Thinstation-developer] DISPLAY

[Jeremy P. <p.e...@gm...>]

Thanks for the reply. Did you see the 2nd part of my reply? Your
suggestion will not do what you intend. However, I don't think it is
needed, as I've said. Here's why:

1. any nx session defined using the thinstation.conf mechanism i.e.
using SESSION_0_TYPE=NX; SESSION_0_SCREEN=1; etc... will already have
an (correct) entry in the session file (/tmp/ts/session) that is
generated by /etc/init.d/session.

2. nx_menu generates an entry in the session file for _other_ nx
configurations (placed in the image at build time) that are not
defined at all in thinstation.conf (and hence have no session number
associated with them).

Am I making sense?

Also, I've revised my patch because the nx session file extension is
now .nxs instead of .conf. It is now reflected here as well.

-Jeremy

On 7/28/06, Miles Roper <mr...@xt...> wrote:
> i think so :o)
>
> if....
>
> SESSION_0_SCREEN=1
> SESSION_0_TYPE="NX"
> etc...
>
> when it defines the entries in the session file, SCREEN will be still set as the default, 0, this is
> only set when parsing the normal session file through etc/init.d/session.  When calling nx.init
> which calls nx_menu, which adds an entry to the session file, SCREEN will be 0.  Thats why we need
> to modify the nx.init file to check if the SESSION_X_SCREEN has been defined.  So your patch is
> fine, but to work for a non-standard screen setup it needs above.  You can test if you want without
> the patch and see if it works.
>
>
> Jeremy Parrish wrote:
> > On 7/27/06, Miles Roper <mr...@xt...> wrote:
> >> this won't work in all situations, as nx_menu could be called when the SCREEN should be different
> >> from the default "0".  This wouldn't get picked up in the init script, but would when the session starts
> >
> > Is that really the case (could you give me an example)? I think using
> > the default $SCREEN is the desired effect for nx_menu, as it just
> > generates a "generic" session based on your NX configuration files so
> > that it will show up in the wm/replimenu menus. i.e. they don't have a
> > session number associated with them.
> >
> >> so....
> >>
> >> so need to use this patch, please test and report back if you have time.
> >>
> >> in nx.init, line 85
> >>
> >>          done
> >>
> >> INSERT
> >>          # Checks to see if different default screen is defined
> >>          if [ -n "`eval echo '$SESSION_'$x'_SCREEN'`" ] ; then
> >>                  SCREEN="`eval echo '$SESSION_'$x'_SCREEN'`"
> >>          fi
> >>
> >> FINISH INSERT
> >>
> >> nx_menu
> >>
> >
> > Maybe I'm wrong, but it looks like line 85 (and the call to nx_menu)
> > are outside the while loop that loops through the sessions -- as they
> > probably should be or else it'd generate a lot of redundant session
> > entries. The code you suggest will most likely not do anything since
> > $x will be 1 + the highest session number when it reaches that point.
> >
> > That's my interpretation anyway. YMMV.
> >
> > -Jeremy
> >
> > -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share your
> > opinions on IT & business topics through brief surveys -- and earn cash
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Thinstation-developer mailing list
> > Thi...@li...
> > https://lists.sourceforge.net/lists/listinfo/thinstation-developer
> >
>
>