Sponsored Content
Full Discussion: IPC - queue problems
Top Forums Programming IPC - queue problems Post 5624 by Neo on Saturday 18th of August 2001 09:53:43 PM
Old 08-18-2001
There are too many things that can go wrong and your question is too broad. Lot's of things can go wrong and it would be pointless to guess Smilie
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Print Queue Problems

Hi All Does anyone know what is meant by PRINTER STATUS CONNECT concerning print queues? At work we run a Perle/Connectix JetStream 8500 (RJ45 Model) to connect our dot matrix printers and often we get the Connect Status. Nobody I speak to knows what the status means. When the printer... (0 Replies)
Discussion started by: nickbungus
0 Replies

2. HP-UX

posix ipc message queue

Hello, My question is related to "pipcs -qa" command under HP-UX 11i PA-RISC 64 bits. We have a little C program that creates posix ipc message queues using the mq_open() system function. The program fail with 'No space left on device' error when we create big queues. What is the system... (6 Replies)
Discussion started by: cadanir
6 Replies

3. UNIX for Advanced & Expert Users

System V IPC problems

Hi all, Is there a situation like system assigning same ID's for semaphores and shared memory at the same time. Ex: When I try to create 10 Shared memory objects with starting key as 0x1500 and 10 semaphore objects with starting key as 0x1234 in the same program. Assume those are not deleted... (2 Replies)
Discussion started by: gkreddy
2 Replies

4. SCO

Sco openserver 5 print queue problems

Hwey I manage a Unix box where I ama having multiple printer problems. the only way to get printers to print again is by rebooting. I stop and start services with no luck. Any one have any ideas? It can go weeks with being OK but then any given printer can go and cause the entire print queue to... (6 Replies)
Discussion started by: uk2us88
6 Replies

5. UNIX for Dummies Questions & Answers

IPC Message Queue. msgrcv doesnt work..

Hi everybody, this is the situation. there is a programm XYZ which opens a message queue with the key 47110815 and waits for a SIGUSR1. After receiving this signal it sends a message with type 100 and a number (as ASCII) in the message-body. I have to write a prog which frist sends the... (1 Reply)
Discussion started by: daredevil82m
1 Replies

6. UNIX for Dummies Questions & Answers

g03 problems on rocks 5.3 with sge queue.

Dear all, I'm a new guy doing some quntum calculation with gaussian on my rocks clusters. Recently, my cluster upgraded to rocks 5.3, but something strange happened. Everything goes correct except a serious problem. when I summit my gaussian job with script to sge queue, the job does run,... (0 Replies)
Discussion started by: liuzhencc
0 Replies

7. Solaris

errors on Netra-440: "IPC Warning: ipc: tcp_protocol: bad magic number"

I was asked to look into a problem with a Sun Netra 440 in another department. On the server in question, the relevant 'uname -a' information is, "SunOS host1 5.9 Generic_118558-16 sun4u sparc SUNW,Netra-440". That information aside, while the other admin is logged into the ALOM, these errors are... (0 Replies)
Discussion started by: Borealis
0 Replies

8. AIX

Queue problems

Hi, We have a problem with remote printers installed on our server. Consistently, the printer status is ready but the impressions of the queue are waiting therefore blocked. To unblock the situation, we must launch stopsrc qdaemon-s-s and startsrc qdaemon to reactivate the queue. Thank you... (2 Replies)
Discussion started by: GBAGO
2 Replies

9. AIX

Print queue problems

I am using AIX 5. Just swapped over an HP printer. The old printer was on a JetDirect box. The new printer connects directly to the network. Using the same IP address to print to, so the only alteration I made was to edit the etc/qconfig file to alter the port setting from 9103 to 9100. I can... (2 Replies)
Discussion started by: charding
2 Replies

10. Programming

Problems with pipe IPC

I'm currently studying IPC, I have a first program A: Do an exec for B and wait B: Receive through a fifo a string from a third program "C" and have to resend it to A I was thinking to open a pipe in A before the exec, then passing fd to B as an argument if(pipe(fd)==-1){ ... (1 Reply)
Discussion started by: cifz
1 Replies
Perl::Critic::Policy::Subroutines::RequireFinalReturn(3)User Contributed Perl DocumentatioPerl::Critic::Policy::Subroutines::RequireFinalReturn(3)

NAME
Perl::Critic::Policy::Subroutines::RequireFinalReturn - End every path through a subroutine with an explicit "return" statement. AFFILIATION
This Policy is part of the core Perl::Critic distribution. DESCRIPTION
Require all subroutines to terminate explicitly with one of the following: "return", "carp", "croak", "die", "exec", "exit", "goto", or "throw". Subroutines without explicit return statements at their ends can be confusing. It can be challenging to deduce what the return value will be. Furthermore, if the programmer did not mean for there to be a significant return value, and omits a return statement, some of the subroutine's inner data can leak to the outside. Consider this case: package Password; # every time the user guesses the password wrong, its value # is rotated by one character my $password; sub set_password { $password = shift; } sub check_password { my $guess = shift; if ($guess eq $password) { unlock_secrets(); } else { $password = (substr $password, 1).(substr $password, 0, 1); } } 1; In this case, the last statement in check_password() is the assignment. The result of that assignment is the implicit return value, so a wrong guess returns the right password! Adding a "return;" at the end of that subroutine solves the problem. The only exception allowed is an empty subroutine. Be careful when fixing problems identified by this Policy; don't blindly put a "return;" statement at the end of every subroutine. CONFIGURATION
If you've created your own terminal functions that behave like "die" or "exit", then you can configure Perl::Critic to recognize those functions as well. Just put something like this in your .perlcriticrc: [Subroutines::RequireFinalReturn] terminal_funcs = quit abort bailout BUGS
We do not look for returns inside ternary operators. That construction is too complicated to analyze right now. Besides, a better form is the return outside of the ternary like this: "return foo ? 1 : bar ? 2 : 3" AUTHOR
Chris Dolan <cdolan@cpan.org> COPYRIGHT
Copyright (c) 2005-2011 Chris Dolan. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. The full text of this license can be found in the LICENSE file included with this module. perl v5.16.3 2014-06-09 Perl::Critic::Policy::Subroutines::RequireFinalReturn(3)
All times are GMT -4. The time now is 09:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy