Sponsored Content
Operating Systems Solaris Broken Pipe: executing a binary application Post 302907732 by Wpgn on Tuesday 1st of July 2014 10:27:36 AM
Old 07-01-2014
Unfortunately am not permitted to post the full code due to legal reasons with 4anything who I have signed a contract with to obtain the software.

when I run the console and it just a blank window there no output or anything it just don't start at all, I did ldd -d mcp and it shows all needed files are there so on I just think it must be a issue with the sh console and I don't no how to run it in debug mode am not a solaris person really am still learning.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

broken pipe?

Hi there, I try to use: > find * | ls but it just gave me one level of ' ls '. and it said: > find * | ls dir1 dir2 f1 f2 f3 Broken Pipe > what is broken pipe? how can i fix it? thks Gusla (3 Replies)
Discussion started by: gusla
3 Replies

2. UNIX for Dummies Questions & Answers

broken pipe

sometimes I ftp files from an Unix environment from the command prompt of my win2000 pc and I get a "broken pipe" message. sometimes I'll get nothing but sometimes I'll get part of the file. Whats this "broken pipe" about?? (3 Replies)
Discussion started by: eloquent99
3 Replies

3. UNIX for Advanced & Expert Users

Broken Pipe

Hi I tried to open the man page of sh and piped to `pg`. Normally while reading a file page by page using `pg`, if we wanna quit at the middle of file, we give "q" near the colon mode. Ex1: $cat file1 | pg hi how r u : (page1) now press "return key", it will go to next page yes i ... (1 Reply)
Discussion started by: ramkrix
1 Replies

4. UNIX for Dummies Questions & Answers

Broken Pipe

Hi I tried to open the man page of sh and piped to `pg`. Normally while reading a file page by page using `pg`, if we wanna quit at the middle of file, we give "q" near the colon mode. Ex1: $cat file1 | pg hi how r u : (page1) now press "return key", it will go to next page yes i ... (3 Replies)
Discussion started by: ramkrix
3 Replies

5. Linux

pipe broken

hi i have a server, and i have a web site and i installed apache in the /usr/local/apache/logs i have a file and i have this problem (32)Broken pipe: core_output_filter: writing data to the network plz help me how i can resolve this plz it's urgent th (2 Replies)
Discussion started by: abir2
2 Replies

6. UNIX and Linux Applications

pipe broken

hi i have a server, and i have a web site and i installed apache in the /usr/local/apache/logs i have a file and i have this problem (32)Broken pipe: core_output_filter: writing data to the network plz help me how i can resolve this plz it's urgent th (1 Reply)
Discussion started by: abir2
1 Replies

7. Shell Programming and Scripting

broken pipe

hi i am trying to upload a file using ftp protocol, i am facing some problem while uploading "Failedtoupload:SFTREGUP1:FTP_ASCII_MAILBOX21.39.10.856305000:Broken pipe" Can someone explain why it is coming , and the solution . (0 Replies)
Discussion started by: Satyak
0 Replies

8. Shell Programming and Scripting

Replace pipe with Broken Pipe

Hi All , Is there any way to replace the pipe ( | ) with the broken pipe (0xA6) in unix (1 Reply)
Discussion started by: saj
1 Replies

9. UNIX for Dummies Questions & Answers

broken pipe

I know what causes 'broken pipe' errors, but I can't understand why I can get it (only occasionally) with my example: ps -ef | grep "\./ans$" | grep -v grep Basically I'm searching the ps output looking for the process I'm interested in and excluding the process that is grepping for the... (2 Replies)
Discussion started by: fhew
2 Replies

10. Red Hat

Broken pipe

Hi all, I am trying to run a sleep command and I am receiving a broken pipe when I execute. any help would be greatly appreciated. sleep `< /dev/urandom tr -dc 0-6 | head -c2` (2 Replies)
Discussion started by: gartie
2 Replies
vga_init(3)							Svgalib User Manual						       vga_init(3)

NAME
vga_init - initialize svgalib library SYNOPSIS
#include <vga.h> int vga_init(void); DESCRIPTION
It detects the chipset and gives up supervisor rights. This is the recommended first line of any program that uses svgalib. vga_setchipset(3) can be called before it to avoid detection. Svgalib catches a bunch of signals that usually kill your program to restore textmode. If you catch signal's before calling vga_init() svgalib will restore textmode and prepare for shutdown and then call your handler routine. If you don't want this, catch the signal after calling vga_init and do not daisychain to svgalib's original handler. WARNING! svgalib needs two signals for it's own purposes (that is managing console switches). To avoid problems it uses the otherwise unused signals SIGUSR1 and SIGUSR2. However, this means that you cannot use them in your program by any means. They are setup by vga_init() as everything else is. Since version 1.2.11 vga_init() includes code to hunt for a free virtual console on its own in case you are not starting the program from one (but instead over a network or modem login, from within 'screen' or an 'xterm'). Provided there is a free console, this succeeds if you are root or if the svgalib calling user own the current console. This is to avoid people not using the console being able to fiddle with it. On graceful exit the program returns to the console from which it was started. Otherwise it remains in text mode at the VC which svgalib allocated to allow you to see any error messages. In any case, any I/O the svgalib makes in text mode (after calling vga_init) will also take place at this new console. Alas, some games misuse their suid root priviledge and run as full root process. svgalib cannot detect this and allows Joe Blow User to open a new VC on the console. If this annoys you ROOT_VC_SHORTCUT in Makefile.cfg allows you to disable allocating a new VC for root (except when he owns the current console) when compiling svgalib. This is the default (disabling the allocation for root). vga_init() returns a non-zero value in case of errors. As of this writing it will return -1 if it is unable to allocate a graphical con- sole. Otherwise, 0 is returned. BUGS
Svgalib versions prior to 1.2.11 had a security hole where it would be possible to regain root priviledges even after a vga_init() call. This is not necessarily a problem, but if your program is vulnerable to buffer overflows and other attacks, an attacker may exploit this. However, prior to your call, your program will need to run setuid root, so you should be very careful. The ioperm library by Olaf Titz will allow svgalib programs to run not setuid root. However, it gives all programs unlimited access to the hardware. Again, a malicious person can exploit this (albeit a bit more difficult) too. Thus, in general, make your svgalib programs as secure as any setuid root program. Some programs may (accidently) rely on the old behaviour (which was probably due to the author not knowing about saved uids (which might actually even not have existed in Linux at that time)). A line: security compat in the configuration file /etc/vga/libvga.conf will reinstate the old behaviour whereas security revoke-all-privs enables the (currently default) action. SEE ALSO
svgalib(7), vga_setmode(3), mouse_init(3), vga_claimvideomemory(3), vga_ext_set(3), vga_fillblt(3), vga_getcurrentchipset(3), vga_getde- faultmode(3), vga_getgraphmem(3), vga_runinbackground(3), vga_runinbackground_version(3), vga_safety_fork(3), vga_setchipset(3), vga_setchipsetandfeatures(3), vgagl(7), libvga.config(5), AUTHOR
This manual page was edited by Michael Weller <eowmob@exp-math.uni-essen.de>. The exact source of the referenced function as well as of the original documentation is unknown. It is very likely that both are at least to some extent are due to Harm Hanemaayer <H.Hanemaayer@inter.nl.net>. Occasionally this might be wrong. I hereby asked to be excused by the original author and will happily accept any additions or corrections to this first version of the svgalib manual. Svgalib (>;= 1.2.11) 27 July 1997 vga_init(3)
All times are GMT -4. The time now is 04:39 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy