Bartlby 1.3.1 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Bartlby 1.3.1 (Default branch)
# 1  
Old 04-17-2008
Bartlby 1.3.1 (Default branch)

ImageBartlby is a network and system monitor,completely written in C, to provide a scalableframework with the ability to monitor networks ofvarious sizes. It consists of a core daemon,several plugins, and a Web GUI (PHP extension).The core daemon checks (over active/passive TCP)services/hosts and notifies users in case ofcritical service conditions (mail, SMS, ICQ, andcustom triggers are supported). Bartlby providesan open plugin interface to give everyadministrator an easy to use option to extend theplugin base, and a fully customizable GUI (writtenin PHP using a C extension). Nearby everything can be controlled via an XML interface.License: GNU General Public License (GPL)Changes:
This release has some major code houskeeping and a ton of fixes. A few key features have been added like the re-notification and the new role of the standby worker. A new extension allows your operations center to manage the whole on-call schedule and create reports of activities over the weekend (OcL).Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
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)