Your message dated Mon, 11 Jul 2005 14:43:19 -0400 (EDT)
with message-id <[EMAIL PROTECTED]>
and subject line too old and merged
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 19 Jan 1997 22:07:56 +0000
Received: (qmail 31034 invoked from network); 19 Jan 1997 22:07:53 -0000
Received: from tekla.ing.umu.se ([EMAIL PROTECTED])
by master.debian.org with SMTP; 19 Jan 1997 22:07:52 -0000
Received: from thelma.ing.umu.se ([EMAIL PROTECTED] [130.239.117.81])
by tekla.ing.umu.se (8.8.4/8.8.4) with SMTP
id XAA03791 for <[EMAIL PROTECTED]>; Sun, 19 Jan 1997 23:04:39 +0100
Date: Sun, 19 Jan 1997 23:04:43 +0100 (MET)
From: Niklas Edmundsson <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: sessreg logs garbage.
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Package: xbase
Version: 3.2-1.1
We are using a newly installed Debian 1.2 system with kernel 2.0.27.
When sessreg is invoked to log that a user has logged in via xdm it writes
garbage to both wtmp & utmp.
Example: (last -f <broken wtmp-file>
root xdm `**********@ Fri Jan 3 04:30 - 04:30 (00:00)
The utmp-file contains similar rubbish.
sessreg is invoked as follows:
sessreg -L /var/log/lastlog -u /var/run/utmp -w /var/log/wtmp -a -l xdm -h
$DISPLAY $USER
This should produce an output similar to this:
nikke xdm tfe2s234.tfe2s.u Sun Jan 5 18:05 - 20:13 (02:07)
We know that the invokation is correct since we are now using an old
sessreg from our old installation. They show the same help-text so it can
be assumed that they have the same syntax.
It looks like sessreg uses the wrong format of the utmp/wtmp-file.
It would be nice if this quite serious problem could be remedied as soon
as possible, since we are now using an ancient A.OUT sessreg that refuses
to execute if it's stored on our /usr-partition (4k block-size). It only
works from a 1k block-size partition !
I am surprised that noone else has reported this bug, are there no people
logging their xdm-logins ??
/Nikke
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Niklas Edmundsson, Admin @ ing.umu.se | [EMAIL PROTECTED]
---------------------------------------------------------------------------
Black Holes were created when God divided by zero!
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
---------------------------------------
Received: (at 11147-done) by bugs.debian.org; 11 Jul 2005 18:40:29 +0000
>From [EMAIL PROTECTED] Mon Jul 11 11:40:29 2005
Return-path: <[EMAIL PROTECTED]>
Received: from grex.cyberspace.org [216.86.77.194] (exim)
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1Ds3Cf-0004Ww-00; Mon, 11 Jul 2005 11:40:29 -0700
Received: from dajo (helo=localhost)
by grex.cyberspace.org with local-esmtp (Exim 4.42)
id 1Ds3FP-0000YK-6i; Mon, 11 Jul 2005 14:43:19 -0400
Date: Mon, 11 Jul 2005 14:43:19 -0400 (EDT)
From: Daniel Jonan <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED], [EMAIL PROTECTED]
cc: [EMAIL PROTECTED], [EMAIL PROTECTED],
[EMAIL PROTECTED]
Subject: too old and merged
Message-ID: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: Daniel Jonan <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2005_01_02
X-Spam-Level:
X-CrossAssassin-Score: 2
closing
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
