Sponsored Content
Top Forums Programming Shell script - if statements dont work Post 302987155 by rbatte1 on Tuesday 6th of December 2016 06:56:44 AM
Old 12-06-2016
Hello robertkwild,

What input do you use and what errors do you get?

You might be hitting a number of problems because you have minimal error checking and your mv command might have a null input so becomes invalid too. This might not be a problem for a simple helper script for yourself but might be more confusing if you delegate it.

Is a null response to the source directory okay? That would change to the user's home directory.



Robin
 

10 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

OS X / fsck / apps dont work no control panel

Alright. My neighbor kid brings me his iBook and says nothing works. He decided to move the file system to his likeness and that semed to create the problems. Now he doesn't have access rights to his home. I have run fsck over and over again and I keep getting ** fs modified ** I have also... (0 Replies)
Discussion started by: maxwell
0 Replies

2. Shell Programming and Scripting

Running remote shell script containing sql statements

I have a shell script which resides on three SCO machines containing some simple sqlplus statments. I need to run these scripts remotely. Currently, I am trying to use rsh to do so: rsh hostname myscript args The problem is that the arguments to the sqlplus statements in the remote shell... (4 Replies)
Discussion started by: Madbreaks
4 Replies

3. UNIX for Advanced & Expert Users

why the date format dont work in crontab

Hi I tried to put a cron job which pipes the logfile appended to date +%d but it didnt work . anyone know how to make this happen thanks in advance -prasad (7 Replies)
Discussion started by: p4cldba
7 Replies

4. Shell Programming and Scripting

if [ -z echo foo | egrep -e 'regexp' != '' ] -> dont work

Hallo, I need to test a String (a special ip number-string). So I want to run that: ipadress=172.0.0.0 # for debugging: echo $ipadress | egrep -e '172\.?\.??\.??$' # the test that doesnt work if test -z `echo $ipadress | egrep -e '172\.?\.??\.??$'` != "" then echo "match" else... (1 Reply)
Discussion started by: wiseguy
1 Replies

5. Shell Programming and Scripting

Looping through a shell script with sql statements

Hello members, I'm working on the Solaris environment and the DB i'm using is Oracle 10g. Skeleton of what I'm attempting; Write a ksh script to perform the following. I have no idea how to include my sql query within a shell script and loop through the statements. Have therefore given a... (4 Replies)
Discussion started by: novice82
4 Replies

6. Shell Programming and Scripting

Substitution in a file dont work with an Array in filename

Hi. I´ve a script that should substitude the 8th line in a file called xxx.num6. The "xxx" is set by an array filled with this command: j=0 for Par in *.sys ; do Par=`echo $Par | sed 's/\(.*\).sys/\1/'` ; Par2="$Par" ; echo "${Par2}" j=$((j + 1)); done Now i try... (0 Replies)
Discussion started by: Lock3
0 Replies

7. UNIX for Dummies Questions & Answers

keyboard and mouse dont work after sometime from boot in linux.

when i started booting linux ,after sometime both the mouse and the keyboard are getting freeze and wont respond(also the system gets hanged and all the process running dont go forward) ,nothing seem to work. Keeping in mind that it will work after sometime ,i waited for one hour also ,but... (1 Reply)
Discussion started by: sanjay.login
1 Replies

8. Shell Programming and Scripting

Can we use two shebang statements in a single shell script?

Hi, As per my understanding, we can use two shebang statements in a single shell script. Please see below snippet- #!/bin/bash .......## some code A #!/bin/csh .......## some code B exit 0; Here, code A will be executed using bash shell and code B will be executed with c shell. ... (9 Replies)
Discussion started by: tarunmudgal4u
9 Replies

9. Programming

Breakpoints dont work in Codeblocks, code does not build

Hey so I've written a program and it crashes every time I run it. I tried placing breakpoints to see what was going but to my surprise they do not work! I've placed them anywhere and they do not stop the execution of the program. In fact if I add code and hit rebuild it doesn't even build that... (1 Reply)
Discussion started by: Cambria
1 Replies

10. Shell Programming and Scripting

Dont want to mention user id passwd in shell script

Hi, i have one shell script which transfers files from one server to other server through FTP, but i can see login id and password is not mentioned. kindly help to understand the script.then how below script is working if login and password is not mentioned in script #!/bin/sh... (1 Reply)
Discussion started by: ni3b007
1 Replies
tkconrc(5)							File Formats Manual							tkconrc(5)

__________________________________________________________________________________________________________________________________________________

NAME
tkconrc - TkCon resource file DESCRIPTION
TkCon will search for a resource file in "~/.tkconrc". TkCon never sources the "~/.wishrc" file. The resource file is sourced by each new instance of the console. An example resource file is provided below. The file itself is a Tcl script, so it is required that the file conforms to Tcl script conventions. VARIABLES
Certain variables in TkCon can be modified to suit your needs. It's easiest to do this in the resource file, but you can do it when time the program is running (and some can be changed via the Prefs menu). All these are part of the master interpreter's ::tkcon namespace. The modifiable array variables are ::tkcon::COLOR and ::tkcon::OPT. You can call tkcon set ::tkcon::COLOR when the program is running to check its state. Here is an explanation of certain variables you might change or use: ::tkcon::COLOR(bg) The background color for tkcon text widgets. Defaults to the operating system default (determined at startup). ::tkcon::COLOR(blink) The background color of the electric brace highlighting, if on. Defaults to yellow. ::tkcon::COLOR(cursor) The background color for the insertion cursor in tkcon. Defaults to black. ::tkcon::COLOR(disabled) The foreground color for disabled menu items. Defaults to dark grey. ::tkcon::COLOR(proc) The foreground color of a recognized proc, if command highlighting is on. Defaults to dark green. ::tkcon::COLOR(var) The background color of a recognized var, if command highlighting is on. Defaults to pink. ::tkcon::COLOR(prompt) The foreground color of the prompt as output in the console. Defaults to brown. ::tkcon::COLOR(stdin) The foreground color of the stdin for the console. Defaults to black. ::tkcon::COLOR(stdout) The foreground color of the stdout as output in the console. Defaults to blue. ::tkcon::COLOR(stderr) The foreground color of stderr as output in the console. Defaults to red. ::tkcon::OPT(autoload) Packages to automatically load into the slave interpreter (i.e. 'Tk'). This is a list. Defaults to {} (none). ::tkcon::OPT(blinktime) The amount of time (in millisecs) that braced sections should blink for. Defaults to 500 (0.5 secs), must be at least 100. ::tkcon::OPT(blinkrange) Whether to blink the entire range for electric brace matching or to just blink the actual matching braces (respectively 1 or 0, defaults to 1). ::tkcon::OPT(buffer) The size of the console scroll buffer (in lines). Defaults to 512. ::tkcon::OPT(calcmode) Whether to allow expr commands to be run at the command line without prefixing them with expr (just a convenience). ::tkcon::OPT(cols) Number of columns for the console to start out with. Defaults to 80. ::tkcon::OPT(dead) What to do with dead connected interpreters. If dead is leave, TkCon automatically exits the dead interpreter. If dead is ignore then it remains attached waiting for the interpreter to reappear. Otherwise TkCon will prompt you. ::tkcon::OPT(exec) This corresponds to the -exec tkcon option (see tkcon(1)). ::tkcon::OPT(font) Font to use for tkcon text widgets (also specified with -font option). Defaults to the system default, or a fixed width equivalent. ::tkcon::OPT(gets) Controls whether tkcon will overload the gets command to work with tkcon. The valid values are: congets (the default), which will redirect stdin requests to the tkcon window; gets, which will pop up a dialog to get input; and {} (empty string) which tells tkcon not to overload gets. This value must be set at startup to alter tkcon's behavior. ::tkcon::OPT(history) The size of the history list to keep. Defaults to 48. ::tkcon::OPT(hoterrors) Whether hot errors are enabled or not. When enabled, errors that are returned to the console are marked with a link to the error info that will pop up in an minimal editor. This requires more memory because each error that occurs will maintain bindings for this feature, as long as the error is in the text widget. Defaults to on. ::tkcon::OPT(library) The path to any tcl library directories (these are appended to the auto_path when the after the resource file is loaded in). ::tkcon::OPT(lightbrace) Whether to use the brace highlighting feature or not (respectively 1 or 0, defaults to 1). ::tkcon::OPT(lightcmd) Whether to use the command highlighting feature or not (respectively 1 or 0, defaults to 1). ::tkcon::OPT(maineval) A tcl script to execute in the main interpreter after the slave interpreter is created and the user interface is initialized. ::tkcon::OPT(maxlinelen) A number that specifies the limit of long result lines. True result is still captured in $_ (and 'puts $_' works). Defaults to 0 (unlimited). ::tkcon::OPT(maxmenu) A number that specifies the maximum number of packages to show vertically in the Interp->Packages menu before breaking into another column. Defaults to 15. ::tkcon::OPT(nontcl) For those who might be using non-Tcl based Tk attachments, set this to 1. It prevents TkCon from trying to evaluate its own Tcl code in an attached interpreter. Also see my notes for non-Tcl based Tk interpreters. ::tkcon::OPT(prompt1) Like tcl_prompt1, except it doesn't require you use puts. No equivalent for tcl_prompt2 is available (it's unnecessary IMHO). Defaults to {([file tail [pwd]]) [history nextid] % }. ::tkcon::OPT(rows) Number of rows for the console to start out with. Defaults to 20. ::tkcon::OPT(scollypos) Y scrollbar position. Valid values are left or right. Defaults to right. ::tkcon::OPT(showmenu) Show the menubar on startup (1 or 0, defaults to 1). ::tkcon::OPT(showmultiple) Show multiple matches for path/proc/var name expansion (1 or 0, defaults to 1). ::tkcon::OPT(slaveeval) A tcl script to execute in each slave interpreter right after it's created. This allows the user to have user defined info always available in a slave. Example: set ::tkcon::OPT(slaveeval) { proc foo args { puts $args } lappend auto_path . } ::tkcon::OPT(slaveexit) Allows the prevention of exit in slaves from exitting the entire application. If it is equal to exit, exit will exit as usual, oth- erwise it will just close down that interpreter (and any children). Defaults to close. ::tkcon::OPT(subhistory) Allow history substitution to occur (0 or 1, defaults to 1). The history list is maintained in a single interpreter per TkCon con- sole instance. Thus you have history which can range over a series of attached interpreters. EXAMPLES
An example TkCon resource file might look like: ###################################################### ## My TkCon Resource File # Use a fixed default font #tkcon font fixed; # valid on unix #tkcon font systemfixed; # valid on win tkcon font Courier 12; # valid everywhere # Keep 50 commands in history set ::tkcon::OPT(history) 50 # Use a pink prompt set ::tkcon::COLOR(prompt) pink ###################################################### SEE ALSO
dump(n), idebug(n), observe(n), tkcon(1), tkcon(n) KEYWORDS
Tk, console COPYRIGHT
Copyright (c) Jeffrey Hobbs <jeff at hobbs.org> TkCon 2.5 tkconrc(5)
All times are GMT -4. The time now is 01:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy