Discuss November 2018

discuss@lists.centos.org

96 participants
69 discussions

CentOS 6: Logrotate / selinux problem
by Robert Heller 11 Nov '18

11 Nov '18

Ever since a recent power failure I have been getting a Logrotate error. My machine is on a UPS -- it shutdown cleanly, but I suspect that its BIOS/RTC battery is dead, since the machine came up thinking it was 1982 :-(. I reset the clock and everything is fine, *except* I had to delete Logrotate's state files (which had bad dates). But now Logrotate is raising the error: error: error creating unique temp file: Permission denied and audit.log contains these messages: type=AVC msg=audit(1541925899.209:28416): avc: denied { create } for pid=5281 comm="logrotate" name="logrotate_temp.bPbOYF" scontext=system_u:system_r:logrotate_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:var_lib_t:s0 tclass=file type=SYSCALL msg=audit(1541925899.209:28416): arch=c000003e syscall=2 success=no exit=-13 a0=7ffdd2d613d0 a1=c2 a2=180 a3=0 items=0 ppid=5279 pid=5281 auid=0 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=1865 comm="logrotate" exe="/usr/sbin/logrotate" subj=system_u:system_r:logrotate_t:s0-s0:c0.c1023 key=(null) It is (obviously) a selinux problem, but I don't know what file or directory needs to be fixed. How to I find that out? I turned on verbose in /etc/cron.daily/logrotate: #!/bin/sh /usr/sbin/logrotate -v /etc/logrotate.conf EXITVALUE=$? if [ $EXITVALUE != 0 ]; then /usr/bin/logger -t logrotate "ALERT exited abnormally with [$EXITVALUE]" fi and am getting this (typical) message from logrotate daily: reading config file /etc/logrotate.conf including /etc/logrotate.d reading config file apcupsd reading config info for /var/log/apcupsd.events reading config file ConsoleKit reading config info for /var/log/ConsoleKit/history reading config file cups reading config info for /var/log/cups/*_log reading config file cyrus-imapd reading config info for /var/log/imapd.log /var/log/auth.log reading config file dracut reading config info for /var/log/dracut.log reading config file httpd reading config info for /var/log/httpd/*log reading config file iscsiuiolog reading config info for /var/log/iscsiuio.log reading config file libvirtd reading config info for /var/log/libvirt/libvirtd.log reading config file libvirtd.lxc reading config info for /var/log/libvirt/lxc/*.log reading config file libvirtd.qemu reading config info for /var/log/libvirt/qemu/*.log reading config file mcelog reading config info for /var/log/mcelog reading config file mysqld reading config file named reading config info for /var/named/data/named.run reading config file numad reading config info for /var/log/numad.log reading config file ppp reading config info for /var/log/ppp/connect-errors reading config file psacct reading config info for /var/account/pacct reading config file sa-update reading config info for /var/log/sa-update.log reading config file sssd reading config info for /var/log/sssd/*.log reading config file syslog reading config info for /var/log/cron /var/log/maillog /var/log/messages /var/log/secure /var/log/spooler reading config file wpa_supplicant reading config info for /var/log/wpa_supplicant.log reading config file yum reading config info for /var/log/yum.log reading config info for /var/log/wtmp reading config info for /var/log/btmp Handling 22 logs rotating pattern: /var/log/apcupsd.events weekly (4 rotations) empty log files are not rotated, old logs are removed considering log /var/log/apcupsd.events log does not need rotating rotating pattern: /var/log/ConsoleKit/history monthly (6 rotations) empty log files are not rotated, old logs are removed considering log /var/log/ConsoleKit/history log does not need rotating rotating pattern: /var/log/cups/*_log weekly (4 rotations) empty log files are not rotated, old logs are removed considering log /var/log/cups/access_log log needs rotating considering log /var/log/cups/error_log log needs rotating considering log /var/log/cups/page_log log needs rotating rotating log /var/log/cups/access_log, log->rotateCount is 4 dateext suffix '-20181111' glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]' rotating log /var/log/cups/error_log, log->rotateCount is 4 dateext suffix '-20181111' glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]' rotating log /var/log/cups/page_log, log->rotateCount is 4 dateext suffix '-20181111' glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]' fscreate context set to system_u:object_r:cupsd_log_t:s0 renaming /var/log/cups/access_log to /var/log/cups/access_log-20181111 creating new /var/log/cups/access_log mode = 0600 uid = 0 gid = 7 fscreate context set to system_u:object_r:cupsd_log_t:s0 renaming /var/log/cups/error_log to /var/log/cups/error_log-20181111 creating new /var/log/cups/error_log mode = 0600 uid = 0 gid = 7 fscreate context set to unconfined_u:object_r:cupsd_log_t:s0 renaming /var/log/cups/page_log to /var/log/cups/page_log-20181111 creating new /var/log/cups/page_log mode = 0600 uid = 0 gid = 7 removing old log /var/log/cups/access_log-19821102 removing old log /var/log/cups/error_log-19821102 removing old log /var/log/cups/page_log-19821102 rotating pattern: /var/log/imapd.log /var/log/auth.log weekly (4 rotations) empty log files are rotated, old logs are removed considering log /var/log/imapd.log log /var/log/imapd.log does not exist -- skipping considering log /var/log/auth.log log /var/log/auth.log does not exist -- skipping not running postrotate script, since no logs were rotated rotating pattern: /var/log/dracut.log 1048576 bytes (4 rotations) empty log files are not rotated, old logs are removed considering log /var/log/dracut.log log does not need rotating rotating pattern: /var/log/httpd/*log weekly (4 rotations) empty log files are not rotated, old logs are removed considering log /var/log/httpd/access_log log needs rotating considering log /var/log/httpd/error_log log needs rotating considering log /var/log/httpd/ssl_access_log log does not need rotating considering log /var/log/httpd/ssl_error_log log does not need rotating considering log /var/log/httpd/ssl_request_log log does not need rotating considering log /var/log/httpd/suexec.log log does not need rotating rotating log /var/log/httpd/access_log, log->rotateCount is 4 dateext suffix '-20181111' glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]' rotating log /var/log/httpd/error_log, log->rotateCount is 4 dateext suffix '-20181111' glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]' fscreate context set to unconfined_u:object_r:httpd_log_t:s0 renaming /var/log/httpd/access_log to /var/log/httpd/access_log-20181111 creating new /var/log/httpd/access_log mode = 0644 uid = 0 gid = 0 fscreate context set to unconfined_u:object_r:httpd_log_t:s0 renaming /var/log/httpd/error_log to /var/log/httpd/error_log-20181111 creating new /var/log/httpd/error_log mode = 0644 uid = 0 gid = 0 running postrotate script removing old log /var/log/httpd/access_log-20181007 removing old log /var/log/httpd/error_log-20181021 rotating pattern: /var/log/iscsiuio.log weekly (4 rotations) empty log files are not rotated, old logs are removed considering log /var/log/iscsiuio.log log /var/log/iscsiuio.log does not exist -- skipping not running postrotate script, since no logs were rotated rotating pattern: /var/log/libvirt/libvirtd.log weekly (4 rotations) empty log files are rotated, only log files >= 102400 bytes are rotated, old logs are removed considering log /var/log/libvirt/libvirtd.log log does not need rotating rotating pattern: /var/log/libvirt/lxc/*.log weekly (4 rotations) empty log files are rotated, only log files >= 102400 bytes are rotated, old logs are removed considering log /var/log/libvirt/lxc/*.log log /var/log/libvirt/lxc/*.log does not exist -- skipping rotating pattern: /var/log/libvirt/qemu/*.log weekly (4 rotations) empty log files are rotated, only log files >= 102400 bytes are rotated, old logs are removed considering log /var/log/libvirt/qemu/c532guest.log log does not need rotating considering log /var/log/libvirt/qemu/c632guest.log log does not need rotating considering log /var/log/libvirt/qemu/c664guest.log log does not need rotating considering log /var/log/libvirt/qemu/c764guest.log log does not need rotating considering log /var/log/libvirt/qemu/C764guest.log log does not need rotating considering log /var/log/libvirt/qemu/msbuilder.log log does not need rotating considering log /var/log/libvirt/qemu/testsvn.log log does not need rotating considering log /var/log/libvirt/qemu/ub120432.log log does not need rotating considering log /var/log/libvirt/qemu/ub120464.log log does not need rotating rotating pattern: /var/log/mcelog 2097152 bytes (99 rotations) empty log files are not rotated, old logs are removed considering log /var/log/mcelog log /var/log/mcelog does not exist -- skipping not running postrotate script, since no logs were rotated rotating pattern: /var/named/data/named.run weekly (4 rotations) empty log files are rotated, old logs are removed considering log /var/named/data/named.run log needs rotating rotating log /var/named/data/named.run, log->rotateCount is 4 dateext suffix '-20181111' glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]' fscreate context set to unconfined_u:object_r:named_cache_t:s0 renaming /var/named/data/named.run to /var/named/data/named.run-20181111 creating new /var/named/data/named.run mode = 0644 uid = 25 gid = 25 running postrotate script removing old log /var/named/data/named.run-20181021 rotating pattern: /var/log/numad.log 1048576 bytes (5 rotations) empty log files are rotated, old logs are removed considering log /var/log/numad.log log /var/log/numad.log does not exist -- skipping rotating pattern: /var/log/ppp/connect-errors after 1 days (5 rotations) empty log files are not rotated, old logs are removed considering log /var/log/ppp/connect-errors log /var/log/ppp/connect-errors does not exist -- skipping rotating pattern: /var/account/pacct after 1 days (31 rotations) empty log files are not rotated, old logs are removed considering log /var/account/pacct log does not need rotating not running postrotate script, since no logs were rotated rotating pattern: /var/log/sa-update.log monthly (4 rotations) empty log files are not rotated, old logs are removed considering log /var/log/sa-update.log log does not need rotating rotating pattern: /var/log/sssd/*.log weekly (2 rotations) empty log files are not rotated, old logs are removed considering log /var/log/sssd/*.log log /var/log/sssd/*.log does not exist -- skipping not running postrotate script, since no logs were rotated rotating pattern: /var/log/cron /var/log/maillog /var/log/messages /var/log/secure /var/log/spooler weekly (4 rotations) empty log files are rotated, old logs are removed considering log /var/log/cron log needs rotating considering log /var/log/maillog log needs rotating considering log /var/log/messages log needs rotating considering log /var/log/secure log needs rotating considering log /var/log/spooler log needs rotating rotating log /var/log/cron, log->rotateCount is 4 dateext suffix '-20181111' glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]' rotating log /var/log/maillog, log->rotateCount is 4 dateext suffix '-20181111' glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]' rotating log /var/log/messages, log->rotateCount is 4 dateext suffix '-20181111' glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]' rotating log /var/log/secure, log->rotateCount is 4 dateext suffix '-20181111' glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]' rotating log /var/log/spooler, log->rotateCount is 4 dateext suffix '-20181111' glob pattern '-[0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]' fscreate context set to system_u:object_r:var_log_t:s0 renaming /var/log/cron to /var/log/cron-20181111 creating new /var/log/cron mode = 0600 uid = 0 gid = 0 fscreate context set to system_u:object_r:var_log_t:s0 renaming /var/log/maillog to /var/log/maillog-20181111 creating new /var/log/maillog mode = 0600 uid = 0 gid = 0 fscreate context set to system_u:object_r:var_log_t:s0 renaming /var/log/messages to /var/log/messages-20181111 creating new /var/log/messages mode = 0600 uid = 0 gid = 0 fscreate context set to system_u:object_r:var_log_t:s0 renaming /var/log/secure to /var/log/secure-20181111 creating new /var/log/secure mode = 0600 uid = 0 gid = 0 fscreate context set to system_u:object_r:var_log_t:s0 renaming /var/log/spooler to /var/log/spooler-20181111 creating new /var/log/spooler mode = 0600 uid = 0 gid = 0 running postrotate script removing old log /var/log/cron-20181021 removing old log /var/log/maillog-20181021 removing old log /var/log/messages-20181021 removing old log /var/log/secure-20181021 removing old log /var/log/spooler-20181021 rotating pattern: /var/log/wpa_supplicant.log 30720 bytes (4 rotations) empty log files are not rotated, old logs are removed considering log /var/log/wpa_supplicant.log log does not need rotating not running postrotate script, since no logs were rotated rotating pattern: /var/log/yum.log yearly (4 rotations) empty log files are not rotated, old logs are removed considering log /var/log/yum.log log does not need rotating rotating pattern: /var/log/wtmp monthly (1 rotations) empty log files are rotated, only log files >= 1048576 bytes are rotated, old logs are removed considering log /var/log/wtmp log does not need rotating rotating pattern: /var/log/btmp monthly (1 rotations) empty log files are rotated, old logs are removed considering log /var/log/btmp log does not need rotating set default create context error: error creating unique temp file: Permission denied /var/lib/logrotate.status contains: logrotate state -- version 2 "/var/log/btmp" 2018-11-6 "/var/log/ConsoleKit/history" 2018-11-6 "/var/log/libvirt/qemu/c664guest.log" 2018-11-6 "/var/log/httpd/access_log" 2018-11-4 "/var/log/spooler" 2018-11-6 "/var/log/sssd/*.log" 2018-11-4 "/var/log/mcelog" 2018-11-4 "/var/log/libvirt/qemu/testsvn.log" 2018-11-6 "/var/log/iscsiuio.log" 2018-11-4 "/var/log/libvirt/qemu/c532guest.log" 2018-11-6 "/var/log/wtmp" 2018-11-6 "/var/log/auth.log" 2018-11-4 "/var/log/yum.log" 2018-11-4 "/var/log/ppp/connect-errors" 2018-11-4 "/var/log/httpd/ssl_error_log" 2018-11-4 "/var/log/secure" 2018-11-6 "/var/log/messages" 2018-11-6 "/var/log/libvirt/qemu/c764guest.log" 2018-11-6 "/var/log/httpd/ssl_request_log" 2018-11-4 "/var/log/httpd/suexec.log" 2018-11-4 "/var/log/libvirt/qemu/ub120432.log" 2018-11-6 "/var/log/cron" 2018-11-6 "/var/account/pacct" 2018-11-4 "/var/log/httpd/error_log" 2018-11-6 "/var/log/libvirt/libvirtd.log" 2018-11-6 "/var/log/dracut.log" 2018-11-4 "/var/log/imapd.log" 2018-11-4 "/var/log/sa-update.log" 2018-11-4 "/var/log/libvirt/qemu/c632guest.log" 2018-11-6 "/var/log/cups/page_log" 2018-11-4 "/var/log/libvirt/qemu/msbuilder.log" 2018-11-6 "/var/log/cups/error_log" 2018-11-4 "/var/named/data/named.run" 2018-11-6 "/var/log/maillog" 2018-11-6 "/var/log/numad.log" 2018-11-4 "/var/log/wpa_supplicant.log" 2018-11-4 "/var/log/libvirt/lxc/*.log" 2018-11-4 "/var/log/httpd/ssl_access_log" 2018-11-4 "/var/log/cups/access_log" 2018-11-4 "/var/log/libvirt/qemu/ub120464.log" 2018-11-6 "/var/log/libvirt/qemu/C764guest.log" 2018-11-6 "/var/log/apcupsd.events" 2018-11-4 -- Robert Heller -- 978-544-6933 Deepwoods Software -- Custom Software Services http://www.deepsoft.com/ -- Linux Administration Services heller(a)deepsoft.com -- Webhosting Services

1 0

Load html file into elinks from desktop
by Frank Cox 10 Nov '18

10 Nov '18

With a html file on my (Mate) desktop I would like to be able to right-click on it and select "open with" and have it load into elinks. But I haven't yet figured out the magic command line that I need for this to happen. gnome-terminal --command="elinks %s" That loads elinks but doesn't load the html file into it. gnome-terminal --command="cat %s | elinks" doesn't work either. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

2 1

last failed login...
by Fred Smith 10 Nov '18

10 Nov '18

Hi all! I just (well, a few days ago) installed C7 on a new-to-me (used) laptop, and notice something I've not noticed before, either on my personal desktop, or other C7 machines I use: every time I log in, it gives me a message something like "last failed login <timestamp>", where the date and time it gives are RIGHT NOW, just at the time I'm logging in (which succeeds). Anybody know why that would be happening? BTW, using the Mate desktop, but did not change the DM, so I think it is still GDM. Thanks in advance! Fred -- ---- Fred Smith -- fredex(a)fcshome.stoneham.ma.us ----------------------------- The Lord detests the way of the wicked but he loves those who pursue righteousness. ----------------------------- Proverbs 15:9 (niv) -----------------------------

1 0

Red Hat is Planning To Deprecate KDE on RHEL By 2024
by Frank Cox 10 Nov '18

10 Nov '18

https://www.theregister.co.uk/2018/11/02/rhel_deprecates_kde/ That's still several years in the future, of course. I use Mate on all of my machines rather than Gnome or KDE and I'm sure many of you fine folks do the same. But it's interesting nonetheless. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com

25 37

Fresh install C7 nvidia
by Jerry Geis 10 Nov '18

10 Nov '18

I am install C7.5 on a nvidia unit and nvidia-detect tells me to use kmod-nvidia-390xx so I do the yum install and and after a long time I see this -> Processing Dependency: kernel(__drm_atomic_helper_crtc_duplicate_state) = 0xa5f3a170 for package: kmod-nvidia-390xx-390.87-2.el7_6.elrepo.x86_64 --> Processing Dependency: kernel(__drm_atomic_helper_crtc_destroy_state) = 0x00a9c70b for package: kmod-nvidia-390xx-390.87-2.el7_6.elrepo.x86_64 --> Processing Dependency: kernel(__check_object_size) = 0x88db9f48 for package: kmod-nvidia-390xx-390.87-2.el7_6.elrepo.x86_64 --> Processing Dependency: kernel(___ratelimit) = 0x155f4108 for package: kmod-nvidia-390xx-390.87-2.el7_6.elrepo.x86_64 --> Processing Dependency: kernel >= 3.10.0-957.el7 for package: kmod-nvidia-390xx-390.87-2.el7_6.elrepo.x86_64 ---> Package nvidia-x11-drv-390xx.x86_64 0:390.87-1.el7_5.elrepo will be installed Packages skipped because of dependency problems: kmod-nvidia-390xx-390.87-2.el7_6.elrepo.x86_64 from elrepo nvidia-x11-drv-390xx-390.87-1.el7_5.elrepo.x86_64 from elrepo I have also tried --skip-broken and get the same result as above. have I missed something ? This has always working in the past. Thanks, Jerry

4 3

Yum through a proxy
by Vic Chester 09 Nov '18

09 Nov '18

I have configured yum to use a proxy via the yum.conf file by adding: proxy=http://myproxy.com:8080/ What I noticed when running yum check-up date is that some requests are going through the proxy while the system seems to be trying to resolve the domains of other hosts in the repo and trying to establish direct connections to them instead of going through the proxy. Can anyone explain this behavior?

3 3

CentOS-announce Digest, Vol 165, Issue 1
by centos-announce-request＠centos.org 09 Nov '18

09 Nov '18

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2018:3406 Critical CentOS 6 python-paramiko Security Update (Johnny Hughes) 2. CEBA-2018:3454 CentOS 6 tzdata BugFix Update (Johnny Hughes) 3. CESA-2018:3403 Important CentOS 6 thunderbird Security Update (Johnny Hughes) ---------------------------------------------------------------------- Message: 1 Date: Mon, 5 Nov 2018 18:49:55 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:3406 Critical CentOS 6 python-paramiko Security Update Message-ID: <20181105184955.GA23857(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:3406 Critical Upstream details at : https://access.redhat.com/errata/RHSA-2018:3406 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: ba22dc027fdb5a2399c658d74ec55e6efe08225d65e9aaf3ff5837319c0a67eb python-paramiko-1.7.5-5.el6_10.noarch.rpm x86_64: ba22dc027fdb5a2399c658d74ec55e6efe08225d65e9aaf3ff5837319c0a67eb python-paramiko-1.7.5-5.el6_10.noarch.rpm Source: f0e20741d17d1c06461711205d12b0edf44e5011cf15c7173dcb305a4c49e46d python-paramiko-1.7.5-5.el6_10.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 2 Date: Mon, 5 Nov 2018 18:51:17 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CEBA-2018:3454 CentOS 6 tzdata BugFix Update Message-ID: <20181105185117.GA24083(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Bugfix Advisory 2018:3454 Upstream details at : https://access.redhat.com/errata/RHBA-2018:3454 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 687d4198ba7ddcc02ab3e32b7a757e82474c862a77b6f877fe433aedb42f665d tzdata-2018g-1.el6.noarch.rpm 4673a5ff13fc83c51d537c997c7161affb1a94445798c2976d133309cbb70418 tzdata-java-2018g-1.el6.noarch.rpm x86_64: 687d4198ba7ddcc02ab3e32b7a757e82474c862a77b6f877fe433aedb42f665d tzdata-2018g-1.el6.noarch.rpm 4673a5ff13fc83c51d537c997c7161affb1a94445798c2976d133309cbb70418 tzdata-java-2018g-1.el6.noarch.rpm Source: a38862e075a0669152f341ff55a6675b8f1476fdd876d51b408b10011e99f8e8 tzdata-2018g-1.el6.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Message: 3 Date: Mon, 5 Nov 2018 18:57:41 +0000 From: Johnny Hughes <johnny(a)centos.org> To: centos-announce(a)centos.org Subject: [CentOS-announce] CESA-2018:3403 Important CentOS 6 thunderbird Security Update Message-ID: <20181105185741.GA24387(a)n04.lon1.karan.org> Content-Type: text/plain; charset=us-ascii CentOS Errata and Security Advisory 2018:3403 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:3403 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 8df523679c35149a2785c6056419e4087d991acf7a5415761d5353b5d7612840 thunderbird-60.2.1-5.el6.centos.i686.rpm x86_64: 4ba750dbed745049285ca8c7345b4bc8366efd5bda230f8d09a1604e2544c2b3 thunderbird-60.2.1-5.el6.centos.x86_64.rpm Source: fa1c647433cdb857e464a18c595ad567662feb698ff9beb544e3e8b9bca32773 thunderbird-60.2.1-5.el6.centos.src.rpm -- Johnny Hughes CentOS Project { http://www.centos.org/ } irc: hughesjr, #centos(a)irc.freenode.net Twitter: @JohnnyCentOS ------------------------------ Subject: Digest Footer _______________________________________________ CentOS-announce mailing list CentOS-announce(a)centos.org https://lists.centos.org/mailman/listinfo/centos-announce ------------------------------ End of CentOS-announce Digest, Vol 165, Issue 1 ***********************************************

1 0

A newbie question about searching an installed packet
by Pierre Malard 08 Nov '18

08 Nov '18

Hi, I’m french and literally one. So I’m not really easy with Sheakespeare language. So, accept my apologies. As write in subject, I’m a newbie about CentOS an all RedHat declines. I wrote a Shell script for ours Debians (all sort of Debian like) which verify which packets are present before running. I thought I had found an equivalent with « yum list installed | grep <packet> » command but I have sometime alerts about a lock because an other instance of « yum » is running. I don’t understand why a simple « yum list » impose that! I suppose, like with « aptitude search », it is an understanding scorie. I’m sure there is an other way to do what I want to do: just verify if a packet is, or not, installed. Help? Thanks -- Pierre Malard « On ne peut pas pousser à fond l'éducation politique et l'éducation tout court de masses sans l'accompagner d'un développement économique, culturel et social parallèle. » Romain Gary - "Les racines du ciel" |\ _,,,---,,_ /,`.-'`' -. ;-;;,_ |,4- ) )-,_. ,\ ( `'-' '---''(_/--' `-'\_) πr perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-. ;-;;,_: |,A- ) )-,_. ,\ ( `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"' `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print' - --> Ce message n’engage que son auteur <--

2 2

Desktop files change?
by david allan finch 08 Nov '18

08 Nov '18

Hi, Does anyone know if they changed the way that desktop files for apps work? It seams that inside your start script you can no longer change your scripts directory. Does it now call some form of restricted shell? Anyone know where you can track these changes? Thanks -- / The whole history of this invention has been a struggle /\|/\ against time - Charles Babbage 1837 on the Analytical Engine | K | All Hail Discordia - Burn all Orange Books! \___/ david.allan at finch.org - http://www.ironfort.co.uk

1 1

command in kickstart file to write disklabel?
by Valeri Galtsev 08 Nov '18

08 Nov '18

Dear All, At some point after release of CentOS 7 (though this thing might have started before, it is just when _I_ noticed it) I discovered that if I stick into machine drive without disk label, and then do kickstart installation, the command in kickstart file clearpart --initlabel does not work. Even worse: if I just use GUI installer the drive is not listed between available disks. If I switch in the same installer to some virtual console Ctrl + Alt + F2 I can see that the kernel installer run under definitely sees the drive: /dev/sda is present. It must be an issue beaten to death, but somehow my search ability fails on this particular one (I am not "googling" but "duckduckgo-ing", though this shouldn't matter the problem as usually must be myself). Can someone suggest something? I know it is trivial to just create disklabel before sticking drive in machine, but once I'm using kickstart, any need in separate manual steps feels really lame. Thanks a lot for all your help in advance! Valeri ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss November 2018