Hot answers tagged

3

I'm going to assume you're on CentOS 7+ or Ubuntu 15.04+ which both come with systemd. Systemd has some great tools for figuring out how long your system took to boot along with some visualizations to see why. For the most basic output just run systemd-analyze and you'll get a nice summary like so Startup finished in 853ms (kernel) + 3min 50.610s (initrd) ...


2

I think the reason you're seeing this discrepancy is that your BIOS clock is set to local time and not to UTC, and something has missed adjusting it for the winter/summer time change. (Dual booting could have this effect, as could the system being switched off across the time change.) My recommendation would be to run the system on UTC and have the OS ...


2

If you define an alias such as alias ls='ls --time-style=long-iso' then ls invocations which end up displaying dates will use that.


2

The only real problem is that you assign to $AAA and $BBB instead of AAA and BBB. So if you do (nearly the same as your code): AAA="2015-12-11 20:00:00" BBB="2015-12-12 01:00:00" awk '$2" "$3>="'"$AAA"'" && $2" "$3<="'"$BBB"'"' file.txt > newfile.txt it should already work. But I recommend the following further changes in order to reduce ...


2

The time builtin of bash shows timing info on STDERR after the command after it (the actual one) returns. So unless you grouped them and pass the STDERR of the group to a file, only the actual command's STDERR will be redirected to the file and the file will be closed when command returns (prior to time shows its info). You can use command grouping, ...



Only top voted, non community-wiki answers of a minimum length are eligible