Sponsored Content
Full Discussion: Policy Manager
Top Forums UNIX for Dummies Questions & Answers Policy Manager Post 53651 by mikeinmi on Wednesday 21st of July 2004 10:52:09 AM
Old 07-21-2004
Policy Manager

I have searched all over the SCO website and can't seem to find an answer to this error message. Has anyone seen the following error, and if so what steps do I need to take to fix it? I don't really want to reload the entire OS if I don't have to.

LOGIN: ERROR- Failed to initialize policy manager. (IFOR_PM_FATAL)
The status from the policy manager daemon (PMD - /etc/ifor_pmd) indicates that a serious error condition has occurred. Login is allowed, but the system administrator is strongly advised to consult the SCO online Support Solutions Library (SSL) for assistance; if the SSL is inaccessible, please contact your SCO Support representative.

Thanks in advance
Smilie
 

8 More Discussions You Might Find Interesting

1. Solaris

RAID manager or veritas volume manager

Can somebody kindly help me to determine which one i should choose to better manipulate OS volume. RAID manager or veritas volume manager? Any critical differences between those two? Thanks in advance. (5 Replies)
Discussion started by: beginningDBA
5 Replies

2. Solaris

Password policy problem ??

Hi Solaris's expert I need to change user password on Solaris10 2 servers. With the same password I can change it just only one. Try to check everything but not found difference?? password pattern: abcdeFgh9Jk server1 check all characters but server2 check only first 8 characters.Why??... (10 Replies)
Discussion started by: arm_naja
10 Replies

3. Red Hat

ipsec policy not working

Hi, I am trying to set a policy between 2 machines for all the ports except for 22 i.e. for tcp - basically I want to bypass ssh. But my policy doesn't seem to work. Here are the entries spdadd 1.2.3.4 4.3.2.1 any -P out prio 100 ipsec esp/transport//require ah/transport//require; spdadd... (0 Replies)
Discussion started by: ahamed101
0 Replies

4. Solaris

LACP Policy - Which is best?

Hello, I have these S10 boxes with LACP using the L4 policy. Does the L4 policy create a lot more overhead as opposed to using the L2? I'm noticing that my traffic does not seem to be very well load balanced accross the NIC's, and I am wondering if the policy I'm using has anything else to do... (1 Reply)
Discussion started by: BG_JrAdmin
1 Replies

5. Ubuntu

User and Password Policy

Hi linux expert, i would like to create a script for listing all user with there password policy. It should be in the following format: Last password change : Sep 19, 2011 Password expires : never Password inactive : never Account... (2 Replies)
Discussion started by: yprudent
2 Replies

6. Cybersecurity

Need patch policy help

I'm working on developing a patch policy for a mid-size and quickly growing company. Patches have been at the bottom of the totem pole for years. I possess the ability and care enough to straighten it out. However I'd like some others input on the best way to handle the patch policy. From when... (1 Reply)
Discussion started by: jlouki01
1 Replies

7. AIX

Password Policy

I need help. I have set a password policy. But I want to dis allow setting user name as password. My policy is as below... min length =8 min diff=2 min alpha=2 max repeats=2 dictionary= /usr/share/dict/words Still user can set his username as password (i.e. Jackie1234). Code tags for... (11 Replies)
Discussion started by: powerAIX
11 Replies

8. Solaris

Help to create a regex for this policy

Help with creating regex in tripwire : the rule is " The idea of it looks to ensure that just ‘share' isn't used in dfstab, must be /usr/sbin/share" Perform the following to determine if the system is configured as recommended: # grep -v '^#' /etc/dfs/dfstab | grep 'share' | grep -v... (1 Reply)
Discussion started by: bathija12
1 Replies
COMPAT_IBCS2(8) 					    BSD System Manager's Manual 					   COMPAT_IBCS2(8)

