#/usr/bin/csh -f not working as expected? Post: 302073388

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

/bin/sh: /usr/bin/vi: No such file or directory when doing crontab

I just set up an ftp server with Red Hat 5.2. I am doing the work, I'm baby stepping, but it seems like every step I get stuck. Currently, I'm trying to set up a crontab job, but I'm getting the following message: /bin/sh: /usr/bin/vi: No such file or directory. I see that vi exists in /bin/vi,...

2. Solaris

/usr/bin/cut not working with largefiles on Solaris 10

I have a person running a perl script that is parsing > 2G log files and pipes to cut -d " " -f 1,6,7,8... The script itself is in a nfs mounted home directory. It runs fine when started from a solaris 8 box but fails after about 400 lines when started from the solaris 10 box. The solaris...

3. Solaris

How do I link ld in /usr/ucb/ to /usr/ccs/bin?

Hi all, below is the problem details: ora10g@CNORACLE1>which ld /usr/ucb/ld ora10g@CNORACLE1>cd /usr/ccs/bin ora10g@CNORACLE1>ln -s /usr/ucb/ld ld ln: cannot create ld: File exists ora10g@CNORACLE1> how to link it to /usr/ccs/bin?

4. Red Hat

/usr/bin/find && -exec /bin/rm never work as expected

hi there, Would you able to advise that why the syntax or statement below couldn't work as expected ? /usr/bin/find /backup -name "*tar*" -mtime +2 -exec /bin/rm -f {} \; 1> /dev/null 2>&1 In fact, I was initially located it as in crontab job, but it doesn't work at all. So, I was...

5. OS X (Apple)

When to use /Users/m/bin instead of /usr/local/bin (& whats the diff?)?

Q1. I understand that /usr/local/bin means I can install/uninstall stuff in here and have any chance of messing up my original system files or effecting any other users. I created this directory myself. But what about the directory I didn't create, namely /Users/m/bin? How is that directory...

6. Solaris

What is the difference between xpg4/bin and usr/bin?

Hi Experts, I found that the same commands(sort, du, df, find, grep etc.) exists in both dir. What is the difference to use them? i.e: to use xpg4/bin/grep and usr/bin/grep My OS version is SunOS 5.10 Regards, Saps

7. Shell Programming and Scripting

/usr/local/bin/expr function not working

Legends, I am not able to set "expr" function in ksh script. Below is the sample code i used, and output is as "Syntax error" Please help me to come out of it. OUTPUT

8. Shell Programming and Scripting

Nested if not working with /usr/xpg4/bin/awk

Hi, I am trying to do if inside the If in /usr/xpg4/bin/awk. But I am getting below error : /usr/xpg4/bin/awk -v a="${THREADIDARR }" 'BEGIN {FS="|"; n=split(a,b," "); for(i=1; i<=n; i++) c]=1;} length($3) == 0{ftag == 1{{print}}; length($3) != 0{$3 in c{ftag=1;print;} !$3 in c{ftag=0;}}'...

9. BSD

FreeBSD: /usr/bin/ld not looking in /usr/local/lib

I'm not sure if this is the default behavior for the ld command, but it does not seem to be looking in /usr/local/lib for shared libraries. I was trying to compile the latest version of Kanatest from svn. The autorgen.sh script seems to exit without too much trouble: $ ./autogen.sh checking...

LEARN ABOUT OPENSOLARIS

nice

nice(1) 							   User Commands							   nice(1)

NAME

       nice - invoke a command with an altered scheduling priority

SYNOPSIS

       /usr/bin/nice [-increment | -n increment] command
	    [argument]...

       /usr/xpg4/bin/nice [-increment | -n increment] command
	    [argument]...

   csh Builtin
       nice [-increment | +increment] [command]

DESCRIPTION

       The  nice utility invokes command, requesting that it be run with a different system scheduling priority. The priocntl(1) command is a more
       general interface to scheduler functions.

       The invoking process (generally the user's shell) must be in a scheduling class that supports nice.

       If the C shell (see csh(1)) is used, the full path of the command must be specified. Otherwise, the csh built-in version of  nice  will	be
       invoked. See csh Builtin below.

   /usr/bin/nice
       If nice executes commands with arguments, it uses the default shell /usr/bin/sh (see sh(1)).

   /usr/xpg4/bin/nice
       If nice executes commands with arguments, it uses /usr/xpg4/bin/sh (see ksh(1)).

   csh Builtin
       nice is also a csh built-in command with behavior different from the utility versions.  See csh(1) for description.

OPTIONS

       The following options are supported:

       -increment | -n increment    increment  is  a positive or negative decimal integer that has the same effect on the execution of the utility
				    as if the utility had called the nice() function with the numeric value of the increment option-argument.  See
				    nice(2). nice() errors, other than EINVAL, are ignored. If not specified, an increment of 10 is assumed.

				    The  super-user may run commands with priority higher than normal by using a negative increment such as -10. A
				    negative increment assigned by an unprivileged user is ignored.

OPERANDS

       The following operands are supported:

       command	   The name of a command that is to be invoked. If command names any of the special built-in  utilities  (see  shell_builtins(1)),
		   the results are undefined.

       argument    Any string to be supplied as an argument when invoking command.

ENVIRONMENT VARIABLES

       See  environ(5)	for descriptions of the following environment variables that affect the execution of nice: LANG, LC_ALL, LC_CTYPE, LC_MES-
       SAGES, PATH, and NLSPATH.

EXIT STATUS

       If command is invoked, the exit status of nice will be the exit status of command. Otherwise, nice will exit with one of the following val-
       ues:

       1-125	An error occurred.

       126	command was found but could not be invoked.

       127	command could not be found.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

   /usr/bin/nice
       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWcsu			   |
       +-----------------------------+-----------------------------+
       |CSI			     |Enabled			   |
       +-----------------------------+-----------------------------+

   /usr/xpg4/bin/nice
       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWxcu4			   |
       +-----------------------------+-----------------------------+
       |CSI			     |Enabled			   |
       +-----------------------------+-----------------------------+
       |Interface Stability	     |Standard			   |
       +-----------------------------+-----------------------------+

SEE ALSO

       csh(1), ksh(1), nohup(1), priocntl(1), sh(1), shell_builtins(1), nice(2), attributes(5), environ(5), standards(5)

SunOS 5.11							    23 Jan 2004 							   nice(1)