After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 82906 - Should support --lastlog and --nolastlog
Should support --lastlog and --nolastlog
Status: RESOLVED DUPLICATE of bug 93906
Product: gnome-terminal
Classification: Core
Component: general
1.9.x
Other other
: Normal normal
: ---
Assigned To: Havoc Pennington
GNOME Terminal Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-05-24 17:10 UTC by Miguel de Icaza
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Miguel de Icaza 2002-05-24 17:10:06 UTC 
Should support controlling whether the lastlog records are updated or not.
Comment 1 Havoc Pennington 2002-05-24 18:32:09 UTC 
The command line option should not be needed, it's done via profiles,
see bug 82904.

I see now though that zvt_term_forkpty() takes a mask for which
records to update, rather than a boolean for whether to update
records. So that 
would involve a UI change, but even without the UI change the current
code is broken.

I need someone to explain when the various records are used, and what
the default settings for whether to use them should be. Should these
be preferences or configure-time checks for specific operating systems.
Comment 2 Miguel de Icaza 2002-05-24 18:45:11 UTC 
They are always there.

utmp/wtmp/lastlog/login control different things.  They are all
clearly documented in the xterm man page and in the 1.x gnome-terminal
man page (and also rxvt, but the documentation is poor).

The features in gnome-terminal 1.x are not there because I had nothing
better to do.  They are there because Unix users expect those features
to be there.
Comment 3 Havoc Pennington 2002-09-22 19:58:28 UTC 

*** This bug has been marked as a duplicate of 93906 ***