Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Write to 1 failed [No space left on device] Error
Operating Systems Solaris Write to 1 failed [No space left on device] Error Post 303000749 by MadeInGermany on Wednesday 19th of July 2017 02:54:57 AM
Old 07-19-2017
Quote:
Originally Posted by bakunin
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:

Code:
  # prepend /usr/xpg4/bin to PATH as needed
  if ! echo "$PATH" | grep -q '\/usr\/xpg4\/bin' ; then
    PATH="/usr/xpg4/bin:${PATH}"

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
Code:
if echo x"${PATH}:" | grep '^x/usr/xpg4/bin:' >/dev/null
then
  :
else
  PATH="/usr/xpg4/bin:${PATH}"

Or
Code:
if expr x"${PATH}:" : x'/usr/xpg4/bin:' >/dev/null
then
  :
else
  PATH="/usr/xpg4/bin:${PATH}"

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.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

no space left on device

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)
Discussion started by: anjane
2 Replies

2. UNIX for Dummies Questions & Answers

cat: write error: No space left on device

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)
Discussion started by: igandu
3 Replies

3. Solaris

No space left on device but free space and inodes are available...

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)
Discussion started by: beta17
8 Replies

4. Solaris

visudo: write error: No space left on device

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)
Discussion started by: Sandeepgupta
13 Replies

5. HP-UX

Received error as Not enough space left on device

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)
Discussion started by: Nishant.Jvk
4 Replies

6. Shell Programming and Scripting

Write to 1 failed [No space left on device]

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)
Discussion started by: mahish20
6 Replies

7. AIX

Cpio: copy failed - No space left on device when I use rpm

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)
Discussion started by: tatab355
7 Replies

8. UNIX for Advanced & Expert Users

Sed: couldn't write 1378 items to stdout: No space left on device

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)
Discussion started by: mohan705
1 Replies

9. Linux

No space left on device while there is plenty of space available

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)
Discussion started by: umen
3 Replies

10. Solaris

Sol11 - Error at prompt (no space left on device)

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

getusershell

getusershell(3C)					   Standard C Library Functions 					  getusershell(3C)

NAME

       getusershell, setusershell, endusershell - get legal user shells

SYNOPSIS

       #include <unistd.h>

       char *getusershell(void);

       void setusershell(void);

       void endusershell(void);

DESCRIPTION

       The  getusershell()  function  returns  a  pointer  to  a  legal  user  shell  as defined by the system manager in the file /etc/shells. If
       /etc/shells does not exist, the following locations of the standard system shells are used in its place:

	 /bin/bash		    /bin/csh
	 /bin/jsh		    /bin/ksh
	 /bin/ksh93		    /bin/pfcsh
	 /bin/pfksh		    /bin/pfsh
	 /bin/sh		    /bin/tcsh
	 /bin/zsh		    /sbin/jsh
	 /sbin/pfsh		    /sbin/sh
	 /usr/bin/bash		    /usr/bin/csh
	 /usr/bin/jsh		    /usr/bin/ksh
	 /usr/bin/ksh93 	    /usr/bin/pfcsh
	 /usr/bin/pfksh 	    /usr/bin/pfsh
	 /usr/bin/sh		    /usr/bin/tcsh
	 /usr/bin/zsh		    /usr/sfw/bin/zsh
	 /usr/xpg4/bin/sh

       The getusershell() function opens the file /etc/shells, if it exists, and returns the next entry in the list of shells.

       The setusershell() function rewinds the file or the list.

       The endusershell() function closes the file, frees any memory used by getusershell() and setusershell(), and rewinds the file /etc/shells.

RETURN VALUES

       The getusershell() function returns a null pointer on EOF.

BUGS

       All information is contained in memory that may be freed with a call to endusershell(), so it must be copied if it is to be saved.

NOTES

       Restricted shells should not be listed in /etc/shells.

SunOS 5.11							    1 Nov 2007							  getusershell(3C)
All times are GMT -4. The time now is 04:25 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy