06-10-2015
Have you checked is remote syslog machine receiving logs from that specific host ?
10 More Discussions You Might Find Interesting
1. Solaris
Hi, Can anyone pls. tell me how to access Active directory from solaris. I am looking at solution by which I can send mail notification from the logs generated by scripts, to the users on Exchange server. I am trying for a Perl-LDAP module , but don't realy know how to go for it (5 Replies)
Discussion started by: ganeshh
5 Replies
2. Solaris
Dear all
I would like to know that is there any way to find out that any client of solaris server, is fetching data from a server, in that situationng server can log what data which is flowing in the form of packet, client is fetching from the server through any application or any utility.
... (3 Replies)
Discussion started by: girish.batra
3 Replies
3. UNIX for Advanced & Expert Users
Hi All,
I have a requirement to send and email of body html with an attachment.
concatinating uuencode output to the mail body with mailx command works, but as my Email body is of HTML type i use sendmail.
my command to send HTML body is as below:
export MAILTO="recipient@domain.com"... (1 Reply)
Discussion started by: mohan_kumarcs
1 Replies
4. Solaris
Hi all,
I want to implement a Syslog Server but i'm new in this area. I donīt know how to configure it in Solaris. I should like send all the logs to a application(manipule the information, por example: do the alerts, configure it, etc...) How can I do that? or Which manual can help me? Exists... (2 Replies)
Discussion started by: yflores
2 Replies
5. Solaris
Hello everyone
I have a problem and I need your help:
I have a Solaris 10 and Solaris 8 UNIX Servers, and Linux Centos4 as email server.
I need send an email from Solaris servers preferably using Centos4 email server.
I have no mail service configured in my Solaris computers (1 Reply)
Discussion started by: aflores
1 Replies
6. Shell Programming and Scripting
i am new in AIX i am trying to write a script to take a backup for specific files on server to and check error log if backup success send email to administrator , script done except for sending mail , i try to configure sendmail on aix to use our exchange server to send emails but still get error... (0 Replies)
Discussion started by: ahmed_salah
0 Replies
7. Shell Programming and Scripting
taus-itcapp1#powermt display dev=all
Pseudo name=emcpower0a
CLARiiON ID=APM00105201788
Logical device ID=60060160B2202B001094F0E0AF5CE011
state=alive; policy=CLAROpt; priority=0; queued-IOs=0;
Owner: default=SP A, current=SP A Array failover mode: 1
... (6 Replies)
Discussion started by: orafup
6 Replies
8. Solaris
Hi folks,
I am attempting to setup a Solaris 10 syslog server to receive logs from linux machines. Here's what I did:
On the server (SunOS sun226 5.10), IP address: 192.168.212.226:
1. start syslogdby issuing $/usr/sbin/syslogd -T
On a client (SunOS sun221 5.8):
1. Configured... (1 Reply)
Discussion started by: kimurayuki
1 Replies
9. Solaris
I am trying to configure central syslog server
On hostA, in /etc/syslog.conf file,I am adding below line*.err;kern.debug;daemon.notice;mail.crit @hostB
then I am restarting syslog servicesvcadm restart /system/system-log
In hostA, I have already added hostB entry in /etc/hosts... (5 Replies)
Discussion started by: amity
5 Replies
10. AIX
Hi everyone,
I am trying to configure AIX 6.1 using syslogd to send syslog event to syslog server configured on RHEL. However, RHEL never receives the events.
I have tried to redirect the syslog event on AIX to a local file and successful. Only forwarding to remote server fails.
Firewall... (10 Replies)
Discussion started by: michael_hoang
10 Replies
LEARN ABOUT OSX
hosts.equiv
HOSTS.EQUIV(5) BSD File Formats Manual HOSTS.EQUIV(5)
NAME
hosts.equiv, .rhosts -- trusted remote hosts and host-user pairs
DESCRIPTION
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:
hostname [username]
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.
EXAMPLES
somehost
A common usage: users on somehost may login to the local host as the same user name.
somehost username
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
user name.
+@anetgroup username
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).
WARNINGS
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).
FILES
/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.
BUGS
The ruserok(3) implementation currently skips negative entries (preceded with a ``-'' sign) and does not treat them as ``short-circuit'' neg-
ative entries.
BSD
November 26, 1997 BSD