× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



What I usually do in cases like this is just to create a shell script that
dumps the data I need and swap out the old one:

mv /QOpenSys/usr/bin/X11/xauth /QOpenSys/usr/bin/X11/xauth.bak

/QOpenSys/usr/bin/X11/xauth.test:

#!/bin/sh
LOGFILE=~kadler/xauth.log

echo "args: $@" >> $LOGFILE
echo "stdin:" >> $LOGFILE
cat - >> $LOGFILE
echo >> $LOGFILE
# end xauth.test

ln -s /QOpenSys/usr/bin/X11/xauth.test /QOpenSys/usr/bin/X11/xauth



"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx> wrote on 03/24/2016
03:12:49 PM:

From: Justin Dearing <zippy1981@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 03/24/2016 03:13 PM
Subject: Re: Trying to use TRCINT to look at PASE processes
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

Aaron,

The error is when I log in I get
/QOpenSys/usr/bin/X11/xauth: (stdin):1: 1356-373 unknown command
"Usage:"
/QOpenSys/usr/bin/X11/xauth: (stdin):2: 1356-373 unknown command "-n"
$


I'm doing X11 forwarding so I can run (for example) /QOpenSys/usr/
bin/X11/xterm
and display it on my windows machine.

Justin

On Thu, Mar 24, 2016 at 4:09 PM Aaron Bartell <aaronbartell@xxxxxxxxx>
wrote:

​What is the error?

The most common error with SSH (that I come across) is the IBM i
profile
can't be more than chars 8 long.​

Also, here's another approach to debugging SSH issues:
http://bit.ly/ibmi-syslogd-debug

Aaron Bartell
litmis.com - Services for open source on IBM i


On Thu, Mar 24, 2016 at 2:59 PM, Justin Dearing <zippy1981@xxxxxxxxx>
wrote:

On Thu, Mar 24, 2016 at 3:44 PM Aaron Bartell
<aaronbartell@xxxxxxxxx>
wrote:

Since you said "sshd" instead of "STRTCPSVR *SSHD", am I safe to
assume
you
are actually using the sshd command in PASE from a shell?


Aaron,

A most fortutious and interesting caveat you make. Actually, I was
STRTCPSVR *SSHD and it did not work. To get some more information I
was
doing "ssh -p 8022 -d" on the command line to start a second session
so I
could get all the server debug messages to match up with the client
messages I got from with plink -v -X -p 8022 user@servername

Ironically, it works when running it in debug mode. Now, to be clear
Ive
done STRTCPSVR *SSHD/ENDTCPSVR *SSHD many times, logged out of my
putty
sessions and made sure all sshd instances were dead with ps between
ENDTCPSVR and STRTCPSVR. I'm sure I don't have to tell you that
STRTCPSVR
*SSHD will actually create sshd pids in PASE.

Anyway, I need to run, but I am going to read all that, digest it,
and
let
you know if it is helpful.

Justin

If so, I
recently went through an extensive PASE debugging experience**
that
gave
me
more insight concerning how to debug PASE issues using dbx***.

**Special thanks to Tony Cairns for taking the time. The entire
experience
is documented here: http://bit.ly/ibmi-git-mmap-failed
*** http://bit.ly/aix-dbx

Aaron Bartell
litmis.com - Services for open source on IBM i


On Thu, Mar 24, 2016 at 2:15 PM, Justin Dearing
<zippy1981@xxxxxxxxx>
wrote:

First of all, I'm probably using the wrong tool for this job.
What
do I
really want to do:
I'm debugging an error when sshd starts up
/QOpenSys/usr/bin/X11/xauth. I
want to know whats being piped to it from stdin. If I could know
the
job
name of any given dead PASE process and do a WRKJOB on it, that
will
likely
give me what I need.

Now, what I tried to do is this: TRCINT SET(*ON) TRCTYPE(*PASE)
TRCTBL(PASETRC)

I then typed a few unix command in a ssh session

Unfortunately, I don't see the table get created with this SQL:
SELECT TABLE_SCHEMA || '.' || TABLE_NAME FROM QSYS2.SYSTABLES
WHERE NAME ='PASETRC'

Luckily, I was able to create a spool file with TRCINT SET(*OFF)
TRCTBL(PASETRC)

However, searching for the spool file did not turn up either the
commands I
ran or anything like exec/execv/shell/cmd, which would be what I
would
expect the API calls to be to start a process.

So my two questions are:

1. Would this trace even record all the started processes in
PASE,
and
if
not how do I capture them?
2. How do I query the trace information with SQL instead of
looking
at
spool files.

Justin
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L)
mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.