conf/62230: log-in-vain issues it's msg every time 'mail'
command is used.
Barbish3 at adelphia.net
Mon Feb 2 09:39:26 PST 2004
I disagree with you on this.
Log-in-vain purpose in life is to interrogate attempts from
the external interface, not the localhost internal functions,
which this clearly is what is happening.
Sure there are work around solutions for this bug.
If you think this is such an trivial annoyance bug that it's
does not warrant attention, then just come out and say so,
and not beat around the bush with work around solutions in an
poor effort to conceal your reluctance to perform system
>From what little documentation is published on Log-in-vain,
it is not functioning correctly, period.
Anybody look at the percentage of bug reports that get closed
right out of hand to the ones that really get serious attention?
Maybe there is some thing wrong with the evaluation criteria you
people use to evaluate bug reports like this one.
This is not an single event but an attitude that is too common
among the people who review newly filed bug reports.
It does nothing to foster confidence in the bug report system,
or for that matter in the quality of the overall FBSD system.
Just my observations of the over all bug reporting system, it stinks
and needs to be readdressed so it's more amiable to really getting
bugs fixed and not passing the buck, offering work around solutions.
Just because there are many work around solutions does not warrant
fixing the bug causing the problem in the first place.
No use beating an dead horse who can't hear what being said anyway.
From: Ceri Davies [mailto:ceri at FreeBSD.org]
Sent: Monday, February 02, 2004 11:22 AM
To: FBSD_User at a1poweruser.com; ceri at FreeBSD.org;
freebsd-bugs at FreeBSD.org
Subject: Re: conf/62230: log-in-vain issues it's msg every time
'mail' command is used.
Synopsis: log-in-vain issues it's msg every time 'mail' command is
State-Changed-When: Mon Feb 2 08:20:36 PST 2004
This is not a problem with the log in vain code, which is doing
as it's supposed to do, but rather with the configuration of your
As suggested by Bjoern A. Zeeb, you should sent a post to
questions at FreeBSD.org asking for help on configuring your system to
resolve these issues.
More information about the freebsd-questions