[CentOS] Exists some problem with cronjobs under CentOS7
C.L. Martinez
carlopmart at gmail.comWed Oct 14 14:09:46 UTC 2015
- Previous message: [CentOS] Exists some problem with cronjobs under CentOS7
- Next message: [CentOS] Exists some problem with cronjobs under CentOS7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 10/14/2015 01:56 PM, Jonathan Billings wrote: > lsof /dev/log Uhmm ... that is not what I expect: lsof: WARNING: can't stat() fuse.gvfsd-fuse file system /run/user/1000/gvfs Output information may be incomplete. COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME systemd 1 root 27u unix 0xffff880250ea0f00 0t0 1436 /dev/log systemd-j 263 root 5u unix 0xffff880250ea0f00 0t0 1436 /dev/log In theory, rsyslog is listenning to uxsock and imjournal: # rsyslog configuration file # For more information see /usr/share/doc/rsyslog-*/rsyslog_conf.html # If you experience problems, see http://www.rsyslog.com/doc/troubleshoot.html #### MODULES #### # The imjournal module bellow is now used as a message source instead of imuxsock. $ModLoad imuxsock # provides support for local system logging (e.g. via logger command) $ModLoad imjournal # provides access to the systemd journal #$ModLoad imklog # reads kernel messages (the same are read from journald) #$ModLoad immark # provides --MARK-- message capability
- Previous message: [CentOS] Exists some problem with cronjobs under CentOS7
- Next message: [CentOS] Exists some problem with cronjobs under CentOS7
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS mailing list