03-13-2019
Unfortunately I inherited an old version of Gentran EDI software that runs it's application on an NFS share. It was on an IBM v7000 and we migrated to a regular Ubuntu Linux server running NFS server and I've migrated several successful shares with no issues. However on this particular share with the application it will not start that application as version 3 NFS on Solaris client. If I go to version 4 it will start the application but in degraded mode and having all kinds of ACL issues.
Process is started manually but within the NFS share just running an application command that's compiled for Solaris. You start it running a shell program and it calls this executable. I traced it down to the archive portion I started this thread with. I can write to that folder and everything but I keep getting this error in the truss output.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
once I run the debug command for a program, I can't get back to the prompt afterwards. I'm sure there is some escape sequence that will get me back there, but I don't know what it is. Anyone know?--thanks--AJ (3 Replies)
Discussion started by: AJA
3 Replies
2. UNIX for Dummies Questions & Answers
I have been trying to perform the following command without success
truss -feo truss.out ftp -nvd < ftpcmds.txt
The error I am getting is
"truss: cannot trace set_id or unreadable object file /usr/bin/ftp"
I have tested the file that contains the ftp commands and it works fine with
ftp... (5 Replies)
Discussion started by: canman
5 Replies
3. Shell Programming and Scripting
Hi,
Can you please let me know if there's any debug command for perl scripts
like
set -x for shell scripts (2 Replies)
Discussion started by: dayanandra
2 Replies
4. Programming
If an executalbe file has several parameters, gdb can not pass parameters correctly. Let us see:
run:
./executablefile1 agr1 arg2 arg3
debug:
gdb executablefile1
run executalbefile1 arg1 arg2 arg3
then argv : executablefile1
argv : executablefile
argv : arg1
... (3 Replies)
Discussion started by: cdbug
3 Replies
5. Shell Programming and Scripting
pariosd -status
NodeName ID ROLE STATE PROTECTION
---------------------------------------------------------------------------
tn320_scm10 10 ACTIVE UP No Protection
tn320_scm11 11 UNKNOWN UNKNOWN
LocalApps ... (5 Replies)
Discussion started by: hariprasad123
5 Replies
6. Solaris
Is there a way to debug the startup on a VT100 running Solaris 5? I have a problem related to file attributes that are resetting to there prior settings when the machine reboots. (3 Replies)
Discussion started by: jimcz2it
3 Replies
7. UNIX for Advanced & Expert Users
Hi,
I am trying to set ulimit for soft stack unlimited, but this is not taking effect, after tracing the ulimit -a unlimited command, the below output was generated, which i am unable to comprehend. Could any one help me with this?
prcbap1-r10prod: truss -d ulimit -s unlimited
Tue Dec 30... (2 Replies)
Discussion started by: NasirAbbasi
2 Replies
8. Shell Programming and Scripting
Hi,
I am using this command fuser_result=`fuser -f /web/$1/admin-*/logs/access` to get the parent pid of the process.
However, The output differs and at times it shows two pids instead of one thus failing the logic of my script. See output below:
bash-3.2$ fuser -f... (3 Replies)
Discussion started by: mohtashims
3 Replies
kill.d(1m) USER COMMANDS kill.d(1m)
NAME
kill.d - snoop process signals as they occur. Uses DTrace.
SYNOPSIS
kill.d
DESCRIPTION
kill.d is a simple DTrace program to print details of process signals as they are sent, such as the PID source and destination, signal num-
ber and result.
This program can be used to determine which process is sending signals to which other process.
Since this uses DTrace, only users with root privileges can run this command.
EXAMPLES
Default output, print process signals as they are sent.
# kill.d
FIELDS
FROM source PID
COMMAND
source command name
TO destination PID
SIG destination signal ("9" for a kill -9)
RESULT result of signal (-1 is for failure)
DOCUMENTATION
See the DTraceToolkit for further documentation under the Docs directory. The DTraceToolkit docs may include full worked examples with ver-
bose descriptions explaining the output.
EXIT
kill.d will run forever until Ctrl-C is hit.
AUTHOR
Brendan Gregg [Sydney, Australia]
SEE ALSO
dtrace(1M), truss(1)
version 0.90 May 14, 2005 kill.d(1m)