Hi bakunin,
Actually, the POSIX Standards have required conforming shells to support export commands with the SYNOPSIS forms:
since 1992.
But, of course, if you're working on a project that is still using a pure Bourne shell, you'd still need to avoid assigning a value to a variable in an export command.
This User Gave Thanks to Don Cragun For This Post:
I am facing a strange issue while running a script(eg A) from the crontab entry
the script calls one more script(eg B) within it
now when i run the script A manually(with nohup) it also executes the script B (embedded inside it) as expected.
but when i run the script A from the crontab entry... (7 Replies)
Hi all,
I wrote small script for Solaris and when I am running it through command prompt its ok, but when I trying to run it using crontab, i am getting error like:
ld.so.1: dbloader: fatal: libACE.so: open failed: No such file or directory
/tmp/file.sh: line 5: 8304 Killed ... (4 Replies)
I am trying to use the CRON utility in Fedora 11 & CentOS...
I intend to run a script which pops up a warning message every hour and i made the following entry using "CRONTAB -e "
* * * * * sh /bin/myscript.sh
But this does not seem to be running.
Another thing to note is that,... (4 Replies)
Hi,
Can someone please help me here with this one.
This is my script:
# more tosh.sh
#!/usr/bin/ksh
clear
. /home/oracle/.profile
echo "Good morning, world."
export ORACLE_HOME=/u01/app/oracle/product/9.0.1
export PATH=$ORACLE_HOME/bin:/usr/local/bin
export ORACLE_SID=xxxx
... (11 Replies)
Hi, I posted this in the Solaris forum but I think this one would be more appropriate.
I created a script starting with the following lines:
#!/usr/bin/ksh
flag=n
export flag
typeset -i quant=0
(...)
When running it I'm getting the following 2 errors:
/tmp/tstscript/testfail.ksh:... (9 Replies)
Hi,
I have created the below script,
set -x
# Set the Path of Environment file
ENV_FILE_DIR=/opt/app/p1trp1c1/sybase/ecdwqdm/xrbid/QDM_Prod/bin
LOG_DIR=/opt/app/p1trp1c1/sybase/ecdwqdm/xrbid/QDM_Prod/log
export ENV_FILE_DIR
export LOG_DIR
# Set Audit Environment
. ${ENV_FILE_DIR}/QDM.env... (8 Replies)
Hi All,
I am having the below script to be run from crontab, it it doesnt run.
1 * * * * /home/cobr_ext/test.sh > /home/cobr_ext/temp.txt
when i run i manally it runs without any issues.
Could please help me as to why doesnt it run the script.:( (7 Replies)
Hi guys!
I created a backup script that works fine when I run manually, but when I put a crontab job to execute it the result are not the expected. (not a time problem).
Here is my script:
bash-3.00# cat /bk_tool/backup2.sh
#!/usr/bin/csh
clear
set DIR_HOST='SCP08'
... (3 Replies)
I need a script which should watch a directory for a file with specific directory.
If it finds a file in directory, it should search for few specific keyword in the file. if the keyword exists, it should trim string from specific column.
The file should be moved to another directory and the a... (8 Replies)
Hi!
I'm using a RaspberryPi with standard Raspbian.
Currently I'm working on some sort of weather station.
For now I have three python scripts - one which is updating txt files for website - update1m.py ( it will not be necessary in few next days so I'll delete it) , second one for updating... (4 Replies)
Discussion started by: bartocham
4 Replies
LEARN ABOUT OSX
python
PYTHON(1) BSD General Commands Manual PYTHON(1)NAME
python, pythonw -- an interpreted, interactive, object-oriented programming language
SYNOPSIS
python ...
pythonw ...
DESCRIPTION
To support multiple versions, the programs named python and pythonw now just select the real version of Python to run, depending on various
settings. (As of Python 2.5, python and pythonw are interchangeable; both execute Python in the context of an application bundle, which
means they have access to the Graphical User Interface; thus both can, when properly programmed, display windows, dialogs, etc.) The current
supported versions are 2.6 and 2.7, with the default being 2.6. Use
% man python2.6
% man python2.7
% man pythonw2.6
% man pythonw2.7
to see the man page for a specific version. Without a version specified,
% man pydoc
and the like, will show the man page for the (unmodified) default version of Python (2.6). To see the man page for a specific version, use,
for example,
% man pydoc2.7
CHANGING THE DEFAULT PYTHON
Using
% defaults write com.apple.versioner.python Version 2.7
will make version 2.7 the user default when running the both the python and pythonw commands (versioner is the internal name of the version-
selection software used).
To set a system-wide default, replace 'com.apple.versioner.python' with '/Library/Preferences/com.apple.versioner.python' (admin privileges
will be required).
The environment variable VERSIONER_PYTHON_VERSION can also be used to set the python and pythonw version:
% export VERSIONER_PYTHON_VERSION=2.7 # Bourne-like shells
or
% setenv VERSIONER_PYTHON_VERSION 2.7 # C-like shells
% python ...
This environment variable takes precedence over the preference file settings.
64-BIT SUPPORT
Versions 2.6 and 2.7 support 64-bit execution (which is on by default).
Like the version of Python, the python command can select between 32 and 64-bit execution (when both are available). Use:
% defaults write com.apple.versioner.python Prefer-32-Bit -bool yes
to make 32-bit execution the user default (using '/Library/Preferences/com.apple.versioner.python' will set the system-wide default). The
environment variable VERSIONER_PYTHON_PREFER_32_BIT can also be used (has precedence over the preference file):
% export VERSIONER_PYTHON_PREFER_32_BIT=yes # Bourne-like shells
or
% setenv VERSIONER_PYTHON_PREFER_32_BIT yes # C-like shells
Again, the preference setting and environmental variable applies to both python and pythonw.
USING A SPECIFIC VERSION
Rather than using the python command, one can use a specific version directly. For example, running python2.7 from the command line will run
the 2.7 version of Python, independent of what the default version of Python is.
One can use a specific version of Python on the #! line of a script, but that may have portability and future compatibility issues.
Note that the preference files and environment variable that apply to the python command, do not apply when running a specific version of
Python. In particular, running python2.6 will always default to 64-bit execution (unless one uses the arch(1) command to specifically select
a 32-bit architecture).
SEE ALSO python2.6(1), python2.7(1), pythonw2.6(1), pythonw2.7(1), arch(1)BSD Aug 10, 2008 BSD