05-16-2005
9 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I removed an external Sun disk (with data on it) from an old 2.6 system and added the disk to another 2.6 system. The new system seems to recognize the system (verified by the format command).
When try to mount I am getting, I got the error:
mount: /dev/dsk/c1t1d0s6 is not this fstype.
I... (3 Replies)
Discussion started by: sunshine
3 Replies
2. Shell Programming and Scripting
I have a file --> file1.txt
i need to copy this file to another server using FTP....the 2 servers are server1 and server2..may i know how to write a script that can do this?
thanks in advance! Im a newbie to this... (4 Replies)
Discussion started by: forevercalz
4 Replies
3. Solaris
Hi,
df -h display:
# df -h
Filesystem size used avail capacity Mounted on
/dev/dsk/c1t0d0s0 9.8G 8.1G 1.7G 84% /
/proc 0K 0K 0K 0% /proc
mnttab 0K 0K 0K 0% /etc/mnttab
fd 0K 0K 0K 0% /dev/fd
swap 1.0G 152K 1.0G 1% /var/run
swap 1.1G 24M 1.0G 3% /tmp
/dev/dsk/c1t0d0s3 57G 13G 43G 24%... (4 Replies)
Discussion started by: lamoul
4 Replies
4. Red Hat
Hi, we have a root-server with 2 Disks, each 750 gb / centos 5.1
we would like to have 4 mirrored data, and 1 mirrored boot-filesystem
what do you think is the best solution, I would like to use linux lvm for a raid1-mirror, but I was told the system wont boot in case of a disk failure
... (4 Replies)
Discussion started by: funksen
4 Replies
5. Solaris
Hi,
The disks of my servers are getting full and I need to move the /export/home partition on to a new set of disks. I already have 2 mirrored disks and have added 2 more and mirrored them after creating the filesystem on them.
Do I just need to edit the /etc/vfstab and point the /export/home... (1 Reply)
Discussion started by: run_time_error
1 Replies
6. Solaris
Hi All
Hope it's okay to post on this sub-forum, couldn't find a better place
I've got a 480R running solaris 8 with veritas volume manager managing all filesystems, including an encapsulated root disk (I believe the root disk is encapsulated as one of the root mirror disks has an entry under... (1 Reply)
Discussion started by: sunnyd76
1 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I have server with 2 active disk, but disk 1 contain big part of os is falling,
how can i move everything to disk 2 and then remove the disk 1?
Thanks (4 Replies)
Discussion started by: prpkrk
4 Replies
8. Linux
Hi
We have RHEL 7.3 running from local disk and we want to move it to storage.
I am unable to find any proper procedure to do this activity. Please help. (4 Replies)
Discussion started by: powerAIX
4 Replies
9. Solaris
We have in a couple of occasions moved root disk & flashcard in netra 240 to new identical hardware instead of replacing mb in dead server. Flashcard is to preserve mac adresses and mainly hostid for license stuff. Works without doing anything other than poweron & boot.
Now we have a similar... (5 Replies)
Discussion started by: stockhes
5 Replies
LEARN ABOUT OSX
dbd::gofer::policy::base
DBD::Gofer::Policy::Base(3) User Contributed Perl Documentation DBD::Gofer::Policy::Base(3)
NAME
DBD::Gofer::Policy::Base - Base class for DBD::Gofer policies
SYNOPSIS
$dbh = DBI->connect("dbi:Gofer:transport=...;policy=...", ...)
DESCRIPTION
DBD::Gofer can be configured via a 'policy' mechanism that allows you to fine-tune the number of round-trips to the Gofer server. The
policies are grouped into classes (which may be subclassed) and referenced by the name of the class.
The DBD::Gofer::Policy::Base class is the base class for all the policy classes and describes all the individual policy items.
The Base policy is not used directly. You should use a policy class derived from it.
POLICY CLASSES
Three policy classes are supplied with DBD::Gofer:
DBD::Gofer::Policy::pedantic is most 'transparent' but slowest because it makes more round-trips to the Gofer server.
DBD::Gofer::Policy::classic is a reasonable compromise - it's the default policy.
DBD::Gofer::Policy::rush is fastest, but may require code changes in your applications.
Generally the default "classic" policy is fine. When first testing an existing application with Gofer it is a good idea to start with the
"pedantic" policy first and then switch to "classic" or a custom policy, for final testing.
POLICY ITEMS
These are temporary docs: See the source code for list of policies and their defaults.
In a future version the policies and their defaults will be defined in the pod and parsed out at load-time.
See the source code to this module for more details.
POLICY CUSTOMIZATION
XXX This area of DBD::Gofer is subject to change.
There are three ways to customize policies:
Policy classes are designed to influence the overall behaviour of DBD::Gofer with existing, unaltered programs, so they work in a
reasonably optimal way without requiring code changes. You can implement new policy classes as subclasses of existing policies.
In many cases individual policy items can be overridden on a case-by-case basis within your application code. You do this by passing a
corresponding "<go_<policy_name">> attribute into DBI methods by your application code. This let's you fine-tune the behaviour for special
cases.
The policy items are implemented as methods. In many cases the methods are passed parameters relating to the DBD::Gofer code being
executed. This means the policy can implement dynamic behaviour that varies depending on the particular circumstances, such as the
particular statement being executed.
AUTHOR
Tim Bunce, <http://www.tim.bunce.name>
LICENCE AND COPYRIGHT
Copyright (c) 2007, Tim Bunce, Ireland. All rights reserved.
This module is free software; you can redistribute it and/or modify it under the same terms as Perl itself. See perlartistic.
perl v5.16.2 2007-10-16 DBD::Gofer::Policy::Base(3)