10 More Discussions You Might Find Interesting
1. AIX
I'm New to AIX / VIOS
We're doing a FC switch cutover on an ibm device, connected via SAN.
How do I tell if one path to my remote disk is lost? (aix lvm)
How do I tell when my link is down on my HBA port?
Appreciate your help, very much! (4 Replies)
Discussion started by: BG_JrAdmin
4 Replies
2. AIX
We have a 2 node oracle rac cluster one node is in frame 1 and other is in frame 2
Now,because of some hardware failure(processor card and cable) in frame 1 we will failover database services from lpar in frame 1 to lpar(oracle rac cluster node2) in frame2 and the entire replacement of hardware... (9 Replies)
Discussion started by: admin_db
9 Replies
3. AIX
Hi all,
We are migrating our SAN storage from HSV360 to 3PAR. The system runs aix 6.1 version with HACMP.
Please let me know what are requirements from OS side and how are the data copied to the new disks. (10 Replies)
Discussion started by: ElizabethPJ
10 Replies
4. AIX
Hi,
Existing several p5 server with lpar (aix5.3), also implemented with hacmp.
And now planning to buy new set of server (installing aix7.1)and SAN to replace the existing server.
My question is, how to perform data migration from old server/SAN to new server/SAN.
Suppose I install... (6 Replies)
Discussion started by: Oceanlo2013
6 Replies
5. UNIX for Advanced & Expert Users
We are about to get a new server and I need to prepare for migration to the new one. This will be my first migration so I'm sure I will be learning alot.
My current server is running CentOS 4.x and I want to move to a sever running Centos 5.x , thought it would make things easier.
The old... (1 Reply)
Discussion started by: mcraul
1 Replies
6. Shell Programming and Scripting
Hi,
I am working on migration project. thier are 50,000 scripts. As we are doing 70% of automization for changing the scripts. The remaining 30% doing manually.
After doing manual changes i have to find the wheather the change is dont or not and also clode review process.
Is there any... (2 Replies)
Discussion started by: unihp1
2 Replies
7. UNIX for Advanced & Expert Users
Hi ,
There is going to be a server migration from Solaris 8.0 to Solaris10.0.
Could anyone give me some tips and documents regarding the steps to be remembered,tips to be followed etc.
like
syntax differences
any new changes to the existing commands and tools we use
whatever the... (1 Reply)
Discussion started by: mohanpadamata
1 Replies
8. Solaris
Hi,
I need docs related to migration of Solaris8.0 to solaris10.0.
steps to be taken care from developement side..
cheers
shell scripts developer (0 Replies)
Discussion started by: mohanpadamata
0 Replies
9. UNIX for Advanced & Expert Users
Hi all,
Would appreciate advise on my situation.
Currently server A is in production. Server A takes in data from Server X, does some processing and send to server Y. We are going to develop a different system in server B, something like an enhanced version of A. Server A will be retired once... (2 Replies)
Discussion started by: new2ss
2 Replies
10. UNIX for Advanced & Expert Users
hi,
is there any tool that i can use to update my scripts (SH scripts)
form Unix to linux.
please mention any useful websites.
thanx in advance (2 Replies)
Discussion started by: omran
2 Replies
w2kusers.deny(4) Kernel Interfaces Manual w2kusers.deny(4)
NAME
w2kusers.deny - Authentication file for Windows 2000 Single Sign On.
SYNOPSIS
# Comment account_name
DESCRIPTION
The w2kusers.deny is a text file containing a list of user account names. When an account is included in this file, the Windows 2000 Sin-
gle Sign-On software verifies only the UNIX authentication for the named account.
To add user accounts to the file, use a text editor to enter the user's UNIX account name. The following syntax rules apply to the
w2kusers.deny file: Only one user name can be entered on a line. The user name must exactly match a user name in the UNIX /etc/passwd
file. Comment lines begin with a pound sign (#).
EXAMPLES
The following example shows a typical w2kusers.deny file: # The following file lists account names that are not allowed to use # the Win-
dows 2000 authentication information when it is enabled. # Account names must match exactly the user account name in the # /etc/passwd
file. # # Syntax: account_1 # . # . # . # account_n # root nobody nobodyV daemon bin uucp
uucpa auth cron lp tcb adm ris wnn pop imap Peter Dave Beth Martha
FILES
Location of the file.
RELATED INFORMATION
Commands: ldapcd(8), lw2ksetup(8)
Files: etc/w2kusers.deny(4)
Windows 2000 Single Sign-OnInstallation and Administration Guide.
delim off delim off
w2kusers.deny(4)