Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: test command looks strange...
Top Forums Shell Programming and Scripting test command looks strange... Post 302143720 by porter on Friday 2nd of November 2007 07:24:10 PM
Old 11-02-2007
Quote:
Originally Posted by jjinno
I just ran into this today, and don't know what to make of it...
Code:
if test x$SERVER = x
then
        echo $USAGE
        exit 1
fi

I know what everything in there does, except for the 'x' jazz...
It is effecitvely doing

Code:
if test "$SERVER" = ""
then
     ....

rather than using quotes, it prefixes an x to the string to ensure it's not an empty string argument. Where it falls down of course is if there is a space in $SERVER.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Strange error message with regex test...

Hi all, I have a script where i need to check the format of a string. finally, i'm waiting a "process name" and 2 numbers separated by a "," string like : "this_is_a_string.txt,1,10 should be ok" string ok : "apache.exe,1,10" string ok : "mysqld,50,0" string not ok : "ap ache,1,10"... (4 Replies)
Discussion started by: fgilain
4 Replies

2. UNIX for Advanced & Expert Users

Sort command - strange behaviour

Hi guys, I have the following example data: A;00:00:19 B;00:01:02 C;00:00:13 D;00:00:16 E;00:02:27 F;00:00:12 G;00:00:21 H;00:00:19 I;00:00:13 J;00:13:22 I run the following sort against it, yet the output is as follows: sort -t";" +1 -nr example_data.dat A;00:00:19 (16 Replies)
Discussion started by: miwinter
16 Replies

3. Programming

a strange segment fault about ltp-posix test

Hi all In the ltp-posix test,there is a case in open_posix_testsuite\conformance\interfaces\timer_gettime\speculative/6-1.c I run the above code,it will has a segment fault, if I modify it to below,it works well Anybody can tell me why? (1 Reply)
Discussion started by: yanglei_fage
1 Replies

4. Shell Programming and Scripting

Test on string containing spacewhile test 1 -eq 1 do read a $a if test $a = quitC then break fi d

This is the code: while test 1 -eq 1 do read a $a if test $a = stop then break fi done I read a command on every loop an execute it. I check if the string equals the word stop to end the loop,but it say that I gave too many arguments to test. For example echo hello. Now the... (1 Reply)
Discussion started by: Max89
1 Replies

5. Shell Programming and Scripting

How to check weather a string is like test* or test* ot *test* in if condition

How to check weather a string is like test* or test* ot *test* in if condition (5 Replies)
Discussion started by: johnjerome
5 Replies

6. Solaris

Getting strange output of who -r command

Hi At OK> prompt, I have run the boot -s command After system is coming on to multiuser state, when I run the " who -r" command, I get the following message # who -r run-level Oct 17 03:48 last= Means I dont see "S" after run-level keyword. Could any one... (2 Replies)
Discussion started by: amity
2 Replies

7. UNIX for Dummies Questions & Answers

Strange cat command

What does the below statement means ? cat "$1" > /tmp/file.$$ 2>/tmp/file0.$$ Please help. (3 Replies)
Discussion started by: csrohit
3 Replies

8. UNIX for Dummies Questions & Answers

Strange result using find command.

I created a file with the permissions of 776. When I ran the command find /root/Desktop -perm -644 -type f The created file shows up as part of the results. Doesn't -perm -mode mean that for global, only 4(read) and 2(write) can be accepted ? (2 Replies)
Discussion started by: Hijanoqu
2 Replies

9. Shell Programming and Scripting

Find with rm command gives strange results

I want to remove any files that are older than 2 days from a directory. It deletes those files. Then it comes back with a message it is a directory. What am I doing wrong here? + find /mydir -mtime +2 -exec rm -f '{}' ';' rm: /mydir is a directory (2 Replies)
Discussion started by: jtamminen
2 Replies

10. UNIX for Advanced & Expert Users

Strange behavior from kill command

I am getting some strange behaviour from the kill command. When I run the which command it says it points to /usr/bin/kill. When I look at my PATH I have /usr/bin in it. So why does running kill or /usr/bin/kill produce different outputs? ghost ~ $ which kill /usr/bin/kill ghost ~ $ kill... (5 Replies)
Discussion started by: cokedude
5 Replies

LEARN ABOUT DEBIAN

ods-server

ODS-SERVER(1)							   User Commands						     ODS-SERVER(1)

NAME

       ods-server - minimal OBEX server based on obex-data-server

SYNOPSIS

       ods-server [options] profile path

DESCRIPTION

       ods-server  provides a minimal OBEX server based on obex-data-server for receiving files over bluetooth.  profile selects the UUID-128 pro-
       file ID to use, currently opp and ftp can be used as aliases for object push and obex ftp respectively.	path is the target  directory  for
       received files.

OPTIONS

       -h, --help
	      show this help message and exit

       -l ADDRESS, --local=ADDRESS
	      ADDRESS of Bluetooth adapter to listen on. Default is 00:00:00:00:00:00

       -p, --pairing
	      Require remote devices to be paired before allowing them to connect. Disabled by default

       -r, --readonly
	      Disallow any write operations. Allowed by default

       -t, --thumbnails
	      Require remote device to send thumbnails when using Imaging (BIP) server

       -a, --ask-to-accept
	      Prompt user to accept or reject every file. By default all files are accepted

AUTHOR

       ods-server was written by Tadas Dailyda <tadas@dailyda.com> and is shipped as ods-server-test.py in the obex-data-server distribution

       This manual page was written by Filippo Giunchedi <filippo@debian.org> for the Debian project (but may be used by others).

ods-server 0.4.4						     May 2009							     ODS-SERVER(1)
All times are GMT -4. The time now is 06:08 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy