On Mon, 26 Mar 2018 15:56:29 +0200 (CEST) "Carlos E. R." <robin.listas@telefonica.net> wrote:
On Sunday, 2018-03-25 at 16:48 +0100, Dave Howorth wrote:
On Sun, 25 Mar 2018 15:31:36 +0200 "Carlos E. R." <> wrote:
On 2018-03-25 15:06, Dave Howorth wrote:
On Sat, 24 Mar 2018 23:21:34 +0100 "Carlos E. R." <robin.listas@telefonica.net> wrote:
On 2018-03-24 21:58, Dave Howorth wrote:
After Carlos' recent message about NVRM, I looked at my /var/log/warn (before I realized his problem was NV specific). One thing I noticed was a bunch of warnings from org.mate.atril.Daemon[3030] that included things like
2018-03-23T11:32:22.265295+00:00 acer-suse org.mate.atril.Daemon[3030]: UnregisterDocument URI 'file:///tmp/mozilla_dhoworth0/UFPLS-Factsheet.pdf'
As to your question, the log is not public, only root and root group can read them.
Ah, not so bad then. EXCEPT:
$ l /var/log/warn -rw-r--r-- 1 root root 3319870 Mar 25 13:03 /var/log/warn $ l /var/log/messages -rw-r----- 1 root root 28381977 Mar 25 14:00 /var/log/messages
What's that all about? I haven't tinkered with logging AFAIK.
The permissions on yours are wrong (read by all), regarding privacy. We can work with that if you wish.
I've changed it to rw-r- but I don't understand why/how it was rw-r-r
Check the file "/etc/logrotate.d/syslog". You should have an entry like this:
/var/log/warn /var/log/messages /var/log/localmessages /var/log/firewall /var/log/acpid /var/log/NetworkManager /var/log/kernel /var/log/named{ compress dateext maxage 365 rotate 99 missingok notifempty size +4096k create 640 root root <============ sharedscripts postrotate /usr/bin/systemctl reload syslog.service > /dev/null endscript }
Yes my /etc/logrotate.d/syslog is identical to that.
If not, then check "/etc/permissions.local".
It just contains comments.
The date and the <4.5> are customizations. The rest is standard. The text message is up to the client app.
Well why is yours different to mine, if we both think they are standard?
The message part is up to the sending application, can't be customized. The parts before it can.
Ah, so yours is customised?
which also refers to private files I was reading from mozilla. It is an error but not at warning level (it goes at level 5, "notice").
#define KERN_EMERG "<0>" /* system is unusable */ #define KERN_ALERT "<1>" /* action must be taken immediately */ #define KERN_CRIT "<2>" /* critical conditions */ #define KERN_ERR "<3>" /* error conditions */ #define KERN_WARNING "<4>" /* warning conditions */ #define KERN_NOTICE "<5>" /* normal but significant condition */ #define KERN_INFO "<6>" /* informational */ #define KERN_DEBUG "<7>" /* debug-level messages */
What decides that notices get logged to /var/log/warn? I looked in /etc/rsyslog.conf and /etc/rsyslog.d/remote.conf and there's nothing there that I can see.
It is up to the application that sends the messages; rsyslog is doing the right thing.
I think you misunderstood. Since the message from atril (and evince) seems to be a 'notice' (as opposed to a 'warning' or worse) how can I stop 'notices' being logged to /var/log/warn? Indeed, given the file name and the presence of /var/log/messages as well, why are 'notices' logged to /var/log/'warn' at all?
Mine is indeed a notice, but your's I don't know. The "<4.5>" is "<facility.priority>". Chances are your string is a warning correctly filed.
Seems a strange change for the atril authors to have made when forking from evince. Still never mind; worse things happen at sea. Thanks for the help. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org