7 More Discussions You Might Find Interesting
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
2. Shell Programming and Scripting
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
3. Windows & DOS: Issues & Discussions
Please ignore this question. (0 Replies)
Discussion started by: Sommerville
4. Shell Programming and Scripting
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
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
5. UNIX for Advanced & Expert Users
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
6. Shell Programming and Scripting
# mail Generation
echo "Hi" | /mapimail -s "-(Test Mail)From Production- `date`" $email0;
i receive the following error
IDispatch::new MSMAPI.MAPISession failed: 800401f3 at... (0 Replies)
Discussion started by: Vrgurav
7. Shell Programming and Scripting
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
PRINTENV(1) BSD General Commands Manual PRINTENV(1)
printenv, env -- print out the environment, set and print environment
env [-i] [name=value ...] [utility [argument ...]]
The printenv utility prints out the names and values of the variables in the environment, with one name/value pair per line. If name is
specified, only its value is printed.
Some shells may provide a builtin printenv command which is similar or identical to this utility. Consult the builtin(1) manual page.
The env utility executes utility after modifying the environment as specified on the command line. The option name=value specifies an envi-
ronment variable, name, with a value of value.
The options are as follows:
-i Execute the utility with only those environment values specified. The environment inherited by env is ignored completely.
If no utility is specified, env prints out the names and values of the variables in the environment, with one name/value pair per line.
The env utility is sometimes useful with the ``#!'' construct (see execve(2)). The only difference between ``#!/usr/local/bin/foo'' and
``#!/usr/bin/env /usr/local/bin/foo'' is that the latter works even if /usr/local/bin/foo is itself interpreted. Using env this way also
allows one to reference foo without the path, as well as set up the environment as desired.
The env utility uses the PATH environment variable is used to locate the requested utility if the name contains no '/' characters.
The printenv utility exits 0 on success, and >0 if an error occurs.
The env utility exits 0 on success, and >0 if an error occurs. An exit status of 126 indicates utility was found, but could not be executed.
An exit status of 127 indicates utility could not be found.
The env utility accepts the - option as a synonym for -i.
csh(1), sh(1), execvp(3), environ(7)
The env utility conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
The printenv command appeared in 3.0BSD.
The env utility doesn't handle utility arguments with equal (``='') signs in their names, for obvious reasons.
June 6, 1993 BSD