New answers tagged log
Not a a complete answer, but this may help understand what's going on. From http://man7.org/linux/man-pages/man7/capabilities.7.html: Capability bounding set prior to Linux 2.6.25 In kernels before 2.6.25, the capability bounding set is a system- wide attribute that affects all threads on the system. The bounding set is accessible via the file ...
Search for log in dash. Look for: You can go through various logs: You can also use it to open and view other logs. To view the log currently in memory, run dmesg, you may want to maximise the terminal first, as there is quite alot of output... For current System Usage, use 'System Monitor': And for the rest, just use Terminal
I had the same issue, here is what my exim4 paniclog looked like: $ sudo cat /var/log/exim4/paniclog 2014-02-01 21:36:51 socket bind() to port 25 for address 127.0.0.1 failed: Address already in use: daemon abandoned 2014-02-01 22:03:33 socket bind() to port 25 for address 127.0.0.1 failed: Address already in use: daemon abandoned 2014-02-01 22:33:19 ...
It's not a bug, it's a feature! ;) See Ubuntu Bug #743858. This was actually done on purpose, in order to close Debian Bug #314956. While at the end of that Ubuntu bug report there is some discussion about re-enabling /var/log/btmp logging for sshd, it seems nothing has been done so far. You could try to bump it up if you like.
By default it is in user home directory and and named hs_err_pidxxxx.log where xxxx is the PID number.
It looks like it's the error log that's filling up, not the access log. Check the error log level ("LogLevel") in the config file located at /etc/cups/cupsd.conf. It should normally be "LogLevel warn" or "LogLevel error". If it's set to "debug" you will get a ton of messages you don't need. Check the error log (/var/log/cups/error_log) for errors. Given ...
'sudo initctl log-priority debug' will set the most verbose log level. You should be able to view the logs at /var/log/syslog, or if it's a custom script the logs might be at /var/log/upstart/[script-name]
This blog entry have a extended description on how it can be done Perhaps the method of this answer could be used Bash history handling with multiple terminals
Top 50 recent answers are included