[CentOS] Latest AMD CPUs and AM4 Motherboards

[Eugene Poole]

Has anyone used the new AMD CPUs and AM4 motherboards with CentOS 6 / 7?

Any reservations or warnings?

--
Eugene Poole
Woodstock, Georgia

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] how to use intel-gpu-tools

[DR MW BAFFICO]

To "ken" and "hth" whomever you may have been.

>From the moderator and owner of CENTOS7, et all, in sum and in short:
- this is an improperly formatted question, first
- next, we see that CENTOS7 does NOT and will NOT support anything INTEL now
or
  ever.
- With that said, you should be aware that backdooring through the use of
'rpm', 
  'kel', 'kik', 'deb', 'lost', 'ectect' and etcetera, are and will not be
allowed.  One reason why your
  "licenses" to evaluate YOU as a potential candidate for leaning to use the
actual
  CENTOS7 has been flatly rejected.  5 seconds to critical systems failue.
Cheers!

As for anyone who wishes to dispute this, you can go fuck yourselves.

EOL.

DR MW BAFFICO, MDx, PHDx
OWNER: CENTOS7, CENTAURI 7  --->EOL   as in, END OF LINE; MOTHERFUCKER.



---
DR MW BAFFICO, MDx, PHDx
CEO
[N|A|S] North American Science
p: 718-342-3227
f: 718-342-3227
e: {classified for introductory listserv}
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos




-Original Message-
From: CentOS [mailto:centos-boun...@centos.org] On Behalf Of ken
Sent: Saturday, May 6, 2017 9:10 AM
To: CentOS mailing list 
Subject: Re: [CentOS] how to use intel-gpu-tools

On 05/06/2017 04:37 AM, qw wrote:
> Hi,
>
>
> I use ffmpeg with Intel QSV to transcode some sample clips. And I want to
monitor Intel GPU usage. I found intel-gpu-tools in centos 7.
>
>
> Can intel-gpu-tools monitor Intel GPU usage? how to use it?
>
>
> Thanks!
>
>
> Regards
>
>
> Andrew

Andrew,

intel-gpu-tools is a set of different tools, also the name of the package.
To list the executable utilities in that package, do "rpm -ql
intel-gpu-tools".  This same listing will also show a manpage for each one,
along with documentation under /usr/share/gtk-doc/html/intel-gpu-tools/.

I don't know what sort of gpu monitoring you want to do, but you might also
want to look into "vmstat" and "gkrellm"... also in the /proc filesystem.

hth

___
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

[CentOS] Squirrelmail/PHP issue

[Jay Hart]

Been using Centos and Squirrelmail since early in Centos 6 cycle.  IIRC, I used 
to be able to
attach more than 4 pictures to an email.  Now I can't, four seems to be the 
limit.  Picture file
size doesn't seem to matter, they can be 50k or 5 meg each. I upped the limits 
in php.ini for the
following parameters to see if this would have any bearing on the issue:

post_max_size = 20M
upload_max_filesize = 15M

The way I see this is that I should be able to attach [more than] four pics of 
say, size 100K, to
an email.  I can't.  Within Squirrelmail I go to 'Compose', put in a recipient, 
subject title, and
in the body of text lets just say I add "test case" (as an example).  Then I go 
to 'browse',
select a [pic] file, click 'add' (which attaches the pic to the email), and 
repeat this for a
total of four files. When I try to attach the fifth pic, the 'email' frame goes 
blank, nothing
shown. To recover the text I can select 'Compose' again and squirrelamil will 
state I have an
email in 'draft' and do I want to open it. If I click 'ok' I get my email back 
minus all attached
pics.  Cycle repeats itself if I try to attach pic #5.

I've googled the web looking to see if others have had this issue, and a buddy 
helped me a bit,
but nothing definite shown to resolve.  I've got to figure its a PHP issue. I'm 
currently patched
to Centos 6.9.

Any help appreciated as to what to look for...

J






___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] systemd missing something?

[James Hogarth]

On 7 May 2017 at 16:30, Gordon Messmer  wrote:
> On 05/07/2017 07:22 AM, ken wrote:
>>
>> "Note that traditional init scripts continue to function on a systemd
>> system. An init script /etc/rc.d/init.d/foobar is implicitly mapped
>> into a service unit foobar.service during system initialization."
>> ...
>> However, what it implies doesn't seem to work out.
>
>
> It does not imply what you infer, because it explicitly says that the file
> in init.d is mapped to a systemd service unit.  The files in rc.d are not
> used, because systemd does not boot to runlevel 2, 3, 4, or 5.
>
> If you want "network" to start on boot, you would use "systemctl enable
> network".  (You would also want to "systemctl disable NetworkManager")
>

The two do not conflict and there is no need to to disable one to use the other.

In fact you shoudl leave network enabled when using NetworkManager or
you will get some odd behaviours, like missing loopback.

If you do 'nmcli d' to list devices you'll see that loopback is
unmanaged, ie it's handled by the network service.
___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] systemd missing something?

[Gordon Messmer]

On 05/07/2017 07:22 AM, ken wrote:

"Note that traditional init scripts continue to function on a systemd
system. An init script /etc/rc.d/init.d/foobar is implicitly mapped
into a service unit foobar.service during system initialization."
...
However, what it implies doesn't seem to work out. 


It does not imply what you infer, because it explicitly says that the 
file in init.d is mapped to a systemd service unit.  The files in rc.d 
are not used, because systemd does not boot to runlevel 2, 3, 4, or 5.


If you want "network" to start on boot, you would use "systemctl enable 
network".  (You would also want to "systemctl disable NetworkManager")

___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

Re: [CentOS] systemd missing something?

[Alexander Dalloz]

Am 07.05.2017 um 16:22 schrieb ken:

"Note that traditional init scripts continue to function on a systemd
system. An init script /etc/rc.d/init.d/foobar is implicitly mapped
into a service unit foobar.service during system initialization."

That's what it says in /etc/init.d/README.

However, what it implies doesn't seem to work out.

In the same directory as that README is a file called "network" which is 
symlinked into the various /etc/rc.d/rc?.d/ directories, i.e.:


# ls -l $(find /etc/rc.d/ -name S*network)
lrwxrwxrwx. 1 root root 17 Jan 26 15:23 /etc/rc.d/rc2.d/S56network -> 
../init.d/network
lrwxrwxrwx. 1 root root 17 Jan 26 15:23 /etc/rc.d/rc3.d/S56network -> 
../init.d/network
lrwxrwxrwx. 1 root root 17 Jan 26 15:23 /etc/rc.d/rc4.d/S56network -> 
../init.d/network
lrwxrwxrwx. 1 root root 17 Jan 26 15:22 /etc/rc.d/rc5.d/S56network -> 
../init.d/network


But "network" isn't executed on boot. However, it does work when I run 
this:


# /etc/init.d/network restart

So is this a bug, or is there something else that needs to be done?


CentOS 7 uses by default NetworkManager, thus the network service is 
disabled because both conflict.


Alexander


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos

[CentOS] systemd missing something?

[ken]

"Note that traditional init scripts continue to function on a systemd
system. An init script /etc/rc.d/init.d/foobar is implicitly mapped
into a service unit foobar.service during system initialization."

That's what it says in /etc/init.d/README.

However, what it implies doesn't seem to work out.

In the same directory as that README is a file called "network" which is 
symlinked into the various /etc/rc.d/rc?.d/ directories, i.e.:


# ls -l $(find /etc/rc.d/ -name S*network)
lrwxrwxrwx. 1 root root 17 Jan 26 15:23 /etc/rc.d/rc2.d/S56network -> 
../init.d/network
lrwxrwxrwx. 1 root root 17 Jan 26 15:23 /etc/rc.d/rc3.d/S56network -> 
../init.d/network
lrwxrwxrwx. 1 root root 17 Jan 26 15:23 /etc/rc.d/rc4.d/S56network -> 
../init.d/network
lrwxrwxrwx. 1 root root 17 Jan 26 15:22 /etc/rc.d/rc5.d/S56network -> 
../init.d/network


But "network" isn't executed on boot. However, it does work when I run this:

# /etc/init.d/network restart

So is this a bug, or is there something else that needs to be done?


___
CentOS mailing list
CentOS@centos.org
https://lists.centos.org/mailman/listinfo/centos