03-20-2009
Hey tdiYUZER
Thats something new to me.. Will check and get back..
Thanks
Bala
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
When I do a hard reboot, the system recognizes both the ttya and the ttyb, but when I do a hard reboot, it only doesn't recognize the ttyb. Is there a way I can fix this???
Thanks!:confused: (5 Replies)
Discussion started by: nattie_h
5 Replies
2. UNIX for Advanced & Expert Users
Hi !
I am working on a server. We have ABAQUS installed on it. I added a compiler to .env file and added usr/local...../IMSL/... to the path.
Then i restarted the computer and I get this error:
when I am doing interactive option (Red hat Lunix OS)
Start service local Yes/no/Continue? no... (1 Reply)
Discussion started by: dsmv
1 Replies
3. UNIX for Dummies Questions & Answers
O/P of the uname -a
Server Server 4.0 3.0 3516 Pentium IV(TM)-ISA/PCI
Server is getting rebooted frequetly...
I don't know what is the problem in server ...
Any help why the server is getting rebooted frequetly.
Can i check what is the problem like in log files (5 Replies)
Discussion started by: srikanthus2002
5 Replies
4. Solaris
while installing unix solaris I found that one of the CD's is corupted so I bring another copy of solaris CD's and type reboot instead of 'reboot cdrom' then the server goes in infinite loop of rebooting resetting??I tried to use ctrl+break but didnt work....how can I break this loop....plz help?? (4 Replies)
Discussion started by: mm00123
4 Replies
5. Shell Programming and Scripting
Hi All,
I have created one script with starting letter 'S' (Example: Start) and stored in the path "/etc/rc.d/".
This script was called automatically when we reboot the server.
In this script i am using 'su' command to switch other user but it is not working, it giving some error.
su... (2 Replies)
Discussion started by: Selva_Kumar
2 Replies
6. Linux
Hi All,
We have two servers DSERV1(red hat 8.0) and DSERV2(scounix 3.2) where DSERV1 is the NFS server and DSERV2 is the NFS client. We want to reboot these servers and wanted to know the steps(precautions) we have to follow in order to do this. After reboot should we do anything specific to... (2 Replies)
Discussion started by: jisha
2 Replies
7. Solaris
I got following while whenver i reboot my box
WARNING: add_spec: No major number for hpfc
WARNING: add_spec: No major number for hpfc
Error: Unable to init open counts. Kernel struct change?
and hpfc is related to agilent fiber channel driver .. i do not know why it requires as i 've... (1 Reply)
Discussion started by: fugitive
1 Replies
8. Red Hat
hi,
I have been working on Solaris am very new to linux. My concern is as it goes....our server is getting rebooted automatically and I am not able to understand anything from the var log messages. Could anybody help me out in troubleshooting the issue.
2.6.18-128.el5 #1 x86_64 GNU/Linux is... (1 Reply)
Discussion started by: EmbedUX
1 Replies
9. AIX
Hi,
I would like to know wheather rebooting HMC will impact on Management Systems or Lpar inside it is showing?
or I have to shutdown LPAR then only reboot HMC. (7 Replies)
Discussion started by: manoj.solaris
7 Replies
10. What is on Your Mind?
Apologies if this is not the correct place to post this.
I used to have a job supporting several custom applications that ran on Unix platforms. I used shell scripting, sed, awk, and SQL, but all on a pretty basic level. I also performed non-technical tasks like helping with project management,... (4 Replies)
Discussion started by: intranslation
4 Replies
LEARN ABOUT MOJAVE
io::wrap
IO::Wrap(3) User Contributed Perl Documentation IO::Wrap(3)
NAME
IO::Wrap - wrap raw filehandles in IO::Handle interface
SYNOPSIS
use IO::Wrap;
### Do stuff with any kind of filehandle (including a bare globref), or
### any kind of blessed object that responds to a print() message.
###
sub do_stuff {
my $fh = shift;
### At this point, we have no idea what the user gave us...
### a globref? a FileHandle? a scalar filehandle name?
$fh = wraphandle($fh);
### At this point, we know we have an IO::Handle-like object!
$fh->print("Hey there!");
...
}
DESCRIPTION
Let's say you want to write some code which does I/O, but you don't want to force the caller to provide you with a FileHandle or IO::Handle
object. You want them to be able to say:
do_stuff(*STDOUT);
do_stuff('STDERR');
do_stuff($some_FileHandle_object);
do_stuff($some_IO_Handle_object);
And even:
do_stuff($any_object_with_a_print_method);
Sure, one way to do it is to force the caller to use tiehandle(). But that puts the burden on them. Another way to do it is to use
IO::Wrap, which provides you with the following functions:
wraphandle SCALAR
This function will take a single argument, and "wrap" it based on what it seems to be...
o A raw scalar filehandle name, like "STDOUT" or "Class::HANDLE". In this case, the filehandle name is wrapped in an IO::Wrap
object, which is returned.
o A raw filehandle glob, like "*STDOUT". In this case, the filehandle glob is wrapped in an IO::Wrap object, which is returned.
o A blessed FileHandle object. In this case, the FileHandle is wrapped in an IO::Wrap object if and only if your FileHandle class
does not support the "read()" method.
o Any other kind of blessed object, which is assumed to be already conformant to the IO::Handle interface. In this case, you just
get back that object.
If you get back an IO::Wrap object, it will obey a basic subset of the IO:: interface. That is, the following methods (note: I said
methods, not named operators) should work on the thing you get back:
close
getline
getlines
print ARGS...
read BUFFER,NBYTES
seek POS,WHENCE
tell
NOTES
Clearly, when wrapping a raw external filehandle (like *STDOUT), I didn't want to close the file descriptor when the "wrapper" object is
destroyed... since the user might not appreciate that! Hence, there's no DESTROY method in this class.
When wrapping a FileHandle object, however, I believe that Perl will invoke the FileHandle::DESTROY when the last reference goes away, so
in that case, the filehandle is closed if the wrapped FileHandle really was the last reference to it.
WARNINGS
This module does not allow you to wrap filehandle names which are given as strings that lack the package they were opened in. That is, if a
user opens FOO in package Foo, they must pass it to you either as "*FOO" or as "Foo::FOO". However, "STDIN" and friends will work just
fine.
VERSION
$Id: Wrap.pm,v 1.2 2005/02/10 21:21:53 dfs Exp $
AUTHOR
Primary Maintainer
David F. Skoll (dfs@roaringpenguin.com).
Original Author
Eryq (eryq@zeegee.com). President, ZeeGee Software Inc (http://www.zeegee.com).
POD ERRORS
Hey! The above document had some coding errors, which are explained below:
Around line 212:
'=item' outside of any '=over'
=over without closing =back
perl v5.18.2 2005-02-10 IO::Wrap(3)