Sponsored Content
Full Discussion: syslog
Operating Systems Solaris syslog Post 302085984 by System Shock on Monday 21st of August 2006 02:18:58 PM
Old 08-21-2006
Bounce the daemon.
 

2 More Discussions You Might Find Interesting

1. Solaris

Which are the available entries to forward syslog in syslog.conf?

Hi Community Which are the available entries to forward syslog in syslog.conf i have put *.err;kern.debug;daemon.notice;mail.crit;user.alert;user.emerg;kern.notice;auth.notice;kern.warning @172.16.200.50 and it's not going through.giving error message like below: syslogd:... (2 Replies)
Discussion started by: bentech4u
2 Replies

2. AIX

Cannot send syslog event from AIX 6.1 to RHEL Syslog server

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
lockd(8c)																 lockd(8c)

Name
       lockd - network lock daemon

Syntax
       /usr/etc/lockd [ -t timeout ] [ -g graceperiod ]

Description
       The  daemon processes lock requests that are either sent locally by the kernel or remotely by another lock daemon.  The NFS locking service
       makes this advisory locking support possible by using the system call and the subroutine.  The daemon forwards  lock  requests  for  remote
       data  to  the  server  site's lock daemon.  The daemon then requests the status monitor daemon, for monitor service.  The reply to the lock
       request is not sent to the kernel until the status daemon and the server site's lock daemon have replied.

       If either the status monitor or server site's lock daemon is unavailable, the reply to a lock request for remote data is delayed until  all
       daemons become available.

       When  a server recovers, it waits for a grace period for all client site daemons to submit reclaim requests.  Client site daemons are noti-
       fied by of the server recovery and promptly resubmit previously granted lock requests.  If a client site's daemon fails	to  secure  previ-
       ously  granted  locks  at  the server site, the daemon sends the signal SIGLOST to all the processes that were previously holding locks and
       cannot reclaim them.

Options
       -t timeout      The daemon uses timeout (in seconds) as the interval instead of the default value  of  15  seconds  to  retransmit  a  lock
		       request to the remote server.

       -g graceperiod  The daemon uses graceperiod (in seconds) as the grace period duration instead of the default value of 45 seconds.

See Also
       fcntl(2), lockf(3), signal(3), statd(8c)

																	 lockd(8c)
All times are GMT -4. The time now is 02:19 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy