[CentOS] SCLO php70 imap missing
I am installing php70 on a machine running CentOS 7 for a particular reason and needed sclo-php70-php-imap which I believe is the imap module for php70 from SCL. It, however, does not seem to be available even though https://cbs.centos.org/koji/buildinfo?buildID=24734 suggests it should be. Am I missing something? ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] smba shares are unreachable once or twice per month
Have you checked this one: https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Domain_Member Maybe you missed something. Best Regards,Strahil Nikolov On Tue, Feb 9, 2021 at 7:21, Prengel, Ralf wrote: Hallo, I ve a problem with my samba-server. We are using a centos 7.7 with an samba exporting samba-shares. Logins are managed by our Windows-AD. The samba server has only the function to exports hares. Windows clients are Win10 patched every month. Our problem: Once or twice a month shares aren't akctive any longer and reachable for the Window-Clients. Network can nor be a reason because the same directory exported via NFS is reachable for all Linux-NFS-Client. Normally we disconect and connect the Samba server in the AD and after a reboot the shares are working again but that cant be the solution ;-) Can anyone give me hints hwo to anaylse and solving the problem. Thanks Ralf ___ 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] Resizing a QEMU guest display
Have you restarted the service ?Yesterday I built a CentOS 7 system and spice didn't resize untill I restarted the service. Best Regards,Strahil Nikolov On Mon, Feb 8, 2021 at 14:40, Bill Gee wrote: Hi Strahil - Thanks for the link. Unfortunately it is not helpful. The spice agent is already installed on the guest, and the spice channel is already configured. [bgee@practice21a ~]$ rpm -qa | grep spice spice-vdagent-0.20.0-3.fc33.x86_64 A question occurs to me ... The working guest also has both the spice-vdagent package and the spice channel. Why does it work and the other guest does not? -- Bill Gee On Monday, February 8, 2021 2:12:39 AM CST Strahil Nikolov wrote: > I think the following is a good start: > 11.3. SPICE Agent Red Hat Enterprise Linux 7 | Red Hat Customer Portal > | > | > | > | | | > > | > > | > | > | | > 11.3. SPICE Agent Red Hat Enterprise Linux 7 | Red Hat Customer Portal > > The Red Hat Customer Portal delivers the knowledge, expertise, and guidance > available through your Red Hat subscription. > | | > > | > > | > > > Best Regards,Strahil Nikolov > > > On Sun, Feb 7, 2021 at 20:29, Bill Gee wrote: Hi >Strahil - > > How does one reach a guest via spice? I am not familiar with any remote > access application called "spice". I have tried two methods of accessing the > host. First is to open it from the Virtual Machine Manager on the host. > Second is to use TigerVNC to access it across the local network. > > I see a package installed on the guest which looks like the guest agent. Is > there more that needs to be added? This is the only qemu package installed > on both the Fedora machine that does not resize and the CentOS7 machine that > will resize. The versions are way different between the two guests. > > [root@practice21a ~]# rpm -qa | grep qemu > qemu-guest-agent-5.1.0-9.fc33.x86_64 > > The Fedora guest has, as you see, version 5.1.0-9. The CentOS7 guest has > version 2.12.0-3. Perhaps the Fedora guest version is too new to run on a > CentOS7 host?? > > I see other QEMU packages available. One of them is called > "qemu-device-display-qxl" which is very suggestive. However, that package is > NOT installed on the CentOS7 guest and yet that guest works. > > Another package I see is "libvirt-daemon-driver-qemu". This package is > installed on the host but is not present on either guest. Is it needed on > guests? > > > Have you tried to reach the VM via spice ?Also check if qemu's guest agent > > is runningin the VM. > > > > Best Regards,Strahil Nikolov > > ___ > 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 mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] el7 systemd service:: ensure var/log owner when User is specified
On Tue, Feb 09, 2021 at 07:21:40PM +0200, Adrian Sevcenco wrote: > Hi! Does anyone have an idea how can i (in a nice way [1]) to ensure > ownership/permissions of log directory in /var/log for a unit > that drops privileges to a user (with User=/Group=) > > [1] The ugly way being with script in StartPre and sudo in Start > so i want to use User= > I'm aware of LogsDirectory= but is not available on EL7 Running sudo in a systemd service seems like a bad idea and should be avoided. It'll require disabling the RequireTTY feature in the sudo configuration anyway. Newer versions of systemd support adding a + or ! at the beginning of the ExecStart= command to tell systemd to run with elevated privileges, so you could have: [Service] Type=oneshot User=testuser ExecStartPre=!mkdir -p /var/log/test ExecStartPre=!chown testuser /var/log/test ExecStart=/bin/sh -c 'date > /var/log/test/test.log' However, those features aren't introduced into systemd until ~v231 so it isn't in EL7. I think you will have to do something like: ExecStartPre=mkdir -p /var/log/test ExecStartPre=chown testuser /var/log/test ExecStart=su testuser -c 'date > /var/log/test/test.log' Just don't use sudo. -- Jonathan Billings ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
[CentOS] el7 systemd service:: ensure var/log owner when User is specified
Hi! Does anyone have an idea how can i (in a nice way [1]) to ensure ownership/permissions of log directory in /var/log for a unit that drops privileges to a user (with User=/Group=) [1] The ugly way being with script in StartPre and sudo in Start so i want to use User= I'm aware of LogsDirectory= but is not available on EL7 Thanks a lot! Adrian ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
Re: [CentOS-es] Resumen de CentOS-es, Vol 165, Envío 2
AlmaLinux puede ser una excelente opción... No obstante igual hay una empresa por detrás... Quizás puede resultar peligroso si optan por una determinación parecida a la actual... RockyLinux podría ser una distro de la comunidad. No obstante mientras tanto es una opción y si EPE la recomienda... pues haganle caso Saludos, David El lun, 8 feb 2021 a las 13:09, Ing. Ernesto Pérez Estévez, Mg. via CentOS-es () escribió: > El 8/2/21 a las 10:55, Javier Aquino escribió: > > Alternativas a CentOS: > Y alma Linux, que ya tiene el beta y seguro pronto sale la de producción > > https://www.youtube.com/watch?v=Ykx73UVGWbI > > > el otro día probamos actualizar a almalinux y fue super simple > > -- > CEDIA > La principal herramienta de Investigación en el Ecuador. > > Gonzalo Cordero 2-122 y J. Fajardo > Cuenca - Ecuador > Telf: +593 7 407 9300 Ext. 115 > i...@cedia.org.ec > www.cedia.edu.ec > ___ > CentOS-es mailing list > CentOS-es@centos.org > https://lists.centos.org/mailman/listinfo/centos-es > ___ CentOS-es mailing list CentOS-es@centos.org https://lists.centos.org/mailman/listinfo/centos-es
[CentOS-announce] CEBA-2021:0439 CentOS 7 glibc BugFix Update
CentOS Errata and Bugfix Advisory 2021:0439
Upstream details at : https://access.redhat.com/errata/RHBA-2021:0439
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
ee561a3f0dd8945edec3478e8426cc324bdf6fc5fe6a31d762cfae60d3e14830
glibc-2.17-323.el7_9.i686.rpm
b2b420ac2c03b3a2e4cadd073857498446180ec51a863fe30335c9da3a963fde
glibc-2.17-323.el7_9.x86_64.rpm
f48d75115ac638576d608849a173ace6a70c2430a2e0226487652befdf004b27
glibc-common-2.17-323.el7_9.x86_64.rpm
acbb0c34227bd9c7bba35cfa08b4942dd141ee4ccadd128d8acedaef5e31522c
glibc-devel-2.17-323.el7_9.i686.rpm
aab72ef4b89bc4481b87f7aaf225cbdefb62073dc7fc7c2b94ab11a0a936
glibc-devel-2.17-323.el7_9.x86_64.rpm
9ba71fe357dd09d1913b30b0bd83507588d8cb06eda6f2c15326f3f1384c6180
glibc-headers-2.17-323.el7_9.x86_64.rpm
eae7a2d2bc9f6058c113c27e6bdea6677a865df0f7924ed51165a2653c2d2175
glibc-static-2.17-323.el7_9.i686.rpm
49e01e923bc5d1026751341c9a01ab8ef4d50d8b17e94f179de33afcbfb0b234
glibc-static-2.17-323.el7_9.x86_64.rpm
cafdbebcda7664e47d81f647d715249983cbe0bb4b063c1d56ab327a8766e2d0
glibc-utils-2.17-323.el7_9.x86_64.rpm
27d1ba676d3d4007102e714f71f0f4e97d46890c6eed54e5f10720ff65e7cea8
nscd-2.17-323.el7_9.x86_64.rpm
Source:
cb68b648ffec5a38b0cef7e6a88fb2dfb6357c8f0a17cf0331376a3cdfd41d97
glibc-2.17-323.el7_9.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
[CentOS-announce] CESA-2021:0411 Important CentOS 7 flatpak Security Update
CentOS Errata and Security Advisory 2021:0411 Important
Upstream details at : https://access.redhat.com/errata/RHSA-2021:0411
The following updated files have been uploaded and are currently
syncing to the mirrors: ( sha256sum Filename )
x86_64:
0e230546571aa26c06f1097967584ab4b9e777e7ca6c94d45f8706a36bdccc22
flatpak-1.0.9-10.el7_9.x86_64.rpm
724795eec6065da1df593d22a6a359fc5b241aec5a3916cbec646ff78f2196ba
flatpak-builder-1.0.0-10.el7_9.x86_64.rpm
85ac0468355fd6847c79849e947fd3b5d88f606ad3aa6fd06cb4aca3fe3c9fc8
flatpak-devel-1.0.9-10.el7_9.x86_64.rpm
6a5560cf575ee9bfa9cac85044e94e3bce3ea85e26431c99e41877289cf82b64
flatpak-libs-1.0.9-10.el7_9.x86_64.rpm
Source:
170d39f61f08b19f0c202440b9ac801e8d5e80ec0240b8cd0f3a9d85a3c109d4
flatpak-1.0.9-10.el7_9.src.rpm
--
Johnny Hughes
CentOS Project { http://www.centos.org/ }
irc: hughesjr, #cen...@irc.freenode.net
Twitter: @JohnnyCentOS
___
CentOS-announce mailing list
CentOS-announce@centos.org
https://lists.centos.org/mailman/listinfo/centos-announce
Re: [CentOS] Recommendation for 10 gigabit NICs on CentOS8
I believe connectx2 work using the plus kernel, however look for a connectx 3 or 4 either native Ethernet (EN) or a VPI variant, these will be 40Gb and you can use a qsfp to sfp+ convertor, or 40Gb transceiver (auto negotiated to 10Gb). You can change the port profile using mellanox tools or editing the profile in /says. -- Lauz On 9 February 2021 01:45:26 GMT, Victor Padro wrote: >They work, had a NAS running SMB and NFS serving to a couple ESX for >backups using a dual port Connect-X. > >The ones that have their issues are mostly the VPI/IB models which need >to >be reflashed to the ethernet firmware, on servethehome's forums there's >plenty info about this. > >On Sun, Feb 7, 2021, 4:56 AM Strahil Nikolov via CentOS > >wrote: > >> Hi All, >> >> >> can you share what kind of old NICs do you use on CentOS 8 (Stream or >> not , it doesn't matter) without any issues? >> I was looking at ebay and I found some pretty old Mellanox >"ConnectX" >> or "ConnectX-2" but I seriously doubt they will work on CentOS 8. >> >> Any proposals are also welcome. I don't care of the brand as long as >it >> is PCIe and is supported by the vanilla kernel. >> >> Best Regards, >> Strahil Nikolov >> >> ___ >> 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 -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos
