Find command with MKS Toolkit


 
Thread Tools Search this Thread
Top Forums Shell Programming and Scripting Find command with MKS Toolkit
# 8  
Old 09-23-2009
For setting env variable:
export PATH or set env PATH etc etc ... based on your shell ...

But this might not be the case ... as path will be required only when you have options like -exec or -ok (I am guessing) ..

There might be some other problem.

just try just (no print option)
$ find .

also look where the command is; and run with complete path

$which find
/usr/bin/find

then run
$ /usr/bin/find .
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Linux

how to access schedule in cron/mks/w'

Hi, I need to work around 20 boxes to compile list of scheduled jobs on all of them, and these could be set in Linux RHat:cron, or Windows:MKS scheduler, or Windows:scheduler. Do you know how I can access those entries from script to have this whole list in sync, as we have it changed... (0 Replies)
Discussion started by: trento17
0 Replies

2. Shell Programming and Scripting

MKS Korn shell not working when schedule

Hi I have a sample MKS Korn Shell script, it is working fine when I am executing manually (i.e command prompt) but not when schedule through scheduler. here is the script, ls command working just fine manual run, so I thought it could be environment varilable so kept same PATH when running... (1 Reply)
Discussion started by: rkthoka
1 Replies

3. Windows & DOS: Issues & Discussions

Porting Unix c-shell script to Window under MKS-Tookit

Please ignore this question. (0 Replies)
Discussion started by: Sommerville
0 Replies

4. Shell Programming and Scripting

MKS KORN SHELL WONT EXECUTE from windows command prompt

Can anybody help me with this small script , the script works fine and launches the IE from c:\documents and settings \test\my documents>ksh prompt $RunURL1.sh this scitpt works and launches the ie from ksh , but when i schedule it to run the script then i get the error box saying command:1... (2 Replies)
Discussion started by: venu
2 Replies

5. UNIX for Advanced & Expert Users

Named pipes using MKS Toolkit

I'm not sure whether or not this question really belongs in this forum and will accept rebuke should I have mistakenly put it in the wrong place (hopefully the rebuke will be accompanied by an answer, though) I wish to implement named pipe communication between two process using MKS Toolkit. I... (2 Replies)
Discussion started by: ArndW
2 Replies

6. Shell Programming and Scripting

error while sending mails through MKS

#!/bin/ksh email0="dummy@company.com" emails() { # mail Generation echo "Hi" | /mapimail -s "-(Test Mail)From Production- `date`" $email0; } emails i receive the following error IDispatch::new MSMAPI.MAPISession failed: 800401f3 at... (0 Replies)
Discussion started by: Vrgurav
0 Replies

7. Shell Programming and Scripting

command find returned bash: /usr/bin/find: Argument list too long

Hello, I create a file touch 1201093003 fichcomp and inside a repertory (which hava a lot of files) I want to list all files created before this file : find *.* \! -maxdepth 1 - newer fichcomp but this command returned bash: /usr/bin/find: Argument list too long but i make a filter all... (1 Reply)
Discussion started by: yacsil
1 Replies
Login or Register to Ask a Question
env(1)							      General Commands Manual							    env(1)

NAME
env, printenv - Displays or sets the current environment, or displays the values of environment variables SYNOPSIS
Current Syntax env [-i] [name=value...] [command] [args...] printenv [name] Obsolescent Syntax env [-] [name=value...] [command] [args...] STANDARDS
Interfaces documented on this reference page conform to industry standards as follows: env: XCU5.0 Refer to the standards(5) reference page for more information about industry standards and associated tags. OPTIONS
Invokes utility with exactly the environment specified by the arguments; the inherited environment is ignored completely. Changes are in effect only while the specified command is running. Dash is equivalent to -i option. OPERANDS
Changes in the form name=value are added to the current environment before the command is run. [Tru64 UNIX] Name of an environment vari- able to be printed. Name of a command to be invoked with the modified environment. Arguments to be passed to command when it is executed. DESCRIPTION
The env command lets you get and change your current environment, and then run the specified command with the changed environment. If the -i option is used, the current environment is ignored and the command runs with only the changed environment. Changes are only in effect while the specified command is running. If command is not specified, env displays your current environment, one name=value pair per line. [Tru64 UNIX] The printenv command displays the values of the variables in the environment. If name is specified, only its value is printed. If name is not the name of a currently set environment variable, only a blank line is printed, no error is reported. If name is not specified, printenv displays the current environment, one name=value per line. EXIT STATUS
If command is invoked, the exit status of env is the exit status of command; otherwise, the env utility exits with one of the following values: The env utility completed successfully. An error occurred in the env utility. The command specified by command was found but could not be invoked. The command specified by command could not be found. EXAMPLES
To add a shell variable to the environment for the duration of one command (sh only), enter: TZ=MST7MDT date env TZ=MST7MDT date Each of these commands displays the current date and time in Mountain Standard Time. The two commands shown are equivalent. When date is finished, the previous value of TZ takes effect again. To replace the environment with another one, enter: env -i PATH=$PATH IDIR=/u/jim/include LIBDIR=/u/jim/lib make This runs make in an environment that consists only of these definitions for PATH, IDIR, and LIBDIR. You must redefine PATH so that the shell can find the make command. When make is finished, the previous environment takes effect again. To find the current setting of the TERM environment variable, enter: printenv TERM The command returns the value for the TERM environment variable. ENVIRONMENT VARIABLES
The following environment variables affect the execution of env: Provides a default value for the internationalization variables that are unset or null. If LANG is unset or null, the corresponding value from the default locale is used. If any of the internationalization vari- ables contain an invalid setting, the utility behaves as if none of the variables had been defined. If set to a non-empty string value, overrides the values of all the other internationalization variables. Determines the locale for the interpretation of sequences of bytes of text data as characters (for example, single-byte as opposed to multibyte characters in arguments). Determines the locale for the for- mat and contents of diagnostic messages written to standard error. Determines the location of message catalogues for the processing of LC_MESSAGES. SEE ALSO
Commands: csh(1), ksh(1), Bourne shell sh(1b), POSIX shell sh(1p) Functions: exec(2) Standards: standards(5) env(1)