[CentOS] Basic authentication - maybe off topoc
Hi - I am using CentOS 7.3 and trying to receive basic authentication. I run a command liked: curl -X POST -u jerry:pw http://192.168.1.8/inbound.cgi When I use printenv in the cgi I do not see the user and password anywhere. Isn't it supposed to be there in an environment variable like REMOTE_USER ? How do I receive the basic authentication ? Thanks, Jerry ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] CentOS 6 / Intel CPU support
https://access.redhat.com/support/policy/intel shows mainly Xeon CPUs. What about Intel Core i7-6700 Quad-Core Skylake has the current EL6 variant support for it? Any experience? Feedback would be greatly appreciated. Thanks, LF ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 / Intel CPU support
> Am 11.05.2017 um 14:48 schrieb Leon Fauster :
>
> https://access.redhat.com/support/policy/intel
>
> shows mainly Xeon CPUs. What about
>
> Intel Core i7-6700 Quad-Core Skylake
>
> has the current EL6 variant support for it?
>
> Any experience? Feedback would be greatly appreciated.
I found this
linux-2.6.32-696.1.1.el6/arch/x86/kernel/setup.c
796 if ((boot_cpu_data.x86_vendor == X86_VENDOR_INTEL) &&
797 ((boot_cpu_data.x86 == 6))) {
798 switch (boot_cpu_data.x86_model) {
799 case 94: /* Skylake-S */
800 case 86: /* Broadwell-DE SoC */
801 case 85: /* Purley */
802 case 79: /* Broadwell-EP and EX */
803 case 78: /* Skylake-Y */
804 case 77: /* Atom Avoton */
805 case 71: /* Broadwell-H */
806 case 70: /* Crystal Well */
807 break;
808 default:
809 if (boot_cpu_data.x86_model > 63) {
810 printk(KERN_CRIT
811"Detected CPU family %d model %d\n",
812boot_cpu_data.x86,
813boot_cpu_data.x86_model);
814 mark_hardware_unsupported("Intel CPU model");
815 }
816 break;
817 }
818 }
not sure if "case 94: /* Skylake-S */" means support for Intel Core i7-6700
Quad-Core Skylake ...
--
LF
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 / Intel CPU support
> Am 11.05.2017 um 16:29 schrieb Leon Fauster :
>
>> Am 11.05.2017 um 14:48 schrieb Leon Fauster :
>>
>> https://access.redhat.com/support/policy/intel
>>
>> shows mainly Xeon CPUs. What about
>>
>> Intel Core i7-6700 Quad-Core Skylake
>>
>> has the current EL6 variant support for it?
>>
>> Any experience? Feedback would be greatly appreciated.
>
>
> I found this
>
> linux-2.6.32-696.1.1.el6/arch/x86/kernel/setup.c
>
> 796 if ((boot_cpu_data.x86_vendor == X86_VENDOR_INTEL) &&
> 797 ((boot_cpu_data.x86 == 6))) {
> 798 switch (boot_cpu_data.x86_model) {
> 799 case 94: /* Skylake-S */
> 800 case 86: /* Broadwell-DE SoC */
> 801 case 85: /* Purley */
> 802 case 79: /* Broadwell-EP and EX */
> 803 case 78: /* Skylake-Y */
> 804 case 77: /* Atom Avoton */
> 805 case 71: /* Broadwell-H */
> 806 case 70: /* Crystal Well */
> 807 break;
> 808 default:
> 809 if (boot_cpu_data.x86_model > 63) {
> 810 printk(KERN_CRIT
> 811"Detected CPU family %d model %d\n",
> 812boot_cpu_data.x86,
> 813boot_cpu_data.x86_model);
> 814 mark_hardware_unsupported("Intel CPU model");
> 815 }
> 816 break;
> 817 }
> 818 }
>
> not sure if "case 94: /* Skylake-S */" means support for Intel Core i7-6700
> Quad-Core Skylake ...
for the record:
model 94 seems to be supported since EL6.7.
A quick install could be booted without issues.
# cat /proc/cpuinfo | head -26 ; uname -a
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 94
model name : Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
stepping: 3
microcode : 85
cpu MHz : 3408.025
cache size : 8192 KB
physical id : 0
siblings: 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16
xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave
avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb xsaveopt pln pts dtherm
hwp hwp_noitfy hwp_act_window hwp_epp tpr_shadow vnmi flexpriority ept vpid
fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx
bogomips: 6816.05
clflush size: 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:
Linux srv-s01.ccds.de 2.6.32-696.1.1.el6.x86_64 #1 SMP Tue Apr 11 17:13:24 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
--
LF
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Basic authentication - maybe off topoc
On Thu, May 11, 2017 at 07:56:00AM -0400, Jerry Geis wrote: > Hi - I am using CentOS 7.3 and trying to receive basic authentication. > > I run a command liked: curl -X POST -u jerry:pw > http://192.168.1.8/inbound.cgi > > When I use printenv in the cgi I do not see the user and password anywhere. > Isn't it supposed to be there in an environment variable like REMOTE_USER ? Is this a 'curl' question, a 'How do you write CGI?' question or a general question about how HTTP works? -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] strange system outage
On Wed, May 10, 2017 at 3:19 PM, Larry Martell wrote: > On Wed, May 10, 2017 at 3:07 PM, Jonathan Billings > wrote: >> On Wed, May 10, 2017 at 02:40:04PM -0400, Larry Martell wrote: >>> I have a CentOS 7 system that I run a home grown python daemon on. I >>> run this same daemon on many other systems without any incident. On >>> this one system the daemon seems to die or be killed every day around >>> 3:30am. There is nothing it its log or any system logs that tell me >>> why it dies. However in /var/log/messages every day I see something >>> like this: >> >> How are you starting this daemon? > > I am using code something like this: https://gist.github.com/slor/5946334. > >> Can you check the journal? Perhaps >> you'll see more useful information than what you see in the syslogs? > > Thanks, I will do that. Thank you for that suggestion. I was able to get someone to run journalctl and send me the output and it was very interesting. First, there is logging going on continuously during the time when logging stops in /var/log/messages. Second, I see messages like this periodically: May 10 03:57:46 localhost.localdomain python[40222]: detected unhandled Python exception in '/usr/local/motor/motor/core/data/importer.py' May 10 03:57:46 localhost.localdomain abrt-server[40277]: Only 0MiB is available on /var/spool/abrt May 10 03:57:46 localhost.localdomain python[40222]: error sending data to ABRT daemon: This happens at various times of the day, and I do not think is related to the daemon crashing. But I did see one occurrence of this: May 09 03:49:35 localhost.localdomain python[14042]: detected unhandled Python exception in '/usr/local/motor/motor/core/data/importerd.py' May 09 03:49:35 localhost.localdomain abrt-server[22714]: Only 0MiB is available on /var/spool/abrt May 09 03:49:35 localhost.localdomain python[14042]: error sending data to ABRT daemon: And that is the daemon. But I only see that on this one day, and it crashes every day. And I see this type of message frequently throughout the day, every day: May 09 03:40:01 localhost.localdomain CROND[21447]: (motor) CMD (python /usr/local/motor/motor/scripts/image_mover.py -v1 -d /usr/local/motor/data > ~/last_image_move_log.txt) May 09 03:40:01 localhost.localdomain abrt-server[21453]: Only 0MiB is available on /var/spool/abrt May 09 03:40:01 localhost.localdomain python[21402]: error sending data to ABRT daemon: May 09 03:40:01 localhost.localdomain postfix/postdrop[21456]: warning: uid=0: No space left on device May 09 03:40:01 localhost.localdomain postfix/sendmail[21455]: fatal: root(0): queue file write error May 09 03:40:01 localhost.localdomain crond[2630]: postdrop: warning: uid=0: No space left on device May 09 03:40:01 localhost.localdomain crond[2630]: sendmail: fatal: root(0): queue file write error May 09 03:40:01 localhost.localdomain CROND[21443]: (root) MAIL (mailed 67 bytes of output but got status 0x004b) So it seems there is a space issue. And finally, coinciding with the time that the logging resumes in /var/log/messages I see this every day at that time: May 10 03:57:57 localhost.localdomain run-parts(/etc/cron.daily)[40293]: finished mlocate May 10 03:57:57 localhost.localdomain anacron[33406]: Job `cron.daily' terminated (mailing output) May 10 03:57:57 localhost.localdomain anacron[33406]: Normal exit (1 job run) I need to get my remote hands to get me more info. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Basic authentication - maybe off topoc
>Is this a 'curl' question, a 'How do you write CGI?' question or a >general question about how HTTP works? Hi Jonathan, This was just a general question on why I'm not seeing what I expected. I'm using CentOS 7.3, I have written CGI for years (not using user & pass), I've used http for years - I was just hoping someone might be able to shed some light on why I'm not seeing the REMOTE_USER. I did several searches and did not find any resolution. Thanks for any pointers. Jerry ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Basic authentication - maybe off topoc
> Date: Thursday, May 11, 2017 14:53:28 -0400 > From: Jerry Geis > >> Is this a 'curl' question, a 'How do you write CGI?' question or a >> general question about how HTTP works? > > Hi Jonathan, > > This was just a general question on why I'm not seeing what I > expected. I'm using CentOS 7.3, I have written CGI for years (not > using user & pass), I've used http for years - I was just hoping > someone might be able to shed some light on why I'm not seeing > the REMOTE_USER. I did several searches and did not find any > resolution. > I can't tell from your description if this might be the issue, but you will only see the REMOTE_USER value if the resource being requested requires basic authentication. You don't see it, even if passed, on pages where authentication isn't required. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 / Intel CPU support
On 05/11/2017 12:45 PM, Leon Fauster wrote:
Am 11.05.2017 um 16:29 schrieb Leon Fauster :
Am 11.05.2017 um 14:48 schrieb Leon Fauster :
https://access.redhat.com/support/policy/intel
shows mainly Xeon CPUs. What about
Intel Core i7-6700 Quad-Core Skylake
has the current EL6 variant support for it?
Any experience? Feedback would be greatly appreciated.
I found this
linux-2.6.32-696.1.1.el6/arch/x86/kernel/setup.c
796 if ((boot_cpu_data.x86_vendor == X86_VENDOR_INTEL) &&
797 ((boot_cpu_data.x86 == 6))) {
798 switch (boot_cpu_data.x86_model) {
799 case 94: /* Skylake-S */
800 case 86: /* Broadwell-DE SoC */
801 case 85: /* Purley */
802 case 79: /* Broadwell-EP and EX */
803 case 78: /* Skylake-Y */
804 case 77: /* Atom Avoton */
805 case 71: /* Broadwell-H */
806 case 70: /* Crystal Well */
807 break;
808 default:
809 if (boot_cpu_data.x86_model > 63) {
810 printk(KERN_CRIT
811"Detected CPU family %d model %d\n",
812boot_cpu_data.x86,
813boot_cpu_data.x86_model);
814 mark_hardware_unsupported("Intel CPU model");
815 }
816 break;
817 }
818 }
not sure if "case 94: /* Skylake-S */" means support for Intel Core i7-6700
Quad-Core Skylake ...
for the record:
model 94 seems to be supported since EL6.7.
A quick install could be booted without issues.
# cat /proc/cpuinfo | head -26 ; uname -a
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 94
model name : Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
stepping: 3
microcode : 85
cpu MHz : 3408.025
cache size : 8192 KB
physical id : 0
siblings: 8
core id : 0
cpu cores : 4
apicid : 0
initial apicid : 0
fpu : yes
fpu_exception : yes
cpuid level : 22
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb
rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology nonstop_tsc
aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 fma cx16
xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave
avx f16c rdrand lahf_lm abm 3dnowprefetch ida arat epb xsaveopt pln pts dtherm
hwp hwp_noitfy hwp_act_window hwp_epp tpr_shadow vnmi flexpriority ept vpid
fsgsbase bmi1 hle avx2 smep bmi2 erms invpcid rtm rdseed adx
bogomips: 6816.05
clflush size: 64
cache_alignment : 64
address sizes : 39 bits physical, 48 bits virtual
power management:
Linux srv-s01.ccds.de 2.6.32-696.1.1.el6.x86_64 #1 SMP Tue Apr 11 17:13:24 UTC
2017 x86_64 x86_64 x86_64 GNU/Linux
--
LF
Here's mine. Interesting differences:
# cat /proc/cpuinfo | head -26; uname -a
processor: 0
vendor_id: GenuineIntel
cpu family: 6
model: 94
model name: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
stepping: 3
microcode: 0x9e
cpu MHz: 899.945
cache size: 6144 KB
physical id: 0
siblings: 8
core id: 0
cpu cores: 4
apicid: 0
initial apicid: 0
fpu: yes
fpu_exception: yes
cpuid level: 22
wp: yes
flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall
nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good
nopl xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64
monitor ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2
x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm
abm 3dnowprefetch ida arat epb pln pts dtherm hwp hwp_noitfy
hwp_act_window hwp_epp intel_pt tpr_shadow vnmi flexpriority ept vpid
fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed
adx smap clflushopt xsaveopt xsavec xgetbv1
bogomips: 5184.00
clflush size: 64
cache_alignment: 64
address sizes: 39 bits physical, 48 bits virtual
power management:
Linux null.example.com 3.10.0-514.16.1.el7.x86_64 #1 SMP Wed Apr 12
15:04:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos
[CentOS] TLSv1.3 support?
Hello, will the next update of CentOS 6 (6.10) have TLSv1.3 support? Thanks, Walter ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] TLSv1.3 support?
On 5/11/2017 1:13 PM, Walter H. wrote: will the next update of CentOS 6 (6.10) have TLSv1.3 support? A) Ask Red Hat, I see no date for RHEL 6 update 10 yet. update 9 released 6 or 8 weeks ago, so its likely 3-4 months before update 10 releases. B) afaik, TLS v1.3 hasn't even been ratified yet, its still a draft C) openssl v.1.1.1 which is supposed to support TLS v1.3(draft) isn't finished yet, either, its still a -dev release. -- john r pierce, recycling bits in santa cruz ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] get pdftk into (or from) a repo
pdftk used to be in a repo... or maybe it still is, but I don't know which one. Anyone know? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] TLSv1.3 support?
On 5/11/2017 1:23 PM, John R Pierce wrote: On 5/11/2017 1:13 PM, Walter H. wrote: will the next update of CentOS 6 (6.10) have TLSv1.3 support? A) Ask Red Hat, I see no date for RHEL 6 update 10 yet. update 9 released 6 or 8 weeks ago, so its likely 3-4 months before update 10 releases. B) afaik, TLS v1.3 hasn't even been ratified yet, its still a draft C) openssl v.1.1.1 which is supposed to support TLS v1.3(draft) isn't finished yet, either, its still a -dev release. D) RHEL 6 is, as of yesterday, in "production 3" [*], where only critical fixes and serious security exposures will be fixed.I see this as pretty unlikely they'd upgrade openssl [*] https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/6.9_Release_Notes/chap-Red_Hat_Enterprise_Linux-6.9_Release_Notes-Overview.html -- john r pierce, recycling bits in santa cruz ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 6 / Intel CPU support
> Here's mine. Interesting differences:
If you disable Intel Speedstep in the BIOS it should lock the CPU to its
fastest speed, but you lose power saving during idle.
On Thu, May 11, 2017 at 3:48 PM, ken wrote:
> On 05/11/2017 12:45 PM, Leon Fauster wrote:
>
>> Am 11.05.2017 um 16:29 schrieb Leon Fauster :
>>>
>>> Am 11.05.2017 um 14:48 schrieb Leon Fauster >>> >:
https://access.redhat.com/support/policy/intel
shows mainly Xeon CPUs. What about
Intel Core i7-6700 Quad-Core Skylake
has the current EL6 variant support for it?
Any experience? Feedback would be greatly appreciated.
>>>
>>> I found this
>>>
>>> linux-2.6.32-696.1.1.el6/arch/x86/kernel/setup.c
>>>
>>> 796 if ((boot_cpu_data.x86_vendor == X86_VENDOR_INTEL) &&
>>> 797 ((boot_cpu_data.x86 == 6))) {
>>> 798 switch (boot_cpu_data.x86_model) {
>>> 799 case 94: /* Skylake-S */
>>> 800 case 86: /* Broadwell-DE SoC */
>>> 801 case 85: /* Purley */
>>> 802 case 79: /* Broadwell-EP and EX */
>>> 803 case 78: /* Skylake-Y */
>>> 804 case 77: /* Atom Avoton */
>>> 805 case 71: /* Broadwell-H */
>>> 806 case 70: /* Crystal Well */
>>> 807 break;
>>> 808 default:
>>> 809 if (boot_cpu_data.x86_model > 63) {
>>> 810 printk(KERN_CRIT
>>> 811"Detected CPU family %d model %d\n",
>>> 812boot_cpu_data.x86,
>>> 813boot_cpu_data.x86_model);
>>> 814 mark_hardware_unsupported("Intel CPU model");
>>> 815 }
>>> 816 break;
>>> 817 }
>>> 818 }
>>>
>>> not sure if "case 94: /* Skylake-S */" means support for Intel Core
>>> i7-6700 Quad-Core Skylake ...
>>>
>>
>> for the record:
>>
>> model 94 seems to be supported since EL6.7.
>>
>> A quick install could be booted without issues.
>>
>>
>> # cat /proc/cpuinfo | head -26 ; uname -a
>> processor : 0
>> vendor_id : GenuineIntel
>> cpu family : 6
>> model : 94
>> model name : Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
>> stepping: 3
>> microcode : 85
>> cpu MHz : 3408.025
>> cache size : 8192 KB
>> physical id : 0
>> siblings: 8
>> core id : 0
>> cpu cores : 4
>> apicid : 0
>> initial apicid : 0
>> fpu : yes
>> fpu_exception : yes
>> cpuid level : 22
>> wp : yes
>> flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge
>> mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall
>> nx pdpe1gb rdtscp lm constant_tsc arch_perfmon pebs bts rep_good xtopology
>> nonstop_tsc aperfmperf pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2
>> ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt
>> tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch ida
>> arat epb xsaveopt pln pts dtherm hwp hwp_noitfy hwp_act_window hwp_epp
>> tpr_shadow vnmi flexpriority ept vpid fsgsbase bmi1 hle avx2 smep bmi2 erms
>> invpcid rtm rdseed adx
>> bogomips: 6816.05
>> clflush size: 64
>> cache_alignment : 64
>> address sizes : 39 bits physical, 48 bits virtual
>> power management:
>>
>> Linux srv-s01.ccds.de 2.6.32-696.1.1.el6.x86_64 #1 SMP Tue Apr 11
>> 17:13:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
>>
>> --
>> LF
>>
>
> Here's mine. Interesting differences:
>
> # cat /proc/cpuinfo | head -26; uname -a
> processor: 0
> vendor_id: GenuineIntel
> cpu family: 6
> model: 94
> model name: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
> stepping: 3
> microcode: 0x9e
> cpu MHz: 899.945
> cache size: 6144 KB
> physical id: 0
> siblings: 8
> core id: 0
> cpu cores: 4
> apicid: 0
> initial apicid: 0
> fpu: yes
> fpu_exception: yes
> cpuid level: 22
> wp: yes
> flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca
> cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx
> pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl
> xtopology nonstop_tsc aperfmperf eagerfpu pni pclmulqdq dtes64 monitor
> ds_cpl vmx est tm2 ssse3 fma cx16 xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe
> popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm
> 3dnowprefetch ida arat epb pln pts dtherm hwp hwp_noitfy hwp_act_window
> hwp_epp intel_pt tpr_shadow vnmi flexpriority ept vpid fsgsbase tsc_adjust
> bmi1 hle avx2 smep bmi2 erms invpcid rtm mpx rdseed adx smap clflushopt
> xsaveopt xsavec xgetbv1
> bogomips: 5184.00
> clflush size: 64
> cache_alignment: 64
> address sizes: 39 bits physical, 48 bits virtual
> power management:
>
> Linux null.example.com 3.10.0-514.16.1.el7.x86_64 #1 SMP Wed Apr 12
> 15:04:24 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
>
>
> ___
> Cent
Re: [CentOS] Thunderbird Regression
Maybe this is not very helpful to you, but I run Thunderbird 52 on CentOS 7, and it is as good as always. I'm not using RAID on home directory. Yan > On May 10, 2017, at 8:16 PM, Mark LaPierre wrote: > > Has anyone else noticed a 10X slowing of the time it takes Thunderbird > to load an email that contains graphics on CentOS 6? The last > Thunderbird update moved us from Thunderbird 45 to Thunderbird 52. > > While Thunderbird was loading the images the hard drive was busy > cranking out seeks. I have all my local home accounts mounted on a > software raid. > > I solved the problem with a downgrade to Thunderbird 45, but that's a > poor solution not keeping Thunderbird up to date with the latest > security patches. > > -- >_ > °v° > /(_)\ > ^ ^ Mark LaPierre > Registered Linux user No #267004 > https://linuxcounter.net/ > > ___ > CentOS mailing list > CentOS@centos.org > https://lists.centos.org/mailman/listinfo/centos ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 speedstep CPU support
On 05/11/2017 05:38 PM, Darr247 wrote: Here's mine. Interesting differences: If you disable Intel Speedstep in the BIOS it should lock the CPU to its fastest speed, but you lose power saving during idle. Thanks for the suggestion. I still recall that in CentOS 5.x there was speedstep control available from gnome... and from the CLI too of course. I don't see it in C7.3. Currently I don't actually need more speed. This is already a fairly peppy laptop... like right now the load is about 2%. If it was any lower, I could almost turn this machine off and still run everything. :) Ah but seriously, I'd rather have the speed cranked down and save the battery. That's the one weak spot: this gal can drain a battery faster than a dog can down a bag of cookies. Still, I'd like to have control in gnome over cpu speed again. Thanks again. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] get pdftk into (or from) a repo
> Am 11.05.2017 um 22:26 schrieb ken : > > pdftk used to be in a repo... or maybe it still is, but I don't know which > one. Anyone know? > an old one is in the "dead" rpmforge repo. -- LF ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] get pdftk into (or from) a repo
On 05/11/2017 06:49 PM, Leon Fauster wrote: Am 11.05.2017 um 22:26 schrieb ken : pdftk used to be in a repo... or maybe it still is, but I don't know which one. Anyone know? an old one is in the "dead" rpmforge repo. At https://www.pdflabs.com/docs/install-pdftk-on-redhat-or-centos/ they have version 2.0 in rpm for RH/Cent5 & 6, but not 7, but there's also RH-friendly source code. So it wouldn't be too much head-scratching to get rpms on a repo. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] strange system outage
Am 11.05.2017 um 20:30 schrieb Larry Martell: On Wed, May 10, 2017 at 3:19 PM, Larry Martell wrote: On Wed, May 10, 2017 at 3:07 PM, Jonathan Billings wrote: On Wed, May 10, 2017 at 02:40:04PM -0400, Larry Martell wrote: I have a CentOS 7 system that I run a home grown python daemon on. I run this same daemon on many other systems without any incident. On this one system the daemon seems to die or be killed every day around 3:30am. There is nothing it its log or any system logs that tell me why it dies. However in /var/log/messages every day I see something like this: How are you starting this daemon? I am using code something like this: https://gist.github.com/slor/5946334. Can you check the journal? Perhaps you'll see more useful information than what you see in the syslogs? Thanks, I will do that. Thank you for that suggestion. I was able to get someone to run journalctl and send me the output and it was very interesting. First, there is logging going on continuously during the time when logging stops in /var/log/messages. Second, I see messages like this periodically: May 10 03:57:46 localhost.localdomain python[40222]: detected unhandled Python exception in '/usr/local/motor/motor/core/data/importer.py' May 10 03:57:46 localhost.localdomain abrt-server[40277]: Only 0MiB is available on /var/spool/abrt May 10 03:57:46 localhost.localdomain python[40222]: error sending data to ABRT daemon: This happens at various times of the day, and I do not think is related to the daemon crashing. But I did see one occurrence of this: May 09 03:49:35 localhost.localdomain python[14042]: detected unhandled Python exception in '/usr/local/motor/motor/core/data/importerd.py' May 09 03:49:35 localhost.localdomain abrt-server[22714]: Only 0MiB is available on /var/spool/abrt May 09 03:49:35 localhost.localdomain python[14042]: error sending data to ABRT daemon: And that is the daemon. But I only see that on this one day, and it crashes every day. And I see this type of message frequently throughout the day, every day: May 09 03:40:01 localhost.localdomain CROND[21447]: (motor) CMD (python /usr/local/motor/motor/scripts/image_mover.py -v1 -d /usr/local/motor/data > ~/last_image_move_log.txt) May 09 03:40:01 localhost.localdomain abrt-server[21453]: Only 0MiB is available on /var/spool/abrt May 09 03:40:01 localhost.localdomain python[21402]: error sending data to ABRT daemon: May 09 03:40:01 localhost.localdomain postfix/postdrop[21456]: warning: uid=0: No space left on device May 09 03:40:01 localhost.localdomain postfix/sendmail[21455]: fatal: root(0): queue file write error May 09 03:40:01 localhost.localdomain crond[2630]: postdrop: warning: uid=0: No space left on device May 09 03:40:01 localhost.localdomain crond[2630]: sendmail: fatal: root(0): queue file write error May 09 03:40:01 localhost.localdomain CROND[21443]: (root) MAIL (mailed 67 bytes of output but got status 0x004b) So it seems there is a space issue. And finally, coinciding with the time that the logging resumes in /var/log/messages I see this every day at that time: May 10 03:57:57 localhost.localdomain run-parts(/etc/cron.daily)[40293]: finished mlocate May 10 03:57:57 localhost.localdomain anacron[33406]: Job `cron.daily' terminated (mailing output) May 10 03:57:57 localhost.localdomain anacron[33406]: Normal exit (1 job run) I need to get my remote hands to get me more info. df -hT; df -i There is no space left on a vital partition / logical volume. "Only 0MiB is available on /var/spool/abrt" "postdrop: warning: uid=0: No space left on device" Alexander ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] CentOS 7 speedstep CPU support
On Fri, May 12, 2017 at 8:18 AM, ken wrote: > Currently I don't actually need more speed. This is already a fairly peppy > laptop... like right now the load is about 2%. If it was any lower, I could > almost turn this machine off and still run everything. :) Ah but > seriously, I'd rather have the speed cranked down and save the battery. > That's the one weak spot: this gal can drain a battery faster than a dog can > down a bag of cookies. Still, I'd like to have control in gnome over cpu > speed again. I think all that stuff is controlled by 'tuned' now. There is gtk app tuned-gtk to help setting and switching profiles. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] get pdftk into (or from) a repo
On 05/11/2017 07:07 PM, ken wrote: On 05/11/2017 06:49 PM, Leon Fauster wrote: Am 11.05.2017 um 22:26 schrieb ken : pdftk used to be in a repo... or maybe it still is, but I don't know which one. Anyone know? an old one is in the "dead" rpmforge repo. At https://www.pdflabs.com/docs/install-pdftk-on-redhat-or-centos/ they have version 2.0 in rpm for RH/Cent5 & 6, but not 7, but there's also RH-friendly source code. So it wouldn't be too much head-scratching to get rpms on a repo. It's worth mentioning that this is a really nice utility for manipulating PDFs, taking them apart, rearranging them, putting pages together, and a whole lot more. I've used it hundreds of times. Probably anyone who has to work with PDFs would have need of it. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
