Re: coredump.conf defaults?

On 8/23/19 4:25 PM, Ed Greshko wrote: On 8/24/19 6:42 AM, ToddAndMargo via users wrote: Hi All, /etc/systemd/coredump.conf   # Defaults can be restored by simply deleting this file.   [Coredump]   #Storage=external   #Compress=yes   #ProcessSizeMax=2G   #ExternalS

Re: coredump.conf defaults?

On 8/24/19 6:42 AM, ToddAndMargo via users wrote: > Hi All, > > /etc/systemd/coredump.conf > >   # Defaults can be restored by simply deleting this file. >   [Coredump] >   #Storage=external >   #Compress=yes >   #ProcessSizeMax=2G >   #ExternalSizeMax=2G >   #JournalSiz

Re: NFS mount fails -

On 23Aug2019 17:53, Bob Goodwin wrote: On 8/23/19 1:31 PM, Samuel Sieb wrote: Assuming you are trying to mount an external /home and the server is 192.168.2.128, the command on the client would be: mount 192.168.2.128:/home /home Also, you can check from the client what a server is prepared

coredump.conf defaults?

Hi All, /etc/systemd/coredump.conf # Defaults can be restored by simply deleting this file. [Coredump] #Storage=external #Compress=yes #ProcessSizeMax=2G #ExternalSizeMax=2G #JournalSizeMax=767M #MaxUse= #KeepFree= How to I figure out what t

Re: NFS mount fails -

On 8/23/19 1:31 PM, Samuel Sieb wrote: On 8/23/19 8:13 AM, Bob Goodwin wrote: [bobg@localhost-live ~]$ cat /etc/exports /home    192.168.2.0/24(rw,no_root_squash) but now I am wondering where is that "/home    " coming from? I didn't notice that before ... It has to be there.  That tells the

Re: NFS mount fails -

On 8/23/19 8:13 AM, Bob Goodwin wrote: [bobg@localhost-live ~]$ cat /etc/exports /home    192.168.2.0/24(rw,no_root_squash) but now I am wondering where is that "/home    " coming from? I didn't notice that before ... It has to be there. That tells the nfs server what it should be sharing a

[389-users] Re: A bit help about ACI?

On 8/23/19 11:34 AM, Mark Reynolds wrote: Moving to the correct list (389-users)... On 8/23/19 9:05 AM, Miljan Žugić wrote: I apologize in advance if this is wrong address 😊 I build up 2 389 DS server, make replication and up till now, all looks fine. But I have some issue about ACI. Whe

[389-users] Re: A bit help about ACI?

Moving to the correct list (389-users)... On 8/23/19 9:05 AM, Miljan Žugić wrote: I apologize in advance if this is wrong address 😊 I build up 2 389 DS server, make replication and up till now, all looks fine. But I have some issue about ACI. Where I can find good forum or site to get some

Re: cli support for FIPS 202 - SHA3 plus variants

On 8/23/19 10:15 AM, George N. White III wrote: On Fri, 23 Aug 2019 at 10:07, Robert Moskowitz > wrote: Are there commands to use the SHA3 hashes and there variants? See FIPS 202 and NIST SP800-185 thanks man openssh has:     sha3-224           

Re: NFS mount fails -

On 8/21/19 7:19 AM, Tom H wrote: [root@bobg bobg]# mount 192.168.2.128 /mnt/testb mount: /mnt/testb: special device 192.168.2.128 does not exist. You need to run "mount 192.168.2.128:/path/2/exported/fs /mnt/testb" . If I understand. I think the "path" is complete? -rw-r--r--. 1 root root 41

[389-users] Re: Using self-signed SSL certificate with 389 DS under CentOS 7

Hi, On 8/23/19 4:26 PM, Nicolas Kovacs wrote: Le 23/08/2019 à 15:56, Marc Muehlfeld a écrit : I can't reproduce the problem. I verified the procedure [1] on RHEL 7.7 with RHDS 10.4, and it still works. Just to be sure: is the name of your DS instance really "instance_name"? "instance_name" in

Re: how simple to get jenkins up and running?

On Fri, 23 Aug 2019, Ulf Volmer wrote: > On 23.08.19 12:21, Robert P. J. Day wrote: > > > colleague wants to play with jenkins on a fully-updated fedora 30 > > system, so i figured i'd give it a shot on my similar system, with > > puzzling non-results. > > https://bugzilla.redhat.com/show_bug.cg

