topic Re: which command error, need help in Operating System - HP-UX

which command error, need help

sysad1_1 — Mon, 04 Oct 2010 09:09:58 GMT

My which command is failing recently because of this error:

prompt@localhost>which
which[7]: Syntax error at line 7 : `(' is not expected.

I don't why, but already looked into other HP-UX servers with working "which" commands but the script is just the same.

#! /usr/bin/csh
# @(#) $Revision: 72.1 $
#
# which : tells you which program you get
#
set noglob
foreach arg ( $argv )
set alius = `alias $arg`
switch ( $#alius )
case 0 :
breaksw
case 1 :
set arg = $alius[1]
breaksw
default :
echo ${arg}: " " aliased to $alius
continue
endsw
unset found
if ( $arg:h != $arg:t ) then
if ( -e $arg ) then
echo $arg
else
echo $arg not found
endif
continue
else
foreach i ( $path )
if ( -x $i/$arg && ! -d $i/$arg ) then
echo $i/$arg
set found
break
endif
end
endif
if ( ! $?found ) then
echo no $arg in $path
endif
end

What seems to be the problem in here and how can i fix it? Thanks!

Re: which command error, need help

Mounaam — Mon, 04 Oct 2010 09:34:07 GMT

it's as if your script is interpreted by a sh-like shell (sh, ksh...) instead of /usr/bin/csh.
Try this to confirm:
$ sh /usr/bin/which
$ csh /usr/bin/which

Can you check that your csh has not changed (or replaced by another thing).

What is the result of:
$ what /usr/bin/csh

Regards,
Mounaam

Re: which command error, need help

sysad1_1 — Mon, 04 Oct 2010 10:12:55 GMT

here are the command outputs you requested:

# sh /usr/bin/which
/usr/bin/which[7]: Syntax error at line 7 : `(' is not expected.
# csh /usr/bin/which
sh: csh: Execute permission denied.

# what /usr/bin/csh
/usr/bin/csh:

Re: which command error, need help

James R. Ferguson — Mon, 04 Oct 2010 10:43:26 GMT

Hi:

> sh: csh: Execute permission denied.

It looks like you don't have execute permissions. This should look like:

# -r-xr-xr-x 1 bin bin 654 Feb 15 2007 /usr/bin/which

Regards!

...JRF...

Re: which command error, need help

Hakki Aydin Ucar — Mon, 04 Oct 2010 11:05:05 GMT

Check it like JRF said, it should look like;

# ls -l /usr/bin/which
-r-xr-xr-x 1 bin bin 654 Nov 14 2000 /usr/bin/which

Re: which command error, need help

Hakki Aydin Ucar — Mon, 04 Oct 2010 11:07:26 GMT

Hi,

And besides, you can check these also:
# file /usr/bin/which
/usr/bin/which: commands text
# what /usr/bin/which
/usr/bin/which:
B.11.11_LR
# echo $0
/sbin/sh

Re: which command error, need help

Dennis Handly — Mon, 04 Oct 2010 11:12:17 GMT

>My which command is failing recently because of this error:

Any reason you are using the scummy C shell or one if its utilities?
The real shell has "whence".

Re: which command error, need help

Pete Randall — Mon, 04 Oct 2010 11:38:56 GMT

> Any reason you are using the scummy C shell or one if its utilities?

Check your's, Dennis. I think you'll find that that is the way HP provided it to us: with the scummy C shell!

Pete

Re: which command error, need help

Dennis Handly — Mon, 04 Oct 2010 11:46:11 GMT

>Pete: I think you'll find that that is the way HP provided it to us: with the scummy C shell!

And that's why you don't use which(1).

Re: which command error, need help

sysad1_1 — Mon, 04 Oct 2010 23:55:43 GMT

Hi everyone,

i do have execute permission for which

>ls -l /usr/bin/which
-r-xr-xr-x 1 bin bin 664 Oct 4 18:04 /usr/bin/which

>csh /usr/bin/ls
sh: csh: Execute permission denied.

by the way, is the "whence" and "which" command just the same? in my 5 years of IT work experience I never knew that there was a "whence" command.

Re: which command error, need help

Bill Hassell — Tue, 05 Oct 2010 00:46:33 GMT

whence (and it's VERY useful alias type which is the even more useful whence -v) replaces which and whereis. Neither which nor whereis will tell you exactly what happens when you enter a string on the command line. which knows nothing about "for" but...

# which for
no for in /usr/sbin /usr/bin /opt/ansic/bin /usr/ccs/bin /usr/contrib/bin /opt/hparray/bin /opt/nettladm/bin /opt/upgrade/bin /opt/fcms/bin /opt/resmon/bin /opt/pd/bin /opt/gnome/bin /opt/perf/bin /opt/ignite/bin /usr/contrib...etc

# whereis for
for:

# whence -v for
for is a keyword.

which is useless for aliases and shell builtins. Other examples:

# type type
type is an exported alias for whence -v
# type ulimit
ulimit is a shell builtin.
# type pwd
pwd is a shell builtin.
# alias pwd=/usr/bin/pwd
# type pwd
pwd is an alias for /usr/bin/pwd

type (whence) tells you what will happen if you type a string of characters. It finds shell aliases, keywords, basically anything that the shell does for you. This is much more useful than which and whereis.

HP provides the scummy C shell but that doesn't mean you should use it. Fir sysadmins, only a real shell (with standards like POSIX) like ksh or the POSIX shell sh (or even bash) provide consistent and portable results.

Re: which command error, need help

Dennis Handly — Tue, 05 Oct 2010 03:50:31 GMT

>I do have execute permission for which
-r-xr-xr-x 1 bin bin 664 Oct 4 18:04 /usr/bin/which

Do you have it for the scummy C shell?
ll /usr/bin/csh

While this is a rather clever trick to prevent users from using the scummy C shell, you should put the system back the way is was.

>is the "whence" and "which" command just the same? in my 5 years of IT work experience I never knew that there was a "whence" command.

Not really, though similar:
$ which csh
/usr/bin/csh # scummy C shell
$ whence -pv csh
csh is /usr/bin/csh
$ whence -v csh
csh is a tracked alias for /usr/bin/csh

If you know what makes the C shell scummy, you would know that which(1) is scummy too.

And real shell users, use whence. Since it is built into a real shell, it can tell you more things.

Re: which command error, need help

Dennis Handly — Tue, 05 Oct 2010 04:01:39 GMT

>prompt@localhost>which
which[7]: Syntax error at line 7 : `(' is not expected.

One other way to get this error is to link scummy csh to a real shell.
I get a different error if csh isn't executable.

Re: which command error, need help

sysad1_1 — Wed, 06 Oct 2010 02:22:52 GMT

thanks for all the replies. I already made use of whence instead of which.