<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Reflection X question in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/reflection-x-question/m-p/3012276#M911630</link>
    <description>This is a VERY common problem with Xwindow managers and has nothing to do with Reflection/X. And the problem is more pervasive than setting DTSOURCEPROFILE. What your users are expecting is a 'normal' Unix login which (for POSIX shells) first runs /etc/profile and then .profile (DTSOURCEPROFILE doesn't run /etc/profile). It turns out that the default for all terminal emulators is to startup without executing the usual profiles. To fix this, put this into every HOME directory for every user:&lt;BR /&gt;&lt;BR /&gt;echo "*loginShell: true" &amp;gt;&amp;gt; $HOME/.Xdefaults&lt;BR /&gt;&lt;BR /&gt;Now terminal emulators such as hpterm, xterm or dtterm will login as expected and will have the same profiles as a telnet connection.  You can also add additional resource settings for the emulators or other Xwindow applications. For example, the contents might look like this: &lt;BR /&gt;&lt;BR /&gt;*loginShell: true &lt;BR /&gt;HPterm*scrollBar: true &lt;BR /&gt;HPterm*saveLines: 10s &lt;BR /&gt;HPterm*background: navy &lt;BR /&gt;HPterm*foreground: white &lt;BR /&gt;Xterm*background: darkslateblue &lt;BR /&gt;Xterm*foreground: white &lt;BR /&gt;Xterm*saveLines: 10s &lt;BR /&gt;Xterm*scrollBar: true &lt;BR /&gt;Dtterm*saveLines: 10s &lt;BR /&gt;Dtterm*scrollBar: true &lt;BR /&gt;&lt;BR /&gt;and after adding these lines to .Xdefaults, all hpterm, xterm and dtterm windows will have a scroll bar plus 10 screens (800 lines) of history. hpterm will have a dark blue with white letter color scheme while xterm will have a more gray-blue background with white letters. dtterm will match the overall CDE color scheme. &lt;BR /&gt;&lt;BR /&gt;.Xdefaults is one of the many ways to set window decorations or resources. Look at the man page for hpterm and you'll see the dozens of options and resources that can be set. They can be set generically for every window or they can be set for a window that has a specific title. man X is a start but a good book on Xwindows will also be worthwhile.</description>
    <pubDate>Tue, 01 Jul 2003 17:30:04 GMT</pubDate>
    <dc:creator>Bill Hassell</dc:creator>
    <dc:date>2003-07-01T17:30:04Z</dc:date>
    <item>
      <title>Reflection X question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/reflection-x-question/m-p/3012271#M911625</link>
      <description>Has anyone seen a problem where when logging into an XDMC connection, it does not run the .profile file unless I type . $HOME/.profile? The last line in the .dtprofile is uncommented, so I thought it would work. Seems to work for some users and not others. Thanks.</description>
      <pubDate>Tue, 01 Jul 2003 14:19:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/reflection-x-question/m-p/3012271#M911625</guid>
      <dc:creator>Gerry Tully</dc:creator>
      <dc:date>2003-07-01T14:19:06Z</dc:date>
    </item>
    <item>
      <title>Re: Reflection X question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/reflection-x-question/m-p/3012272#M911626</link>
      <description>I assume you mean the line you mean is uncommented is:&lt;BR /&gt;&lt;BR /&gt;DTSOURCEPROFILE=true.&lt;BR /&gt;&lt;BR /&gt;However .profile is only valid for certain&lt;BR /&gt;shells which include korn shell, posix shell and bourne shell.  Users that have a default of c shell will not have .profile execute as&lt;BR /&gt;.cshrc is what it executes.  So for the users that it does not work for are they running csh (c shell) as their default?  Check by look at the entry at the end of /etc/passwd and see what shell they are set for.&lt;BR /&gt;</description>
      <pubDate>Tue, 01 Jul 2003 14:56:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/reflection-x-question/m-p/3012272#M911626</guid>
      <dc:creator>William Wong_2</dc:creator>
      <dc:date>2003-07-01T14:56:27Z</dc:date>
    </item>
    <item>
      <title>Re: Reflection X question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/reflection-x-question/m-p/3012273#M911627</link>
      <description>Are you sure some users are not reading their $HOME/.profile or are there statements in those affected user's .profile and specifically requires a tty device. Since the desktop reads .profile with no associated terminal, any read or echo statements will be lost. This is from the .dtprofile file itself:&lt;BR /&gt;&lt;BR /&gt;###   The desktop reads the .dtprofile and .profile/.login without an&lt;BR /&gt;###   associated terminal emulator such as xterm or dtterm. This means&lt;BR /&gt;###   there is no available command line for interaction with the user.&lt;BR /&gt;###   This being the case, these scripts must avoid using commands that&lt;BR /&gt;###   depend on having an associated terminal emulator or that interact&lt;BR /&gt;###   with the user. Any messages printed in these scripts will not be&lt;BR /&gt;###   seen when you log in and any prompts such as by the 'read' command&lt;BR /&gt;###   will return an empty string to the script. Commands that set a&lt;BR /&gt;###   terminal state, such as "tset" or "stty" should be avoided.&lt;BR /&gt;</description>
      <pubDate>Tue, 01 Jul 2003 15:07:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/reflection-x-question/m-p/3012273#M911627</guid>
      <dc:creator>John Dvorchak</dc:creator>
      <dc:date>2003-07-01T15:07:17Z</dc:date>
    </item>
    <item>
      <title>Re: Reflection X question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/reflection-x-question/m-p/3012274#M911628</link>
      <description>Everyone has the same shell. There is a line that runs a script . /oracle/env_functions.sh but it doesn't look like it is setting the environment from the script.</description>
      <pubDate>Tue, 01 Jul 2003 17:08:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/reflection-x-question/m-p/3012274#M911628</guid>
      <dc:creator>Gerry Tully</dc:creator>
      <dc:date>2003-07-01T17:08:23Z</dc:date>
    </item>
    <item>
      <title>Re: Reflection X question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/reflection-x-question/m-p/3012275#M911629</link>
      <description>One thing that immediately occurs to me is that if the home directories are auto-mounted, you may have problems with the automounter maps. This would explain why it seems to work for some and not for other seemimgly identical users.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 01 Jul 2003 17:24:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/reflection-x-question/m-p/3012275#M911629</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2003-07-01T17:24:42Z</dc:date>
    </item>
    <item>
      <title>Re: Reflection X question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/reflection-x-question/m-p/3012276#M911630</link>
      <description>This is a VERY common problem with Xwindow managers and has nothing to do with Reflection/X. And the problem is more pervasive than setting DTSOURCEPROFILE. What your users are expecting is a 'normal' Unix login which (for POSIX shells) first runs /etc/profile and then .profile (DTSOURCEPROFILE doesn't run /etc/profile). It turns out that the default for all terminal emulators is to startup without executing the usual profiles. To fix this, put this into every HOME directory for every user:&lt;BR /&gt;&lt;BR /&gt;echo "*loginShell: true" &amp;gt;&amp;gt; $HOME/.Xdefaults&lt;BR /&gt;&lt;BR /&gt;Now terminal emulators such as hpterm, xterm or dtterm will login as expected and will have the same profiles as a telnet connection.  You can also add additional resource settings for the emulators or other Xwindow applications. For example, the contents might look like this: &lt;BR /&gt;&lt;BR /&gt;*loginShell: true &lt;BR /&gt;HPterm*scrollBar: true &lt;BR /&gt;HPterm*saveLines: 10s &lt;BR /&gt;HPterm*background: navy &lt;BR /&gt;HPterm*foreground: white &lt;BR /&gt;Xterm*background: darkslateblue &lt;BR /&gt;Xterm*foreground: white &lt;BR /&gt;Xterm*saveLines: 10s &lt;BR /&gt;Xterm*scrollBar: true &lt;BR /&gt;Dtterm*saveLines: 10s &lt;BR /&gt;Dtterm*scrollBar: true &lt;BR /&gt;&lt;BR /&gt;and after adding these lines to .Xdefaults, all hpterm, xterm and dtterm windows will have a scroll bar plus 10 screens (800 lines) of history. hpterm will have a dark blue with white letter color scheme while xterm will have a more gray-blue background with white letters. dtterm will match the overall CDE color scheme. &lt;BR /&gt;&lt;BR /&gt;.Xdefaults is one of the many ways to set window decorations or resources. Look at the man page for hpterm and you'll see the dozens of options and resources that can be set. They can be set generically for every window or they can be set for a window that has a specific title. man X is a start but a good book on Xwindows will also be worthwhile.</description>
      <pubDate>Tue, 01 Jul 2003 17:30:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/reflection-x-question/m-p/3012276#M911630</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2003-07-01T17:30:04Z</dc:date>
    </item>
    <item>
      <title>Re: Reflection X question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/reflection-x-question/m-p/3012277#M911631</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://bizforums.itrc.hp.com/cm/QuestionAnswer/0,,0x826150011d20d6118ff40090279cd0f9,00.html" target="_blank"&gt;http://bizforums.itrc.hp.com/cm/QuestionAnswer/0,,0x826150011d20d6118ff40090279cd0f9,00.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;maybe some info in the above answers.&lt;BR /&gt;&lt;BR /&gt;Hope it helps,&lt;BR /&gt;&lt;BR /&gt;Robert-Jan.</description>
      <pubDate>Tue, 01 Jul 2003 17:30:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/reflection-x-question/m-p/3012277#M911631</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2003-07-01T17:30:20Z</dc:date>
    </item>
    <item>
      <title>Re: Reflection X question</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/reflection-x-question/m-p/3012278#M911632</link>
      <description>I came back to post the fix to the problem, and read some of the responses. Bill, you hit the nail on the head. I had to put that line into the .Xdefaults file and now everyone is happy (especially me). Thanks for everyones help.</description>
      <pubDate>Tue, 01 Jul 2003 17:36:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/reflection-x-question/m-p/3012278#M911632</guid>
      <dc:creator>Gerry Tully</dc:creator>
      <dc:date>2003-07-01T17:36:59Z</dc:date>
    </item>
  </channel>
</rss>