Re: how simple to get jenkins up and running?

On 23.08.19 12:21, Robert P. J. Day wrote: > colleague wants to play with jenkins on a fully-updated fedora 30 > system, so i figured i'd give it a shot on my similar system, with > puzzling non-results. https://bugzilla.redhat.com/show_bug.cgi?id=1517477 Best regards Ulf _

[389-users] Re: Using self-signed SSL certificate with 389 DS under CentOS 7

Le 23/08/2019 à 15:56, Marc Muehlfeld a écrit : > > I can't reproduce the problem. I verified the procedure [1] on RHEL 7.7 > with RHDS 10.4, and it still works. > > Just to be sure: is the name of your DS instance really "instance_name"? > "instance_name" in the RHDS docs as a placeholder (that'

Re: cli support for FIPS 202 - SHA3 plus variants

On Fri, 23 Aug 2019 at 10:07, Robert Moskowitz wrote: > Are there commands to use the SHA3 hashes and there variants? > > See FIPS 202 and NIST SP800-185 > > thanks man openssh has: sha3-224 SHA-3 224 Digest sha3-256 SHA-3 256 Digest sha3-384

[389-users] Re: Using self-signed SSL certificate with 389 DS under CentOS 7

Hi Nicolas, On 8/23/19 3:37 PM, Nicolas Kovacs wrote: Le 23/08/2019 à 15:30, Nicolas Kovacs a écrit : The method using the command-line (specified in the RHDS 10 Administration Guide in Chapter 9) doesn't work. To add a little detail. When I follow section 9.3.5 in the RHDS Administration Gui

[389-users] Re: Using self-signed SSL certificate with 389 DS under CentOS 7

Le 23/08/2019 à 15:30, Nicolas Kovacs a écrit : > The method using the command-line (specified in the RHDS 10 > Administration Guide in Chapter 9) doesn't work. To add a little detail. When I follow section 9.3.5 in the RHDS Administration Guide (Generating and Installing a Self-Signed Certificate

[389-users] Using self-signed SSL certificate with 389 DS under CentOS 7

Hi, I've spent a couple hours trying to install a self-signed SSL certificate in my 389 DS installation running CentOS 7. The method using the command-line (specified in the RHDS 10 Administration Guide in Chapter 9) doesn't work. Neither do any of the various HOWTOs and blogs scattered over the

cli support for FIPS 202 - SHA3 plus variants

Are there commands to use the SHA3 hashes and there variants? See FIPS 202 and NIST SP800-185 thanks ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org Fedora Code of Conduct: ht

how simple to get jenkins up and running?

colleague wants to play with jenkins on a fully-updated fedora 30 system, so i figured i'd give it a shot on my similar system, with puzzling non-results. in short: 1) install jenkins 2) "systemctl start jenkins" 3) temporarily disable firewalld, just for testing 4) attempt to browse

[389-users] Re: Windows Sync Agreement issue

Hi all, For OneWaySync, AD to 389ds. I have read this guide https://access.redhat.com/documentation/en-us/red_hat_directory_server/10/html/administration_guide/using_windows_sync-modifying_the_sync_agreement > Synchronization works two ways. The Directory Server sends its updates to > Active Di

Re: External monitor randomly not waking up

On Thu, Aug 22, 2019 at 8:39 PM wrote: > I have an issue where my external monitor (ViewSonic) will not wake up. > Why I think it's related to Fedora is the following: > > Fedora recognizes the monitor's existence when I go into settings. > However, the monitor will not turn on. I have tried xra

Re: F30: i915 - No HDMI output with KMS enabled

On Fri, Aug 23, 2019 at 4:19 AM Samuel Sieb wrote: > On 8/22/19 6:05 PM, Muhammad Hamzah Khan via users wrote: > > Hello, > > > > I have an old Optiplex 3010 which I put F30 on. For some reason, I > cannot get the HDMI port to work without disabling KMS by adding > i915.modeset=0 to the kernel co

Re: F30: latest kernel no external monitor

On Mon, Aug 19, 2019 at 1:54 PM Gianluca Cecchi wrote: > Hello, > executed "dnf update" after about 15 days of inactivity. > Updates has brought in kernel 5.2.8-200.fc30.x86_64 > But after reboot the system is not able to detect (in the sense of no > monitor connection at all seen) when connectin