01-14-2005
thank-you for the speedy reply.
When you re-install the OS do you need to supply a key for volume manager (we're using v2.6)
thank-you again
andy
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I've got a Linux box that I'm pretty sure is having some disk issues. iostat isn't installed, but vmstat is, so i've been trying to use that to do some initial diagnostics while I go through our company's change control process to get iostat installed.
The problem I'm having is that the disks... (4 Replies)
Discussion started by: kknigga
4 Replies
2. Solaris
DEVICE TYPE DISK GROUP STATUS
c0t0d0s2 sliced rootdisk rootdg online
c1t1d0s2 sliced disk01 rootdg online
c2t0d0s2 sliced actsvr101 actsvr1dg online
c2t2d0s2 sliced actsvr102 actsvr1dg online
c2t3d0s2 ... (13 Replies)
Discussion started by: incredible
13 Replies
3. Solaris
Hi,
Quick question if anyone knows this. Is there a command I can use in Veritas Volume manager on Solaris that will tell me what the name of the SAN I am connected to? We have a number of SANs so I am unsure which one my servers are connected to. Thanks. (13 Replies)
Discussion started by: gwhelan
13 Replies
4. Solaris
Hi Guys,
I have a doubt either to Reboot the server after Replacing the disk0.
I have two disks under vxvm root mirrored and i had a problem with primary disk so i replace the disk0 failed primary disk and then mirrored. After mirroring is it reboot required ? (7 Replies)
Discussion started by: kurva
7 Replies
5. Filesystems, Disks and Memory
:confused:
Last week I read that VxVM won't work with MPxIO (i don't recall the link) and that it should be unconfigured when installing VxVM. Today I read that VxVM works in "pass-thru" mode with MPxIO and DMP uses the devices presented by MPxIO.
If I create disks with MPxIO and use VxVM to... (1 Reply)
Discussion started by: bluescreen
1 Replies
6. Solaris
Hi community,
I've a hard question for you.
1)What are the differences between ZFS and Veritas Volume Manager on Solaris10?
2) what is the difference to manage the internal disks (Mirror)?
3) what is the difference to manage the external disks?
4) What is the difference to manage... (5 Replies)
Discussion started by: Sunb3
5 Replies
7. Solaris
Anyone knows that how many volumes can be created in a Diskgroup?
Thanks in advance... (1 Reply)
Discussion started by: bpsunadm
1 Replies
8. Solaris
hi all,
how can we check whether vxvm is installed in our system or not in solaris?
Thanks in advance
dinu (4 Replies)
Discussion started by: dinu
4 Replies
9. Emergency UNIX and Linux Support
I have VxVM 5.1 running on Solaris-10. I have to increase a application file-system and storage team gave me a lun. After scanning scsi port by cfgadm, I can see them in format output. I labelled it, but I am not able to see them in "vxdisk list".
I already tried commands -->
vxdctl enable... (4 Replies)
Discussion started by: solaris_1977
4 Replies
10. Solaris
Hi,
When we are running fsck in vxvm FS within few sec it will completed even if data is more than 500GB or in TB also.
compare to UFS FS in that it will take more time compare with vxvm.UFS check FS in block level. & then vvxm on where its checking the FS.
Please explain. (1 Reply)
Discussion started by: tiger09
1 Replies
LEARN ABOUT DEBIAN
speedy_backend
SPEEDY_BACKEND(1p) SPEEDY_BACKEND(1p)
NAME
speedy_backend - the backend process for a persistent Perl interpreter
SYNOPSIS
none ; this program is not meant to be called directly.
DESCRIPTION
speedy, short for SpeedyCGI, is a way to run perl scripts persistently, which can make them run much more quickly.
After the script is initially run, instead of exiting, the perl interpreter is kept running inside a backend process, speedy_backend. Dur-
ing subsequent runs, this interpreter is used to handle new executions instead of starting a new perl interpreter each time. A very fast
frontend program, speedy, written in C, is executed for each request. This fast frontend then contacts the persistent Perl process, which
is usually already running, to do the work and return the results.
Each perl script runs in its own Unix process, so one perl script can't interfere with another. Command line options can also be used to
deal with programs that have memory leaks or other problems that might keep them from otherwise running persistently.
The speedy front end connects to the back end process, speedy_backend, via a Unix socket in /tmp. A queue is kept in a shared file in /tmp
that holds an entry for each process. In that queue are the pids of the perl processes waiting for connections. The frontend pulls a
process out of this queue, connects to its socket, sends over the environment and argv, and then uses this socket for stdin/stdout to the
perl process.
FILES
/tmp/speedy* A unix socket used to connect to the frontend process.
AUTHOR
Sam Horrocks
http://daemoninc.com
sam@daemoninc.com
NOTES
This manual page was created by Niko Tyni <ntyni@iki.fi> for Debian GNU/Linux, because the original program does not have one. It is based
on the original and more complete CGI::SpeedyCGI(3pm) manual page.
SEE ALSO
perl(1), CGI::SpeedyCGI(3pm), speedy(1)
SPEEDY_BACKEND(1p)