Sponsored Content
Operating Systems Solaris Solaris 9 login Screen not loading Post 302213028 by deaconf19 on Wednesday 9th of July 2008 04:04:24 AM
Old 07-09-2008
yes ftp telnet works fine. DNS is working with the system as well. currently i am telnet into the system.

. run-level 3

yes that file is in there. It has perms of 744 with root:sys
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Login screen change

If I want to change a Solaris 8 login screen to add a Company name what do I need to do ? Current login prompt SunOS 5.8 login: ... (2 Replies)
Discussion started by: miredale
2 Replies

2. Solaris

Pre-Login Screen Resolution

I'm trying to configure the resolution that the pre-login screen is set at, I have looked on the net and all I can find is people telling me to edit the 'm46config' file. I cant find this file anywhere in any directory. I'm running Solaris 10 - any ideas how I can alter the resolution? :confused: (1 Reply)
Discussion started by: Dredz
1 Replies

3. AIX

I won't get the login screen

Hi to all, I am new to AIX.I faced some desktop problem from past few days. when i login to that machine, i won't get the login screen. Why it's happening lot of times, i don't know. I get only blank screen. Could any knows please help me. It's very urget to me. Thanks &... (2 Replies)
Discussion started by: balarajum
2 Replies

4. UNIX for Advanced & Expert Users

openwebmail custom login screen.

I'm running openwebmail on a centos 4.x machine. I want to make my own custom login screen. I would go to the openwebmail mailing list and ask but it seems to be down for the moment. Anyway anybody ever try this? I seen that there are template files and that the login screen is somehow created... (0 Replies)
Discussion started by: mcraul
0 Replies

5. AIX

Pre Login Screen

Is it possible to have the user press enter to acknowledge a message before typing in his or her login name and password? I need to add this functionality to the CDE login, ssh, and ibm 3151 console on AIX 5.3. (0 Replies)
Discussion started by: prichard
0 Replies

6. Solaris

Solaris Login Screen Not Loading

I (think I) successfully installed Solaris 10 5/09 on the IDE hard drive of my computer using the 5 installation CDs I downloaded from the Sun website. But now when I boot from the IDE hard drive I think it boots successfully but It asks me for the root password or Ctrl+D to abort. When I give it... (5 Replies)
Discussion started by: Bradj47
5 Replies

7. Red Hat

Screen resolution before and after login

system: Fedora14 on vmware the login screen resolution is 1024*768, but after login the resolution is 800*600. I want to set the login screen resolution as 800*600 too. How to do this? thanks! (2 Replies)
Discussion started by: vistastar
2 Replies

8. Shell Programming and Scripting

OpenSuse Login Screen

I'm Not really sure if this is the best place to ask this question but logic tells me it is :P I'm Trying to change the login screen for OpenSuse the green Screen for something a little bit more of my liking, and I think the only way to do it perfect and right is through the command Line, do not... (1 Reply)
Discussion started by: JuankyKong
1 Replies

9. Solaris

Login Screen in Solaris 11

I have a requirement to add a warning banner to the Solaris 11 login screen. Adding the banner was pretty easy in Solaris 10 by changing *Dtlogin. Does anyone know how to make the change in Solaris !!? (3 Replies)
Discussion started by: goose25
3 Replies

10. Red Hat

Login screen reappears..!!

Hi all, My login screen reappears if i give a correct password for a user and give login.. I am doing Linux BMR process for CentOs .. I first backup the ' / ' folder with partition details and then restore it using a live cd. By doing so i got succeeded in restoring a machine.. But while... (0 Replies)
Discussion started by: selvarajvs
0 Replies
ipsec_policy(1M)														  ipsec_policy(1M)

NAME
ipsec_policy - HP-UX IPSec policy tester SYNOPSIS
src_ip_addr] dst_ip_addr] src_port] dst_port] DESCRIPTION
is a utility program that allows the HP-UX IPSec Administrator to query the active policy database to determine which host IPsec Policy will be used for an IP packet based on a packet descriptor, or 5-tuple, and the direction. The packet descriptor consists of a source IP address, source port number, destination IP address, destination port number, and network protocol. If the host policy uses dynamic key Security Associations, also displays the authentication record and IKE policy selected. If the authentication record contains two values for the IKE (KMP) version, uses the first value and selects the IKE policy according to this value. If the host policy uses a tunnel pol- icy, also displays the tunnel policy used. requires the optional HP-UX IPSec software. You must have superuser capabilities to run the utility. Command-Line Arguments recognizes the following command-line options and arguments: Specifies the source IP address (src_ip_addr) of the packet. If the direction is out, this is the local IP address. If the direction is in, this is the remote IP address. Acceptable values: An IPv4 address in dotted-decimal notation or an IPv6 address in colon-hexadecimal notation. Default: If you omit the source address and destination address uses the wildcard IPv4 address If you omit the source address but specify the destination address, uses the wildcard IPv4 address or wildcard IPv6 address according to the type of IP address you specify for the destination address. Specifies the source port number (src_port) of the packet. If the direction is out, this is the local port number. If the direction is in, this is the remote port number. Range: An unsigned integer in the range 1 - 65535. Default: Any port number(0). If you are making a query for an outbound client-server application where the source port number can be any user-space port, specify a "dummy" user-space port number for the source port, such as 65535. Specifies the destination IP address (dst_ip_addr) of the packet. If the direction is out, this is the remote IP address. If the direction is in, this is the local IP address. Acceptable values: An IPv4 address in dotted-decimal notation or an IPv6 address in colon-hexadecimal notation. Default: If you omit the source address and destination address uses the wildcard IPv4 address If you omit the destination address but specify the source address, uses the wildcard IPv4 address or wildcard IPv6 address according to the type of IP address you specify for the source address. Specifies the destination port number (dst_port) of the packet. If the direction is out, this is the remote port number. If the direction is in, this is the local port number. Range: An unsigned integer in the range 1 - 65535. Default: If omitted, any port number is assumed. If you are making a query for an inbound client-server application where the client port number can be any user-space port, specify a "dummy" user-space port number for the destination (server) port such as 65535. Specifies the network_protocol of the packet. Acceptable values: (Mobile IPv6 Mobility Header), or Default: Any network protocol(0). Specifies the direction for the packet specification. Acceptable values: or Default: RETURN VALUE
Upon successful completion, returns 0; otherwise it returns 1. ERRORS
fails if any of the following conditions is encountered: o Command used incorrectly - Usage message is returned. o HP-UX IPSec subsystem is not running - returns the following message: EXAMPLES
IPv4 Example On system A you want to determine which host IPsec policy will be used for outbound telnet traffic to system B or when local users telnet to system B. Since the telnet clients on system A will use any unused user-space TCP port and the telnet daemons on system B will use TCP port 23, you could use the following command: On system A you want to determine which host IPsec policy will be used for inbound telnet traffic from system B or when users on system B telnet to the local system. Since the local telnet daemons will use TCP port 23 and clients on system B will use any unused user-space TCP port, you could use the following command: IPv6 example On system A you want to determine which host IPsec policy will be used for outbound telnet traffic to system B or when local users telnet to system B. Since the telnet clients on system A will use any unused user-space TCP port and the telnet daemons on system B will use TCP port 23, you could use the following command: On system A you want to determine which host IPsec policy will be used for inbound telnet traffic from system B or when users on system B telnet to the local system. Since the local telnet daemons will use TCP port 23 and clients on system B will use any unused user-space TCP port, you could use the following command: WARNINGS
requires the optional HP-UX IPSec software. AUTHOR
was developed by HP. SEE ALSO
ipsec_admin(1M), ipsec_config(1M), ipsec_config_add(1M), ipsec_config_batch(1M), ipsec_config_delete(1M), ipsec_config_export(1M), ipsec_config_show(1M), ipsec_migrate(1M), ipsec_report(1M). HP-UX IPSec Software Required ipsec_policy(1M)
All times are GMT -4. The time now is 06:45 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy