New answers tagged

1

In your sshd_config (mostly /etc/ssh/sshd_config), Try something like Subsystem sftp internal-sftp -f AUTH -l INFO or Subsystem sftp internal-sftp -l INFO I think these are the logging levels: QUIET, FATAL, ERROR, INFO, VERBOSE, DEBUG, DEBUG1, DEBUG2, and DEBUG3 If you need more details on log, increase the logging level


7

Use journalctl Since journald contains all the logs, you can use the journalctl command with suitable filters. In the case of boot.log, which used to contain messages from the init system, you could do: journalctl -b0 SYSLOG_PID=1 -b0 shows messages from the current boot, -b1 from the previous boot, and so on. Without the -b option, journalctl will show ...


5

In Ubuntu 16.04 the boot.log file is still located in the /var/log folder as you can see here. The boot logfile is from today (2016-04-29). Maybe something went wrong when you installed Ubuntu 16.04 or have upgraded the operating system from Ubuntu 15.10 to Ubuntu 16.04 LTS. Alternatively you can examine the general boot behavior from the comprehensive ...


0

You can do it using cat /proc/meminfo.


1

With the available information this is a bit of a shot in the dark, but... if the script is the one that issues the command to go back to sleep (which one?) the problem may be stdio buffering. So I will prepare a script that does the backup but will not go to sleep, call it bck_script. prepare another script that sends the PC to sleep, call it ...



Top 50 recent answers are included