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
LEARN ABOUT MOJAVE
opensnoop
opensnoop(1m) USER COMMANDS opensnoop(1m)
NAME
opensnoop - snoop file opens as they occur. Uses DTrace.
SYNOPSIS
opensnoop [-a|-A|-ceFghstvxZ] [-f pathname] [-n name] [-p PID]
DESCRIPTION
opensnoop tracks file opens. As a process issues a file open, details such as UID, PID and pathname are printed out.
The returned file descriptor is printed, a value of -1 indicates an error. This can be useful for troubleshooting to determine if applia-
cions are attempting to open files that do not exist.
Since this uses DTrace, only users with root privileges can run this command.
OPTIONS
-a print all data
-A dump all data, space delimited
-c print current working directory of process
-e print errno value
-F print the flags passed to open
-g print full command arguments
-s print start time, us
-t print user stack trace
-v print start time, string
-x only print failed opens
-Z print zonename
-f pathname
file pathname to snoop
-n name
process name to snoop
-p PID process ID to snoop
EXAMPLES
Default output, print file opens by process as they occur,
# opensnoop
Print human readable timestamps,
# opensnoop -v
See error codes,
# opensnoop -e
Snoop this file only,
# opensnoop -f /etc/passwd
FIELDS
ZONE Zone name
UID User ID
PID Process ID
PPID Parent Process ID
FD File Descriptor (-1 is error)
FLAGS Flags passed to open
ERR errno value (see /usr/include/sys/errno.h)
CWD current working directory of process
PATH pathname for file open
COMM command name for the process
ARGS argument listing for the process
TIME timestamp for the open event, us
STRTIME
timestamp for the open event, string
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
opensnoop will run forever until Ctrl-C is hit.
BUGS
occasionally the pathname for the file open cannot be read and the following error will be seen,
dtrace: error on enabled probe ID 6 (...): invalid address
this is normal behaviour.
AUTHOR
Brendan Gregg [Sydney, Australia]
SEE ALSO
dtrace(1M), truss(1)
version 1.60 Jan 12, 2006 opensnoop(1m)