NAME
compat_ibcs2 -- setup procedure for running iBCS2 binaries DESCRIPTION
NetBSD supports running Intel Binary Compatibility Standard 2 (iBCS2) binaries. This only applies to i386 systems for now. Binaries are supported from SCO UNIX and other systems derived from AT&T System V Release 3 UNIX. iBCS2 support is only well tested using SCO binaries. XENIX binaries are also supported although not as well tested. SVR4 binaries are supported by the COMPAT_SVR4 option. iBCS2 supports COFF, ELF, and x.out (XENIX) binary formats. Binaries from SCO OpenServer (version 5.x) are the only ELF binaries that have been tested. Most programs should work, but not ones that use or depend on: kernel internal data structures STREAMS drivers (other than TCP/IP sockets) local X displays (uses a STREAMS pipe) virtual 8086 mode The iBCS2 compatibility feature is active for kernels compiled with the COMPAT_IBCS2 option enabled. If support for iBCS2 ELF executables is desired, the EXEC_ELF32 option should be enabled in addition to COMPAT_IBCS2. Many COFF-format programs and most ELF-format programs are dynamically linked. This means that you will also need the shared libraries that the program depends on. Also, you will need to create a ``shadow root'' directory for iBCS2 binaries on your NetBSD system. This directory is named /emul/ibcs2. Any file operations done by iBCS2 programs run under NetBSD will look in this directory first. So, if an iBCS2 pro- gram opens, for example, /etc/passwd, NetBSD will first try to open /emul/ibcs2/etc/passwd, and if that does not exist open the 'real' /etc/passwd file. It is recommended that you install iBCS2 packages that include configuration files, etc. under /emul/ibcs2, to avoid nam- ing conflicts with possible NetBSD counterparts. Shared libraries should also be installed in the shadow tree. Generally, you will need to look for the shared libraries that iBCS2 binaries depend on only the first few times that you install an iBCS2 program on your NetBSD system. After a while, you will have a sufficient set of iBCS2 shared libraries on your system to be able to run newly imported iBCS2 binaries without any extra work. Setting up shared libraries How to get to know which shared libraries iBCS2 binaries need, and where to get them? Depending on the file type of the executable, there are different possibilities (when following these instructions: you will need to be root on your NetBSD system to do the necessary installation steps). COFF binaries You can simply copy all of the available shared libraries since they are fairly small in size. The COFF shared libraries are typically found in /shlib and can be obtained from the following sources: SCO UNIX version 3.x (aka ODT) SCO UNIX version 5.x (aka OpenServer) SCO UnixWare Many versions of SVR4.2/x86 After copying the shared libraries, you should have at least the following files on your system: /emul/ibcs2/shlib/libc_s /emul/ibcs2/shlib/libnsl_s /emul/ibcs2/shlib/protlib_s ELF binaries You can simply copy all of the available shared libraries from the source system or distribution or use ldd(1) to determine the libraries required by a specific binary. After copying the shared libraries, you should have at least the following files on your system: /emul/ibcs2/usr/lib/libc.so.1 /emul/ibcs2/usr/lib/libcrypt.so /emul/ibcs2/usr/lib/libndbm.so /emul/ibcs2/usr/lib/libsocket.so.1 If you don't have access to a SCO system, you will need to get the extra files you need from a SCO distribution. As of January 1998, SCO sells a copy of SCO OpenServer (iBCS2) and/or SCO UnixWare (SVR4) for personal/non-commercial use for only the cost of shipping (about $20US). The distribution comes on an ISO9660-format CDROM which can be mounted and used to copy the necessary files. Run the following script to copy the basic set of files from a SCO distribution directory mounted somewhere locally: /usr/share/examples/emul/ibcs2/ibcs2-setup [directory] You should now be set up for SCO binaries which only need standard shared libs. BUGS
The information about SCO distributions may become outdated. Attempting to a use a nameserver on the local host does not currently work due to an absurd shortcut taken by the iBCS2 network code (remem- ber that there are no kernel sockets). 16/32/64 bit offsets may not be handled correctly in all cases. BSD
February 8, 1998 BSD
All times are GMT -4. The time now is 09:00 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy