I have no idea what that is supposed to do, but: whatever it is, it should be done differently. Anyway, the only program external to the shell called in this part is the expr command, the rest is just variable manipulation inside the shell, which can't cause the error you are describing.
Either the error comes from somewhere else or it comes from line 3 of the part you have shown. But again: whatever it is supposed to do, i doubt that it does it and i am sure that even if it would do it it should be done differently.
If this is supposed to test if the path /usr/xpg4/bin is alraedy in the PATH it should be:
instead of these ridiculous expr-gymnastics.
I hope this helps.
bakunin
That's not quite correct. Unlike grep, expr searches from the beginning.
The following is correct
Or
Also avoids potential problems with Solaris 10 /bin/sh and /bin/grep, and with strange characters in PATH.
But the original is okay. As was already stated, the problem is elsewhere.
I have a SCO UNIX on my Server. When I last tried to shutdown my system, I got an error message
“no space left on device”.
Now when I try to boot the system again, I
just can't and I get the same error message. Please help! (2 Replies)
I am trying to create new files under my directory...but i getting the following message...
cat: write error: No space left on device
How do we handle this error.
I am not getting this error when I login as the super user (3 Replies)
hi guys, me again ;)
i recently opened a thread about physical to zone migration.
My zone is mounted over a "bigger" LUN (500GB) and step is now to move the old files, from the physical server, to my zone.
We are talking about 22mio of files.
i used rsync to do that and every time at... (8 Replies)
Hi All,
This is Sandeep Gupta,
I am facing a problem with sudo command.
Whenever i am executing the command "visudo" i am getting the error "visudo: write error: No space left on device".
but i have checked on my Solaris Box everything is ok, i have enough free space on my box, and also... (13 Replies)
Hi Forum,
We have observed one problem in one of our HP-UX machines which runs a software which connects the radio frequency scan devices and the scanned information is stored in the database through the same software.
This software has thrown an error like "Not enough space left on the... (4 Replies)
I am getting error in a shell script having a simple date command.
Error is " write to 1 failed ".
We saw that /tmp folder was 100% full. When we cleared some space in /tmp folder then script worked fine. Why does date command(or any other command) require space in /tmp folder? Which settings... (6 Replies)
Hello,
I want to install GCC gcc-4.8.1-2.src.rpm for AIX 6.1
when I lance my command rpm -i gcc-4.8.1-2.src.rpm
I have this error
unpacking of archive failed on file gcc-4.8.1.tar.bz2: cpio: copy failed - No space left on device
I checked the free space and I am surpise becouse I have... (7 Replies)
Hi ,
In file first line start with "",when trying to remove using sed i am getting the below error .Please advise
sed -e 's///g' -e 's/$]//g' segment1.txt >>segment_m1
sed: couldn't write 1378 items to stdout: No space left on device
Thanks,
Mohan (1 Reply)
Hello all
posting here after scanning the net and tried most of the things offered
still no solution that worked
when I do :
$ df -h
Filesystem Size Used Avail Use% Mounted on
footmpfs 7.9G 60K 7.9G 1% /dev
tmpfs 7.9G 0 7.9G 0% /dev/shm
/dev/da1 ... (3 Replies)
user1@:/$
-ksh: line 3: write to 1 failed
user11@:/$
-ksh: line 3: write to 1 failed
user1@:/$
-ksh: line 3: write to 1 failed
user1@:/$
-ksh: line 3: write to 1 failed
user1@:/$
-ksh: line 3: write to 1 failed But theres plenty of space :-
user1@:/$ df -kh
Filesystem ... (9 Replies)
Discussion started by: psychocandy
9 Replies
LEARN ABOUT OPENSOLARIS
fgrep
fgrep(1) User Commands fgrep(1)NAME
fgrep - search a file for a fixed-character string
SYNOPSIS
/usr/bin/fgrep [-bchilnsvx] -e pattern_list [file...]
/usr/bin/fgrep [-bchilnsvx] -f file [file...]
/usr/bin/fgrep [-bchilnsvx] pattern [file...]
/usr/xpg4/bin/fgrep [-bchilnqsvx] -e pattern_list [-f file]
[file...]
/usr/xpg4/bin/fgrep [-bchilnqsvx] [-e pattern_list] -f file
[file...]
/usr/xpg4/bin/fgrep [-bchilnqsvx] pattern [file...]
DESCRIPTION
The fgrep (fast grep) utility searches files for a character string and prints all lines that contain that string. fgrep is different from
grep(1) and from egrep(1) because it searches for a string, instead of searching for a pattern that matches an expression. fgrep uses a
fast and compact algorithm.
The characters $, *, [, ^, |, (, ), and are interpreted literally by fgrep, that is, fgrep does not recognize full regular expressions as
does egrep. These characters have special meaning to the shell. Therefore, to be safe, enclose the entire string within single quotes (a').
If no files are specified, fgrep assumes standard input. Normally, each line that is found is copied to the standard output. The file name
is printed before each line that is found if there is more than one input file.
OPTIONS
The following options are supported for both /usr/bin/fgrep and /usr/xpg4/bin/fgrep:
-b Precedes each line by the block number on which the line was found. This can be useful in locating block numbers by con-
text. The first block is 0.
-c Prints only a count of the lines that contain the pattern.
-e pattern_list Searches for a string in pattern-list. This is useful when the string begins with a -.
-f pattern-file Takes the list of patterns from pattern-file.
-h Suppresses printing of files when searching multiple files.
-i Ignores upper/lower case distinction during comparisons.
-l Prints the names of files with matching lines once, separated by new-lines. Does not repeat the names of files when the
pattern is found more than once.
-n Precedes each line by its line number in the file. The first line is 1.
-s Works silently, that is, displays nothing except error messages. This is useful for checking the error status.
-v Prints all lines except those that contain the pattern.
-x Prints only lines that are matched entirely.
/usr/xpg4/bin/fgrep
The following options are supported for /usr/xpg4/bin/fgrep only:
-q Quiet. Does not write anything to the standard output, regardless of matching lines. Exits with zero status if an input line is
selected.
OPERANDS
The following operands are supported:
file Specifies a path name of a file to be searched for the patterns. If no file operands are specified, the standard input will be
used.
/usr/bin/fgrep
pattern Specifies a pattern to be used during the search for input.
/usr/xpg4/bin/fgrep
pattern Specifies one or more patterns to be used during the search for input. This operand is treated as if it were specified as -e
pattern_list.
USAGE
See largefile(5) for the description of the behavior of fgrep when encountering files greater than or equal to 2 Gbyte ( 2^31 bytes).
ENVIRONMENT VARIABLES
See environ(5) for descriptions of the following environment variables that affect the execution of fgrep: LC_COLLATE, LC_CTYPE, LC_MES-
SAGES, and NLSPATH.
EXIT STATUS
The following exit values are returned:
0 If any matches are found
1 If no matches are found
2 For syntax errors or inaccessible files, even if matches were found.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
/usr/bin/fgrep
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
/usr/xpg4/bin/fgrep
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWxcu4 |
+-----------------------------+-----------------------------+
|CSI |Enabled |
+-----------------------------+-----------------------------+
SEE ALSO ed(1), egrep(1), grep(1), sed(1), sh(1), attributes(5), environ(5), largefile(5), XPG4(5)NOTES
Ideally, there should be only one grep command, but there is not a single algorithm that spans a wide enough range of space-time tradeoffs.
Lines are limited only by the size of the available virtual memory.
/usr/xpg4/bin/fgrep
The /usr/xpg4/bin/fgrep utility is identical to /usr/xpg4/bin/grep -F (see grep(1)). Portable applications should use /usr/xpg4/bin/grep
-F.
SunOS 5.11 24 Mar 2006 fgrep(1)