I want to modify the CPU of my VM but when i am going to modify it , it showing the below error :
hpvmmodify: ERROR (host): The vswitch 'vmsw4' does not exist.
HPVM guest testhost configuration problems:
Warning 1 on item vmsw4: Vswitch 'vmsw4' does not exist.
These... (0 Replies)
i am trying to open HTTP by curl command.
i am tryng to do that from command or script BASH.
also iptables is off
it doesnt work i am getting an error:
curl: (7) coudn't connect to host
the scipt is:
curl http://www.cnn.com (1 Reply)
A linux box is supposed to emailing the results of backups to the windows exchange server, but nothing arrives. it never has, as the muppet who set up the Windows domain knew nothing about linux. I know only slightly more than that...
pretty sure sendmail is the daemon running to handle mail. it... (0 Replies)
Whenever i login into one of my solaris machine i get below message,
Usage: basename ]
if: Expression syntax
Profile or environment of my user is not properly getting loaded.
Can somebody help why this is coming and solution to it? (1 Reply)
Hello World ~
HW : SUN Fire V240
OS : Solaris 8
Error message prompts 'rmclomv ... SC login failure ...' on terminal.
Error Message prompts continually 'SC Login Failure for user Please login:' on Single Mode(init S)
The System is in normal operation, though
In case of rain, Can... (1 Reply)
I have sendmail setup to relay through my external ISP. Everything was working fine until I started getting the error message (below). I don't what I did to cause this? I have read a number of related posts and it appears that I might need to configure the sending address of my server to appear... (0 Replies)
Our application has to send Fax to our cutomer Fax number .
I am using lpr -P faxser:test-fax <<dos format file>>
I tested on our network Fax numbers . Its working fine.
But when i try to send outside our network , its not sending
all files are sitting in... (1 Reply)
Error: Could not read object configuration data!
Here are some things you should check in order to resolve this error:
1. Verify configuration options using the -v command-line option to check for errors.
2. Check the Nagios log file for messages relating to startup or... (0 Replies)
HOSTS.EQUIV(5) BSD File Formats Manual HOSTS.EQUIV(5)NAME
hosts.equiv, .rhosts -- trusted remote hosts and host-user pairs
The hosts.equiv and .rhosts files list hosts and users which are ``trusted'' by the local host when a connection is made via rlogind(8),
rshd(8), or any other server that uses ruserok(3). This mechanism bypasses password checks, and is required for access via rsh(1).
Each line of these files has the format:
The hostname may be specified as a host name (typically a fully qualified host name in a DNS environment) or address, +@netgroup (from which
only the host names are checked), or a ``+'' wildcard (allow all hosts).
The username, if specified, may be given as a user name on the remote host, +@netgroup (from which only the user names are checked), or a
``+'' wildcard (allow all remote users).
If a username is specified, only that user from the specified host may login to the local machine. If a username is not specified, any user
may login with the same user name.
A common usage: users on somehost may login to the local host as the same user name.
The user username on somehost may login to the local host. If specified in /etc/hosts.equiv, the user may login with only the same
The user username may login to the local host from any machine listed in the netgroup anetgroup.
Two severe security hazards. In the first case, allows a user on any machine to login to the local host as the same user name. In the
second case, allows any user on any machine to login to the local host (as any user, if in /etc/hosts.equiv).
The username checks provided by this mechanism are not secure, as the remote user name is received by the server unchecked for validity.
Therefore this mechanism should only be used in an environment where all hosts are completely trusted.
A numeric host address instead of a host name can help security considerations somewhat; the address is then used directly by iruserok(3).
When a username (or netgroup, or +) is specified in /etc/hosts.equiv, that user (or group of users, or all users, respectively) may login to
the local host as any local user. Usernames in /etc/hosts.equiv should therefore be used with extreme caution, or not at all.
A .rhosts file must be owned by the user whose home directory it resides in, and must be writable only by that user.
Logins as root only check root's .rhosts file; the /etc/hosts.equiv file is not checked for security. Access permitted through root's
.rhosts file is typically only for rsh(1), as root must still login on the console for an interactive login such as rlogin(1).
/etc/hosts.equiv Global trusted host-user pairs list
~/.rhosts Per-user trusted host-user pairs list
SEE ALSO rcp(1), rlogin(1), rsh(1), rcmd(3), ruserok(3), netgroup(5)HISTORY
The .rhosts file format appeared in 4.2BSD.
The ruserok(3) implementation currently skips negative entries (preceded with a ``-'' sign) and does not treat them as ``short-circuit'' neg-
BSD November 26, 1997 BSD