[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[LCFC] templates://uptimed/{uprecords-cgi.templates,uptimed.templates}



(speeding up the process as, nearly always, the only review I get
after mine is Justin's.....and I took all of his proposed changes
without even thinking...as most often! Given that the release is now
approaching, I want to move to the translation step as soon as
possible)

This is the last call for comments for the review of debconf
templates for uptimed.

The reviewed templates will be sent on Thursday, May 31, 2012 to this bug report
and a mail will be sent to this list with "[BTS]" as a subject tag.


-- 


Template: uprecords-cgi/layout
Type: select
__Choices: pre, list, table
Default: pre
_Description: Format used by uprecords.cgi:
 Three different layouts are available for use by the uprecords CGI script.
 Which method you use is a matter of personal preference.
 .
  * pre: Encloses everything in <pre>...</pre>
  * list: Makes a list, using <ol>...</ol>
  * table: Creates an HTML table.

Template: uprecords-cgi/maxentries
Type: string
Default: 10
_Description: Number of records shown by uprecords.cgi:
 While uptimed may keep a large number of uptime records, not all of them
 are interesting to the outside world. Thus, you can limit the number of
 records that will be shown here.

Template: uprecords-cgi/install_note
Type: note
_Description: uprecords.cgi has been installed into the web tree
 You have installed the uprecords-cgi package. That means that a new CGI
 script has been installed, which is now visible to the outside world as
 http://${hostname}/cgi-bin/uprecords.cgi (if you didn't modify your
 web server configuration to have CGI scripts in a different place).
 .
 In the default web server configuration, CGI scripts are accessible from
 anywhere in the world. If you do not want this, you should set up access
 restrictions... but why wouldn't you want to show off your uptimes?
 .
 You may also want to modify the HTML header and footer files in
 /etc/uprecords-cgi (or have your webmaster do so).
Template: uptimed/interval
Type: string
Default: 600
_Description: Delay between database updates (seconds):
 Uptimed will update its database regularly so that the uptime
 doesn't get lost in case of a system crash. You can set how frequently
 this will happen (use higher values if you want to avoid disk activity,
 for instance on a laptop).

Template: uptimed/maxrecords
Type: string
Default: 50
_Description: Number of records that should be kept:
 On systems that reboot frequently, you will get a
 fairly large list of uptime records pretty soon. To avoid this, uptimed
 will only keep the n highest uptimes. You may want to limit this to a
 lower value if you want to get emails each time a record is broken or
 if you reboot your machine often.

Template: uptimed/mail/do_mail
Type: select
__Choices: Never, Record, Milestone, Both
Default: Never
_Description: Send mails if a milestone or record is reached:
 Uptimed can be configured to send a mail each time a record is broken or a
 "milestone" is reached. You can choose whether you:
 .
  * never want to receive these mails;
  * want to be notified only when a record is broken;
  * would like to know about milestones;
  * are interested in both.

Template: uptimed/mail/address
Type: string
Default: root
_Description: Uptimed email recipient:
 Since you have chosen to be sent emails, you should specify where to send
 these mails.

Template: uptimed/mail/milestones_info
Type: note
_Description: Milestone configuration must be done manually
 The milestones must
 be configured manually in /etc/uptimed.conf. Since you have chosen to
 receive emails for milestones you probably want to modify that file.
Source: uptimed
Section: utils
Priority: extra
Maintainer: Thibaut VARENE <varenet@debian.org>
Build-Depends: debhelper (>= 8.1.0~), dpkg-dev (>> 1.16.1~), automake, libtool, po-debconf
Standards-Version: 3.9.3
Homepage: http://podgorny.cz/uptimed

Package: uptimed
Architecture: any
Pre-Depends: ${misc:Pre-Depends}
Depends: ${misc:Depends}, ${shlibs:Depends}, lsb-base
Description: utility to track high uptimes - daemon
 The uptime daemon tracks a system's highest uptimes via boot IDs,
 using the system boot time to keep sessions apart from each other.
 It features a console program to display statistics, and can
 send mail if a milestone or a new record is reached.

Package: libuptimed0
Section: libs
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, perl
Conflicts: libuptimed
Replaces: libuptimed
Description: utility to track high uptimes - library
 The uptime daemon tracks a system's highest uptimes via boot IDs,
 using the system boot time to keep sessions apart from each other.
 It features a console program to display statistics, and can
 send mail if a milestone or a new record is reached.
 .
 This package provides the library package for uptimed.

Package: libuptimed-dev
Section: libdevel
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}, perl, libuptimed0 (= ${binary:Version})
Replaces: libuptimed
Description: utility to track high uptimes - development files
 The uptime daemon tracks a system's highest uptimes via boot IDs,
 using the system boot time to keep sessions apart from each other.
 It features a console program to display statistics, and can
 send mail if a milestone or a new record is reached.
 .
 This is the development files package for uptimed.

Package: uprecords-cgi
Architecture: all
Depends: uptimed (>= ${source:Version}), ${misc:Depends},
Recommends: apache | httpd
Description: utility to track high uptimes - CGI script
 The uptime daemon tracks a system's highest uptimes via boot IDs,
 using the system boot time to keep sessions apart from each other.
 It features a console program to display statistics, and can
 send mail if a milestone or a new record is reached.
 .
 This package provides a CGI script that produces an HTML report
 containing all the highest uptimes from the uptimed database.

Attachment: signature.asc
Description: Digital signature


Reply to: