Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #12646
| Newsgroups | comp.os.linux.misc, comp.sys.raspberry-pi |
|---|---|
| From | spam-no-spam@Freeola.net.invalid (Windmill) |
| Subject | Re: HOW2 capture time of power-failure? |
| Organization | From time to time |
| Message-ID | <nEMxAo.4tu@way.freeola.net> (permalink) |
| References | <m2jbi3$geq$1@dont-email.me> <m2jhnq$7b6$1@dont-email.me> <nEInoz.37p@way.freeola.net> <m3e6do$jh$1@dont-email.me> |
| Date | 2014-11-06 20:37 +0000 |
Cross-posted to 2 groups.
William Unruh <unruh@invalid.ca> writes:
>On 2014-11-04, Windmill <spam-no-spam@Freeola.net.invalid> wrote:
>> William Unruh <unruh@invalid.ca> writes:
>>
>>>On 2014-10-26, not.socialnetwork@gmail.com <not.socialnetwork@gmail.com> wrote:
>>>> I need to capture the time-after-a-sound-file-starts-playing
>>>> until the power is cut, with a resolution of 30 secs., over a
>>>> period of 30 minutes.
>>
>>>Power is cut? What does that mean?
>>>>
>>>> While `ogg123 SoundFie.ogg` is playing, could the play-time
>>>> be updated every 30 secs? How?
>>>How are you playing it, what is the player software?
>>
>>>Usually you can get a pretty good idea of the time of a power cut by
>>>looking at /var/log/messages and seeind when the last message was written before the
>>>cut.
>>
>> Or if 1 minute intervals are acceptable you can edit the appropriate
>> place so that syslogd runs with option '-m 1' and then edit
>> /etc/syslogd.conf so that it includes the line
>I have rsyslog but it has no -m option. Also the mark log facility
>I have not seen before. When was it introduced into syslog? (there is no
>explanation of what it is in the man page.)
>I can also not find any explanation of the mark facility in syslogd
>docs.
I can't be sure where I got that version of syslogd; might have been a
Gnu or BSD version although a lot came from Debian. It was a long time
ago!
It's also possible that '-m' was a feature that had to be selected at
compile time (in those days you often had to compile things yourself).
But Google has references to '-m ', some as recent as 2013.
Maybe you need to use a syslogd with -r for remote logging, instead of
rsyslogd, to get the -m option?
Ah - after writing this I see that someone with up-to-date knowledge
has provided you with more relevant information, so the rest of this is
just of historical interest.
Saying "man syslogd" on that old (ancient!) system shows me this (note
it says sysklogd not syslogd; I've a vague recollection that there were
several flavours although this one's executable is in /bin as syslogd) :-
SYSKLOGD(8) Linux System Administration SYSKLOGD(8)
NAME
sysklogd - Linux system logging utilities.
SYNOPSIS
syslogd [ -d ] [ -f config file ] [ -h ] [ -l hostlist ] [
-m interval ] [ -n ] [ -p socket ] [ -r ] [ -s domainlist
] [ -v ]
DESCRIPTION
Sysklogd provides two system utilities which provide sup-
port for system logging and kernel message trapping. Sup-
port of both internet and unix domain sockets enables this
utility package to support both local and remote logging.
System logging is provided by a version of syslogd(8)
derived from the stock BSD sources. Support for kernel
logging is provided by the klogd(8) utility which allows
kernel logging to be conducted in either a standalone
fashion or as a client of syslogd.
Syslogd provides a kind of logging that many modern pro-
grams use. Every logged message contains at least a time
and a hostname field, normally a program name field, too,
but that depends on how trusty the logging program is.
While the syslogd sources have been heavily modified a
couple of notes are in order. First of all there has been
a systematic attempt to insure that syslogd follows its
default, standard BSD behavior. The second important con-
cept to note is that this version of syslogd interacts
transparently with the version of syslog found in the
standard libraries. If a binary linked to the standard
shared libraries fails to function correctly we would like
an example of the anomalous behavior.
The main configuration file /etc/syslog.conf or an alter-
native file, given with the -f option, is read at startup.
Any lines that begin with the hash mark (``#'') and empty
lines are ignored. If an error occurs during parsing the
whole line is ignored.
OPTIONS
-d Turns on debug mode. Using this the daemon will not
proceed a fork(2) to set itself in the background,
but opposite to that stay in the foreground and
write much debug information on the current tty.
See the DEBUGGING section for more information.
-f config file
Specify an alternative configuration file instead
of /etc/syslog.conf, which is the default.
Version 1.3 13 December 1995 1
SYSKLOGD(8) Linux System Administration SYSKLOGD(8)
-h By default syslogd will not forward messages it
receives from remote hosts. Specifying this switch
on the command line will cause the log daemon to
forward any remote messages it receives to forward-
ing hosts which have been defined.
-l hostlist
Specify a hostname that should be logged only with
its simple hostname and not the fqdn. Multiple
hosts may be specified using the colon (``:'') sep-
arator.
-m interval
The syslogd logs a mark timestamp regularly. The
default interval between two -- MARK -- lines is 20
minutes. This can be changed with this option.
-n Avoid auto-backgrounding. This is needed especially
if the syslogd
--
Windmill, TiltNot@NoneHome.com Use t m i l l
J.R.R. Tolkien:- @ S c o t s h o m e . c o m
All that is gold does not glister / Not all who wander are lost
Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
HOW2 capture time of power-failure? not.socialnetwork@gmail.com - 2014-10-26 17:38 +0000
Re: HOW2 capture time of power-failure? Ian Malcolm <See.My.Sig.for.email@totally.invalid> - 2014-10-26 18:26 +0000
Re: HOW2 capture time of power-failure? not.socialnetwork@gmail.com - 2014-10-27 18:10 +0000
Re: HOW2 capture time of power-failure? Gordon Henderson <gordon+usenet@drogon.net> - 2014-10-27 18:29 +0000
Re: HOW2 capture time of power-failure? not.socialnetwork@gmail.com - 2014-10-28 21:26 +0000
Re: HOW2 capture time of power-failure? William Unruh <unruh@invalid.ca> - 2014-10-28 04:56 +0000
Re: HOW2 capture time of power-failure? Dom <domafp@blueyonder.co.uk> - 2014-10-28 06:29 +0000
Re: HOW2 capture time of power-failure? William Unruh <unruh@invalid.ca> - 2014-10-28 06:41 +0000
Re: HOW2 capture time of power-failure? not.socialnetwork@gmail.com - 2014-10-29 00:12 +0000
Re: HOW2 capture time of power-failure? William Unruh <unruh@invalid.ca> - 2014-10-26 19:23 +0000
Re: HOW2 capture time of power-failure? spam-no-spam@Freeola.net.invalid (Windmill) - 2014-11-04 13:19 +0000
Re: HOW2 capture time of power-failure? William Unruh <unruh@invalid.ca> - 2014-11-05 21:56 +0000
Re: HOW2 capture time of power-failure? Joe Beanfish <joebeanfish@nospam.duh> - 2014-11-06 14:12 +0000
Re: HOW2 capture time of power-failure? nba@users.sourceforge.net (Niels Baggesen) - 2014-11-06 16:15 +0100
Re: HOW2 capture time of power-failure? William Unruh <unruh@invalid.ca> - 2014-11-06 16:00 +0000
Re: HOW2 capture time of power-failure? spam-no-spam@Freeola.net.invalid (Windmill) - 2014-11-06 20:37 +0000
Re: HOW2 capture time of power-failure? Joe Beanfish <joebeanfish@nospam.duh> - 2014-11-06 14:13 +0000
Re: HOW2 capture time of power-failure? andrew@cucumber.demon.co.uk (Andrew Gabriel) - 2014-10-26 20:28 +0000
Re: HOW2 capture time of power-failure? Joe Beanfish <joebeanfish@nospam.duh> - 2014-10-27 13:17 +0000
Re: HOW2 capture time of power-failure? Jean-David Beyer <jeandavid8@verizon.net> - 2014-10-28 13:43 -0400
Re: HOW2 capture time of power-failure? Ant <ant@zimage.comANT> - 2014-10-29 08:18 -0700
Re: HOW2 capture time of power-failure? Joe Beanfish <joebeanfish@nospam.duh> - 2014-10-29 13:28 +0000
Re: HOW2 capture time of power-failure? not.socialnetwork@gmail.com - 2014-10-30 08:32 +0000
background processes (was HOW2 capture time of power-failure?) Joe Beanfish <joebeanfish@nospam.duh> - 2014-10-30 13:16 +0000
Re: background processes (was HOW2 capture time of power-failure?) not.socialnetwork@gmail.com - 2014-11-03 03:25 +0000
Re: background processes (was HOW2 capture time of power-failure?) "David W. Hodgins" <dwhodgins@nomail.afraid.org> - 2014-11-02 23:34 -0500
Re: background processes (was HOW2 capture time of power-failure?) William Unruh <unruh@invalid.ca> - 2014-11-03 08:25 +0000
Re: background processes (was HOW2 capture time of power-failure?) Martin Gregorie <martin@address-in-sig.invalid> - 2014-11-03 12:56 +0000
Re: background processes (was HOW2 capture time of power-failure?) not.socialnetwork@gmail.com - 2014-11-06 19:19 +0000
Re: background processes (was HOW2 capture time of power-failure?) Martin Gregorie <martin@address-in-sig.invalid> - 2014-11-07 02:36 +0000
Re: background processes (was HOW2 capture time of power-failure?) Joe Beanfish <joebeanfish@nospam.duh> - 2014-11-07 14:28 +0000
Re: background processes (was HOW2 capture time of power-failure?) not.socialnetwork@gmail.com - 2014-11-08 03:32 +0000
csiph-web