Sponsored Content
Full Discussion: $PATH error (possibly)
Top Forums UNIX for Dummies Questions & Answers $PATH error (possibly) Post 302692061 by pamu on Monday 27th of August 2012 03:29:36 AM
Old 08-27-2012
Hi SartreSmartre,

From the path itself it clears that your getting wrong path, just check how you are getting this path then you will get answer.

Put some more details about this...
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

stupid question possibly

how would I search through subdirectories under the current directory and delete all files in certain directories. in ThisDirectory.... want to go into foundMe directory which there are several in other subdirectories and delete all files in foundMe ? thank you... (1 Reply)
Discussion started by: MrJaunty
1 Replies

2. Shell Programming and Scripting

input variable like POST in PHP possibly?

I have a very large database and once in awhile the database auto loading scripts that update the database for the daily updates fails and I have to go in and manually fix it but when that happens I usually have to start from scratch on sundays I have access to a weekly database rebuild. Then I... (3 Replies)
Discussion started by: chadrt
3 Replies

3. Solaris

Why in.mpathd errors - performance possibly?

Hello all, Run a search but see no previous queries. Trying to get to the bottom of why a server running Solaris 9 reports the following every other day: lonpcbcfp1:Jun 20 16:33:20 lonpcbcfp1 in.mpathd: missed sending 17 probes cur_time 1478014085 snxt_time 1478015026 snxt_basetime 1478014018... (0 Replies)
Discussion started by: bookiebarton
0 Replies

4. Shell Programming and Scripting

reformatting xml file, sed or awk I think (possibly perl)

I have some xml files that cannot be read using a standard parser, or I am using the wrong parser. The issues seems to be spaces in some of the tags. Here is a sample,<UgUn 2 > <Un> -0.426753 </Un> </UgUn>The parser isn't able to find the number 2, so that information is lost, etc. It seems... (16 Replies)
Discussion started by: LMHmedchem
16 Replies

5. Shell Programming and Scripting

Combining find, grep and possibly ls?!

Hi - can someone please help me combine find, grep and possibly ls into something workable: i.e. How can I list all the files that contain the word "pet" in all directories under the current directory that are called "animal", bar those anywhere under directories called "archive"? I suspect... (6 Replies)
Discussion started by: cs03dmj
6 Replies

6. UNIX for Dummies Questions & Answers

Comparing Two Files, Possibly with VIM

Hello, I have a problem comparing two files, both .csv. One file, let's call it files.csv, contains a list of thousands of file names for models of molecules that have made it through an optimization process. The other file, formulas.csv, contains file names for the same kind of models, and has... (2 Replies)
Discussion started by: Stuart Ness
2 Replies

7. HP-UX

Cdrom device possibly missing?

Hello, I am following the HPUX 11.31 install/update guide and I am trying to install "Update-UX" from the installation media. I put the CD into the drive, and I am trying to mount the device. The instructions state:Find the DVD-ROM device file name: ioscan -C disk -f -n -k | more A typical... (5 Replies)
Discussion started by: bstring
5 Replies

8. Shell Programming and Scripting

How would I construct a (possibly simple) IF statement?

Hi all, I thought this would be simple, but I've been having a lot of trouble trying to write this IF statement, if I may ask for help pls: In BASH, how would I construct the if statement: Should ONLY be true if USEROPTscript=="yes"]] AND $mode=="INSTALL" /or/ $mode=="CHANGE" ]]... (3 Replies)
Discussion started by: jmccoughlin
3 Replies

9. UNIX for Beginners Questions & Answers

DHCP Issue Possibly due to Hardware Clock?

Hello All, OS: openSUSE 13.1 (Bottle) (armv7hl) PC: CuBox-i (*mini-pc) The PC in question is a CuBox-i mini-pc. Since this PC doesn't have a battery, everytime the PC reboots the hardware clock is reset back to the same date every time, which is "2014-07-08 00:00". I have NTP configured... (5 Replies)
Discussion started by: mrm5102
5 Replies
WHEREIS(1)						    BSD General Commands Manual 						WHEREIS(1)

NAME
whereis -- locate programs SYNOPSIS
whereis [-abmqsux] [-BMS dir ... -f] program ... DESCRIPTION
The whereis utility checks the standard binary, manual page, and source directories for the specified programs, printing out the paths of any it finds. The supplied program names are first stripped of leading path name components, any single trailing extension added by gzip(1), compress(1), or bzip2(1), and the leading 's.' or trailing ',v' from a source code control system. The default path searched is the string returned by the sysctl(8) utility for the ``user.cs_path'' string, with /usr/libexec and the current user's $PATH appended. Manual pages are searched by default along the $MANPATH. Program sources are located in a list of known standard places, including all the subdirectories of /usr/src and /usr/ports. The following options are available: -B Specify directories to search for binaries. Requires the -f option. -M Specify directories to search for manual pages. Requires the -f option. -S Specify directories to search for program sources. Requires the -f option. -a Report all matches instead of only the first of each requested type. -b Search for binaries. -f Delimits the list of directories after the -B, -M, or -S options, and indicates the beginning of the program list. -m Search for manual pages. -q (``quiet''). Suppress the output of the utility name in front of the normal output line. This can become handy for use in a back- quote substitution of a shell command line, see EXAMPLES. -s Search for source directories. -u Search for ``unusual'' entries. A file is said to be unusual if it does not have at least one entry of each requested type. Only the name of the unusual entry is printed. -x Do not use ``expensive'' tools when searching for source directories. Normally, after unsuccessfully searching all the first-level subdirectories of the source directory list, whereis will ask locate(1) to find the entry on its behalf. Since this can take much longer, it can be turned off with -x. EXAMPLES
The following finds all utilities under /usr/bin that do not have documentation: whereis -m -u /usr/bin/* Change to the source code directory of ls(1): cd `whereis -sq ls` SEE ALSO
find(1), locate(1), man(1), which(1), sysctl(8) HISTORY
The whereis utility appeared in 3.0BSD. This version re-implements the historical functionality that was lost in 4.4BSD. AUTHORS
This implementation of the whereis command was written by Jorg Wunsch. BUGS
This re-implementation of the whereis utility is not bug-for-bug compatible with historical versions. It is believed to be compatible with the version that was shipping with FreeBSD 2.2 through FreeBSD 4.5 though. The whereis utility can report some unrelated source entries when the -a option is specified. BSD
August 22, 2002 BSD
All times are GMT -4. The time now is 02:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy