Excuse, but this is already accomplished by my .Xdefaults file.
On 4/11/06, Joachim Schipper <[EMAIL PROTECTED]> wrote:
> On Mon, Apr 10, 2006 at 10:54:50PM -0300, Gustavo Rios wrote:
> > Dear friends,
> >
> > i am running two xterm. When i run from any of them the "w" command i got
> > this:
> >
> > $ tty && w
> > /dev/ttyp0
> > 10:47PM up 8 mins, 2 users, load averages: 0.88, 0.50, 0.23
> > USER TTY FROM LOGIN@ IDLE WHAT
> > grios p0 :0.0 10:45PM 0 w
> > grios p1 :0.0 10:46PM 0 -sh
> > $
> >
> > $ tty && w
> > /dev/ttyp1
> > 10:48PM up 8 mins, 2 users, load averages: 0.75, 0.49, 0.23
> > USER TTY FROM LOGIN@ IDLE WHAT
> > grios p0 :0.0 10:45PM 0 -sh
> > grios p1 :0.0 10:46PM 0 w
> > $
> >
> >
> > Now, from xterm terminal running over ttyp1, i start a new terminal,
> > by means of rxvt. And the output from the same previous command
> > execution is totally different:
> >
> > $ tty && w
> > /dev/ttyp0
> > 10:50PM up 10 mins, 2 users, load averages: 0.34, 0.44, 0.25
> > USER TTY FROM LOGIN@ IDLE WHAT
> > grios p0 :0.0 10:45PM 0 w
> > grios p2 :0.0 10:48PM 0 -sh
> > $
> >
> > $ rxvt &
> > [1] 28321
> > $ tty && w
> > /dev/ttyp1
> > 10:49PM up 9 mins, 2 users, load averages: 0.56, 0.49, 0.26
> > USER TTY FROM LOGIN@ IDLE WHAT
> > grios p0 :0.0 10:45PM 0 -sh
> > grios p2 :0.0 10:48PM 0 -sh
> > $
> >
> > $ tty && w
> > /dev/ttyp2
> > 10:49PM up 10 mins, 2 users, load averages: 0.44, 0.47, 0.25
> > USER TTY FROM LOGIN@ IDLE WHAT
> > grios p0 :0.0 10:45PM 0 -sh
> > grios p2 :0.0 10:48PM 0 w
> > $
> >
> >
> > What i could not understand is: ttyp1 terminal was associated with a
> > xterm terminal. From that terminal, after starting a rxvt process,
> > that association was broken. Although i am still running xterm on
> > ttyp1, it is not shown on any of the three screen output. What i was
> > expecting it was to have an entry for the same login ("grios") on
> > ttyp1.
> >
> > Anyhow, it does not make any sense to me.
> >
> > Thanks a lot for your time and cooperation.
> >
> > My .Xdefaults has the following relevant parts:
> > *VT100.loginShell: true
> > *VT100.scrollBar: off
> > *VT100*colorULMode: on
> > *VT100*underLine: off
> > *VT100*colorBDMode: on
> > *VT100*colorUL: red
> > *VT100*colorBD: magenta
> > *VT100*font: -misc-*-*-*-normal--*-*-*-*-c-*-*-*
> > *VT100*background: black
> > *VT100*cursorBlink: true
> > *VT100*foreground: yellow
> > *VT100*cursorColor: green
> > *VT100*cursorOffTime: 200
> > *VT100*cursorOnTime: 200
> > *VT100.pointerColor: red
> > *VT100.pointerColorBackground: black
> >
> > XTerm.termName: xterm
> >
> > Rxvt.loginShell: true
> > Rxvt.scrollBar: off
> > Rxvt*colorUL: red
> > Rxvt*colorBD: magenta
> > Rxvt*font: -misc-*-*-*-normal--*-*-*-*-c-*-*-*
> > Rxvt*background: black
> > Rxvt*foreground: darkgrey
> > Rxvt*cursorColor: yellow
> > Rxvt.pointerColor: red
>
> Search the rxvt(1) page for 'utmp'. Essentially, unlike xterm, rxvt does
> not write to utmp by default. use +ut/utmpInhibit: false to change this
> behaviour, if desired.
>
> Joachim
