Sponsored Content
Operating Systems Solaris Find path of executable having problem Post 302831357 by jlliagre on Wednesday 10th of July 2013 07:20:36 PM
Old 07-10-2013
However, lsof is usually not available on Solaris machines. There are hopefully ways to get the information lsof provides with standard Solaris tools.

To get the full path of the command run you can use this simple command:
Code:
ls -l /proc/<pid>/path/a.out

 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

process executable file full path

hi guys i give "ps -ef | grep some_executable_file" on the command line. this "some_executable_file" resides on many paths which r included in the PATH environment variable, so the output depicts only "some_executable_file" in the COMMAND column. how can i get the full path? thanx (3 Replies)
Discussion started by: xtrix
3 Replies

2. UNIX for Dummies Questions & Answers

cc path problem - no acceptable path found

Hello everyone, I'm a unix noob. I have a powerbook running mac os x 10.4 and for one of my classes I need to install the latest version of php (5.0.5). I'm following the instructions at http://developer.apple.com/internet/opensource/php.html to install but I've run into a problem. The... (2 Replies)
Discussion started by: kendokendokendo
2 Replies

3. Shell Programming and Scripting

script to find latest executable in particular directory and start that particular ex

i have a directory in which there are executable files and these files are added at runtime. now i need a shell script which will be called at a certain interval. this shell script should find the latest executable file in that directory and start that executable. care should be taken that once the... (6 Replies)
Discussion started by: kvineeth
6 Replies

4. Programming

gdb: problem while debug an executable file

I created one file (test.cpp)and complied it and get the executable file(test) and run it.It is giving the out put but when I am trying to debug that executable.I am getting the error -- please tell me the solutions?? Thanks in advance ..... (2 Replies)
Discussion started by: smartgupta
2 Replies

5. Shell Programming and Scripting

problem in making Awk executable script

Guys I placed #!path/awk -f placed awk script and used $1 to call 1st inputfile inside the script. But some where I did mistake. Could you please help me run this script as executable I forgot to mention I also used BEGIN before placing awk script. But nothing worked out. Script ... (2 Replies)
Discussion started by: repinementer
2 Replies

6. Shell Programming and Scripting

Problem with embedded FTP command in Ksh - System Cannot find the specified path.

I have the following FTP embedded in a Ksh script on AIX 5.3 ftp -n <<WHATEVER open 10.101.26.218 user hcistats ******* ascii put $thupdatefile put $thcollectfile quit WHATEVER Here is what my script returns: ... (3 Replies)
Discussion started by: troym72
3 Replies

7. Shell Programming and Scripting

Question on tweaking the PATH variable to allow the world to run my executable script

All, I am pretty new to Unix and still in the learning curve :) I have a simple requirement for which I did not get an answer yet (Atleast I do not know how to keyword the search for my requirement!!!). I have an executable script my.script1 in a folder /data/misc/scripts/dev, which when... (5 Replies)
Discussion started by: bharath.gct
5 Replies

8. UNIX for Dummies Questions & Answers

Problem running executable with ./

Hey all, I'm trying to execute a program and despite it appearing to be there, I keep getting this: -bash: ./aisdispatcher: No such file or directoryTo run it, I'm going into the directory where it is stored and running ./aisdispatcher...the result of which should just be a listing of options... (10 Replies)
Discussion started by: pmd006
10 Replies

9. Solaris

Finding the path to an executable , installed package

Hi all, Recently i wanted to see if i have openssl installed in my system (solaris 10), so i do this (not sure if this is the right way to do this) pkginfo -i | grep -i "ssl" system SUNWopenssl-commands OpenSSL Commands (Usr) system SUNWopenssl-include ... (3 Replies)
Discussion started by: javanoob
3 Replies

10. UNIX for Dummies Questions & Answers

Find exit with success with non executable directory

Hi there, I'm quite surprised by the following behavior of find. $ find -ls # I have a directory and a file in it 8145 4 drwxr-xr-x 3 me me 4096 May 10 09:36 . 87 4 drwxr-xr-x 2 me me 4096 May 10 09:36 ./dir 88 0 -rw-r--r-- 1 me me 0... (2 Replies)
Discussion started by: chebarbudo
2 Replies
VERIFY_KRB5_CONF(8)					    BSD System Manager's Manual 				       VERIFY_KRB5_CONF(8)

NAME
verify_krb5_conf -- checks krb5.conf for obvious errors SYNOPSIS
verify_krb5_conf [config-file] DESCRIPTION
verify_krb5_conf reads the configuration file krb5.conf, or the file given on the command line, parses it, checking verifying that the syntax is not correctly wrong. If the file is syntactically correct, verify_krb5_conf tries to verify that the contents of the file is of relevant nature. ENVIRONMENT
KRB5_CONFIG points to the configuration file to read. FILES
/etc/krb5.conf Kerberos 5 configuration file DIAGNOSTICS
Possible output from verify_krb5_conf include: <path>: failed to parse <something> as size/time/number/boolean Usually means that <something> is misspelled, or that it contains weird characters. The parsing done by verify_krb5_conf is more strict than the one performed by libkrb5, so strings that work in real life might be reported as bad. <path>: host not found (<hostname>) Means that <path> is supposed to point to a host, but it can't be recognised as one. <path>: unknown or wrong type Means that <path> is either a string when it should be a list, vice versa, or just that verify_krb5_conf is confused. <path>: unknown entry Means that <string> is not known by verify_krb5_conf. SEE ALSO
krb5.conf(5) BUGS
Since each application can put almost anything in the config file, it's hard to come up with a watertight verification process. Most of the default settings are sanity checked, but this does not mean that every problem is discovered, or that everything that is reported as a possi- ble problem actually is one. This tool should thus be used with some care. It should warn about obsolete data, or bad practice, but currently doesn't. BSD
December 8, 2004 BSD
All times are GMT -4. The time now is 10:46 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy