WTMP file cleared after upgrade Post: 302171351

8 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

manage the wtmp file

Here's a usefull perl script to trim the wtmp file, in case it got too big, which happens sometimes, or got curropted (which also happens often). You could learn from here how to parse the wtmp file... but of course for just reading its content always simply use "last" like Neo said.... ...

2. News, Links, Events and Announcements

Jon Johansen cleared in landmark DVD case

http://www.cnn.com/2003/TECH/01/07/dvd.johansen/index.html

3. Programming

Displaying fields in wtmp file?

Anyone have any idea on how to display the fields for each record stored in the wtmp file using C? Am I correct in thinking that the info stored in wtmp is in binary and that utmpx will be of some help? Being a beginner, I can come up with bits and pieces of what I might need in order to do the...

4. Forum Support Area for Unregistered Users & Account Problems

hotmail cleared account before activation

Hotmail cleared my email account before I had a chance to activate it. Can a admin re-send the activation email or activate my username? thanks

5. AIX

wtmp file

Hello everyone I have a problem with the file wtmp that is on /var/adm This file was not on this directory (adm). I try creating a new file with the correct rights (644) and owner (adm:adm) but It doesnt work. If I type the last command i get this last ora10g ...

6. AIX

Impacts of emptying /var/adm/wtmp file ?

In our operating procedures, if a workstation has a space problem in the /var filesystem, one of the most frequent case we were told is the size of the /var/adm/wtmp file. Someone once told me it is dangerous to do this. Is it ? I cannot say for certain that whomever wrote that procedure is...

7. Solaris

Unable to remove links of Cleared metas

Hi, have few meta devices which were cleared some year ago but still appear in /dev/md/rdsk. If I create a same meta device again, it shows old timestamp of 2009yr I tried devfsadm -C to clear unlinked links but of no use. What am I missing ?

8. AIX

wtmp file - is there a patch to export the data another file each day?

sorry for being a noob, i am trying to find which user accessed the server at what time and there ip address at first i used who command but the output didn't contain the ip address then i used the last command which provided me with the ip of the users but when i searched i searched and found that...

LEARN ABOUT OSF1

dh_systemd_start

DH_SYSTEMD_START(1)						     Debhelper						       DH_SYSTEMD_START(1)

NAME

       dh_systemd_start - start/stop/restart systemd unit files

SYNOPSIS

       dh_systemd_start [debhelperoptions] [--restart-after-upgrade] [--no-stop-on-upgrade] [unitfile...]

DESCRIPTION

       dh_systemd_start is a debhelper program that is responsible for starting/stopping or restarting systemd unit files in case no corresponding
       sysv init script is available.

       As with dh_installinit, the unit file is stopped before upgrades and started afterwards (unless --restart-after-upgrade is specified, in
       which case it will only be restarted after the upgrade).  This logic is not used when there is a corresponding SysV init script because
       invoke-rc.d performs the stop/start/restart in that case.

OPTIONS

       --restart-after-upgrade
	   Do not stop the unit file until after the package upgrade has been completed.  This is the default behaviour in compat 10.

	   In earlier compat levels the default was to stop the unit file in the prerm, and start it again in the postinst.

	   This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon
	   will not get confused by the package being upgraded while it's running before using this option.

       --no-restart-after-upgrade
	   Undo a previous --restart-after-upgrade (or the default of compat 10).  If no other options are given, this will cause the service to
	   be stopped in the prerm script and started again in the postinst script.

       -r, --no-stop-on-upgrade, --no-restart-on-upgrade
	   Do not stop service on upgrade.

       --no-start
	   Do not start the unit file after upgrades and after initial installation (the latter is only relevant for services without a
	   corresponding init script).

NOTES

       Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command (with the same arguments).
       Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts.

       Note that dh_systemd_start should be run after dh_installinit so that it can detect corresponding SysV init scripts. The default sequence
       in dh does the right thing, this note is only relevant when you are calling dh_systemd_start manually.

SEE ALSO

       debhelper(7)

AUTHORS

       pkg-systemd-maintainers@lists.alioth.debian.org

11.1.6ubuntu2							    2018-05-10						       DH_SYSTEMD_START(1)