Sponsored Content
Top Forums Shell Programming and Scripting Error in the o/p says bad file descriptor... Post 302770453 by RudiC on Saturday 16th of February 2013 06:35:30 AM
Old 02-16-2013
I can't see where the while loop in your script in post #1 reads from; as is it would read from stdin which might be your terminal. Are you sure the variable dline holds a valid file name?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

bad file descriptor?

Ok, I'm sure this is a total newbie question, but I think I'm in the right place, no? I'm trying to call a perl module from a cgi script - Mail::Sendmail - and my web host installed the module in a directory that doesn't seem to be accessible, at least not the way I'm trying. But I thought you... (1 Reply)
Discussion started by: ftb
1 Replies

2. UNIX for Advanced & Expert Users

Script to search a bad record in a file then put the record in the bad file

I need to write a script that can find a bad record (for example: there is date field colom but value provided in the file for this field is N/A) then script shoud searches this pattern and then insert the whole record into the bad file. Example: File1 Name designation dateOfJoining... (1 Reply)
Discussion started by: shilendrajadon
1 Replies

3. Shell Programming and Scripting

Script to search a bad record in a file then put the record in the bad file

I need to write a script that can find a bad record (for example: there is date field colom but value provided in the file for this field is N/A) then script shoud searches this pattern and then insert the whole record into the bad file. Example: File1 Name designation dateOfJoining... (2 Replies)
Discussion started by: shilendrajadon
2 Replies

4. UNIX for Dummies Questions & Answers

File Descriptor

Hi What the below path contains? /proc/<pid>/fd (1 Reply)
Discussion started by: siba.s.nayak
1 Replies

5. Programming

utime returning -1 BAD File DEscriptor

Hi All, First of all thanks for reading this post. In my application, I am trying to create a new message queue . I am attaching the code below. mqd_t mqopen2(const char * pName, unsigned long Flags, long maxMsg, long msgSz) {... (15 Replies)
Discussion started by: parusasi
15 Replies

6. Ubuntu

ufsdump from Solaris to ubuntu fails with bad file descriptor

Hi All I have a dedicated backup server running ubuntu 10.04, which has recently been rebuilt (same OS, just different h/w) This is used to receive ufsdump output from a number of Solaris servers, using the following syntax: ufsdump 1uf :/path/to/backup/file /fs/to/be/backed/up This has... (1 Reply)
Discussion started by: in2deep
1 Replies

7. Solaris

18-Mar-2012 14:25:03.209 general: error: socket: file descriptor exceeds limit (4096/4096)

I have BIND 9.8.1-P1 cache only DNS server running in Solaris 10. I have upgraded the same from 9.6.1 to 9.8.1-P1. Now i am facing "file descriptor exceeds limit (4096/4096)" error frequently on the server. Please help me on this issue! (1 Reply)
Discussion started by: sandeep.tk
1 Replies

8. Solaris

Bad exchange descriptor : not able to remove files under zpool

Hi , One of my zone went down and when i booted it up i could see the pool in degraded state with some check sum errors . we have brought the pool online after scrubbing. But few files are showing this error Bad exchange descriptor Please let me know how to remove these files (2 Replies)
Discussion started by: chidori
2 Replies

9. Solaris

File System Error: BAD SUPERBLOCK AT BLOCK 16: NUMBER OF DIRECTORIES OUT OF RANGE

Hi All, we are having a file system error in one of our servers. The server failed to boot in usual user mode. Instead boot with single user mode and requesting to run a FSCK manually to repair the corrupted. see the below output. Netra T2000, No Keyboard Copyright 2008 Sun Microsystems,... (5 Replies)
Discussion started by: Buddhike G
5 Replies

10. UNIX for Beginners Questions & Answers

Bad file descriptor - error with sed

I'm learning SED command. And while doing that i got to this place where i'm taking a copy of my existing file. The code i used is - sed -n '/Storm/ w Storm.txt' books.txt As expected, the file 'books.txt' is read , and lines with 'Storm' is put in to the new file 'Storm.txt'. However, it also... (4 Replies)
Discussion started by: justo
4 Replies
WMANAGER-LOOP(1)					    BSD General Commands Manual 					  WMANAGER-LOOP(1)

NAME
wmanager-loop -- loop running window managers chosen with wmanager SYNOPSIS
wmanager-loop [OPTIONS ...] DESCRIPTION
The wmanager-loop program starts either the window manager specified by the WM variable or the first window manager listed in ~/.wmanagerrc (or an X terminal emulator if none), and when it exits, runs wmanager(1) to prompt the user for the next window manager. It loops doing this until the user chooses ``Exit this session'' in wmanager(1). Any options given to wmanager-loop will be passed on to wmanager(1). If the WM environment variable is set, the wmanager-loop program tries to interpret it as a window manager specification in the following ways in the specified order: o a full path to an executable file to run as the window manager; o the name of a window manager listed in the /.wmanagerrc file; e.g. ``fluxbox'' would match the following line: fluxbox=/usr/bin/startfluxbox o the program name of a window manager listed in the /.wmanagerrc file; e.g. ``startfluxbox'' would match the above example. o the start of such a program name; e.g. ``start'' would match the above example. o the end of such a program name; e.g. ``box'' would match the above example. If the WM variable is set and there is more than one line in ~/.wmanagerrc that matches the specification, wmanager-loop will exit with an error message. As mentioned above, if no window manager is specified in the WM environment variable or found in the ~/.wmanagerrc file, the wmanager-loop program attempts to start an X terminal emulator. If the WMTERM environment variable is set, the wmanager-loop program uses it as the path to the emulator. Otherwise it searches the user's path for a program named ``x-terminal-emulator'', ``urxvt'', ``rxvt'', or ``xterm'' in this order, and starts the first one found using its full path. If none of the common terminal emulators on the above list is found, the wmanager-loop program just runs ``xterm'' in the hope that something will come up on the user's display. ENVIRONMENT
The wmanager-loop program uses the following environment variables: WM The name, path, or partial path to the first window manager to execute. WMTERM The name of the X terminal emulator to execute if no window manager could be found in the ~/.wmanagerrc file. If not specified, the wmanager-loop program searches the user's path as described above. EXAMPLE
To start using wmanager-loop, create a ~/.wmanagerrc file - generally with wmanagerrc-update(1) - and add something like the following at the end of your ~/.xsession file: exec wmanager-loop -geometry +570+585 SEE ALSO
wmanager(1), wmanagerrc-update(1) HISTORY
The wmanager-loop program was written by Tommi Virtanen in 2000 and later modified by Peter Pentchev. This manual page was originally writ- ten in perldoc format by Tommi Virtanen in 2000, and converted to mdoc format and updated by Peter Pentchev in 2008. AUTHORS
Tommi Virtanen <tv@debian.org> Peter Pentchev <roam@ringlet.net> BSD
September 8, 2009 BSD
All times are GMT -4. The time now is 04:08 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy