[389-users] Re: Master-slave replication procedure

[Thomas E Lackey]

Terraform is excellent for provisioning the machine and network infrastructure, 
but it is not a very good tool for managing LDAP replication.  Adding a new DS 
to the replication cluster involves not just changes to that new instance 
(creating the replication account, replica, possibly changelog, etc.) but also 
to all of its replication partners.  And of course, Terraform does not really 
fix the configuration management issue, since not only the Terraform 
configuration needs to be managed, but also its state.  (Replform does not need 
to store state, since it inspects the servers over LDAP to determine its plan.)

 

If you run it globally (‘--global’ ) you only need to maintain one 
configuration file at all.

 

If you run it on each host (our preferred way) there are number of ways you 
might manage the replform configuration across all the LDAP hosts (eg, Puppet) 
but our normal practice is simple: we keep the ‘replform’ configuration in 
source control and have a cron job on each LDAP host that periodically checks 
for updates to the configuration and executes ‘replform’.  This is all setup 
automatically when the host is provisioned by Terraform.  That works equally 
well for a new host that needs to configure replication from scratch and for 
all the existing LDAP hosts which just need to create a replication agreement 
to the new one.

>From past experience, it is quite possible to bring Terraform, Vault, and 
>‘replform’ together to create an entire LDAP cluster, including issuing SSL 
>certs and configuring MMR replication, completely automated.

 

I’ll add an example cron script to GitHub on Monday for the replform part.

 

Cheers,

 

-- 

Thomas E Lackey

 

From: Michal Medvecky  
Sent: Friday, June 22, 2018 4:07 AM
To: General discussion list for the 389 Directory server project. 
<389-users@lists.fedoraproject.org>
Subject: [389-users] Re: Master-slave replication procedure

 

Hello,





19. 6. 2018 v 23:43, Thomas E Lackey mailto:telac...@bozemanpass.com> >:

 

By happy timing, we (Bozeman Pass) just added one of our in-house tools for 
configuring replication to GitHub:   
https://github.com/bozemanpass/replform.

 

I had a look at this but I don’t like the fact you need to statically define 
the configuration. I have variable number of masters and variable number of 
slaves and if I understand this correctly, adding a new backend server would 
need copypasting the replform config.

 

Have you considered creating LDAP providers for Terraform itself?

 

Michal

___
389-users mailing list -- 389-users@lists.fedoraproject.org
To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org/message/UQWBNKMNC23EWS7HKUZ2GH2JLYEICM6M/

Re: caja mount of network drives

[Ed Greshko]

On 06/24/18 07:17, Robert McBroom via users wrote:
> On 06/17/2018 11:57 PM, Robert McBroom via users wrote:
>> When I look where caja used to mount network drives I see
>>
>>   /run/user/1001:
>>   /usr/bin/ls: cannot access '/run/user/1001/./doc': Permission denied
>>   /usr/bin/ls: cannot access '/run/user/1001/./gvfs': Permission denied
>>     total used in directory 4 available 358772
>>     drwx--. 9 rm3  rm3  280 Jun 17 23:25 .
>>     drwxr-xr-x. 3 root root  60 Jun 17 01:17 ..
>>     srw-rw-rw-. 1 rm3  rm3    0 Jun 17 01:17 bus
>>     drwx--. 3 rm3  rm3   60 Jun 17 01:17 dbus-1
>>     drwx--. 2 rm3  rm3   60 Jun 17 07:38 dconf
>>     d?? ? ?    ?  ?    ? doc
>>     d?? ? ?    ?  ?    ? gvfs
>>     srw---. 1 rm3  rm3    0 Jun 17 07:34 kdeinit5__0
>>     drwx--. 2 rm3  rm3   60 Jun 17 07:35 keyring
>>     srwxrwxr-x. 1 rm3  rm3    0 Jun 17 01:17 klauncherTJ1413.1.slave-socket
>>     srwxrwxr-x. 1 rm3  rm3    0 Jun 17 07:34 klauncherTJ7613.1.slave-socket
>>     -rw-rw-r--. 1 rm3  rm3   67 Jun 17 07:34 KSMserver__0
>>     drwx--. 2 rm3  rm3   80 Jun 17 01:18 pulse
>>     drwxr-xr-x. 3 rm3  rm3  100 Jun 17 01:17 systemd
> Curious
> This is from a root invocation of emacs.  running ls -l in a root window 
> gives the
> same listing. Looking at the same directory with a the user invocation of 
> emacs gives
>
>   /run/user/1001:
>   total used in directory 4 available 358768
>   drwx--. 9 rm3  rm3  260 Jun 23 10:18 .
>   drwxr-xr-x. 3 root root  60 Jun 23 08:06 ..
>   srw-rw-rw-. 1 rm3  rm3    0 Jun 23 08:06 bus
>   drwx--. 3 rm3  rm3   60 Jun 23 08:06 dbus-1
>   drwx--. 2 rm3  rm3   60 Jun 23 10:01 dconf
>   dr-x--. 2 rm3  rm3    0 Dec 31  1969 doc
>   dr-x--. 3 rm3  rm3    0 Jun 23 08:06 gvfs
>   srw---. 1 rm3  rm3    0 Jun 23 08:06 kdeinit5__0
>   drwx--. 2 rm3  rm3   60 Jun 23 08:07 keyring
>   srwxrwxr-x. 1 rm3  rm3    0 Jun 23 08:06 klauncherTJ1425.1.slave-socket
>   -rw-rw-r--. 1 rm3  rm3   67 Jun 23 08:06 KSMserver__0
>   drwx--. 2 rm3  rm3   80 Jun 23 08:07 pulse
>   drwxr-xr-x. 3 rm3  rm3  100 Jun 23 08:06 systemd
>
> and the smb mounted directory is available.
>
>   /run/user/1001/gvfs:
>   total 0
>   dr-x--. 3 rm3 rm3   0 Jun 23 08:06 .
>   drwx--. 9 rm3 rm3 260 Jun 23 10:18 ..
>   drwx--. 1 rm3 rm3   0 Jun 11 14:57 
> smb-share:server=linksys00270,share=seagt1
>
> What has happend to root?

Nothing

If you google "run user doc permissions root fuse" you'd find more details as to
why.  But, very basically, it is by design.


-- 
Conjecture is just a conclusion based on incomplete information. It isn't a 
fact.


signature.asc
Description: OpenPGP digital signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/5R3WKSMUAZBFQHJWX7MYKIWTTXJ6JXEJ/

Re: SSH private keys?

[Todd Zullinger]

Mike Wright wrote:
> On 06/23/2018 01:35 PM, Jeffrey Ross wrote:
>> 
>> my .ssh directory has my private key in a file called "id_rsa" nothing
>> with .pub on the end and if I understand correctly running ssh will look
>> for the private key in a few different file names, none of which end
>> with .pub.
>> 
> Gotta have both halves.  "ssh-keygen" will give you new keys.

No need to generate a new keypair.  ssh-keygen -y "will read
a private OpenSSH format file and print an OpenSSH public
key to stdout."

-- 
Todd
~~
Cryptography products may be declared illegal, but the information
will never be.
-- Bruce Schneier



signature.asc
Description: PGP signature
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/U3EJ2K35ZQ26R675YGQWOSGKO2EECQQA/

Re: caja mount of network drives

[Robert McBroom via users]

On 06/17/2018 11:57 PM, Robert McBroom via users wrote:

When I look where caja used to mount network drives I see

  /run/user/1001:
  /usr/bin/ls: cannot access '/run/user/1001/./doc': Permission denied
  /usr/bin/ls: cannot access '/run/user/1001/./gvfs': Permission denied
    total used in directory 4 available 358772
    drwx--. 9 rm3  rm3  280 Jun 17 23:25 .
    drwxr-xr-x. 3 root root  60 Jun 17 01:17 ..
    srw-rw-rw-. 1 rm3  rm3    0 Jun 17 01:17 bus
    drwx--. 3 rm3  rm3   60 Jun 17 01:17 dbus-1
    drwx--. 2 rm3  rm3   60 Jun 17 07:38 dconf
    d?? ? ?    ?  ?    ? doc
    d?? ? ?    ?  ?    ? gvfs
    srw---. 1 rm3  rm3    0 Jun 17 07:34 kdeinit5__0
    drwx--. 2 rm3  rm3   60 Jun 17 07:35 keyring
    srwxrwxr-x. 1 rm3  rm3    0 Jun 17 01:17 
klauncherTJ1413.1.slave-socket
    srwxrwxr-x. 1 rm3  rm3    0 Jun 17 07:34 
klauncherTJ7613.1.slave-socket

    -rw-rw-r--. 1 rm3  rm3   67 Jun 17 07:34 KSMserver__0
    drwx--. 2 rm3  rm3   80 Jun 17 01:18 pulse
    drwxr-xr-x. 3 rm3  rm3  100 Jun 17 01:17 systemd

Curious
This is from a root invocation of emacs.  running ls -l in a root window 
gives the same listing. Looking at the same directory with a the user 
invocation of emacs gives


  /run/user/1001:
  total used in directory 4 available 358768
  drwx--. 9 rm3  rm3  260 Jun 23 10:18 .
  drwxr-xr-x. 3 root root  60 Jun 23 08:06 ..
  srw-rw-rw-. 1 rm3  rm3    0 Jun 23 08:06 bus
  drwx--. 3 rm3  rm3   60 Jun 23 08:06 dbus-1
  drwx--. 2 rm3  rm3   60 Jun 23 10:01 dconf
  dr-x--. 2 rm3  rm3    0 Dec 31  1969 doc
  dr-x--. 3 rm3  rm3    0 Jun 23 08:06 gvfs
  srw---. 1 rm3  rm3    0 Jun 23 08:06 kdeinit5__0
  drwx--. 2 rm3  rm3   60 Jun 23 08:07 keyring
  srwxrwxr-x. 1 rm3  rm3    0 Jun 23 08:06 klauncherTJ1425.1.slave-socket
  -rw-rw-r--. 1 rm3  rm3   67 Jun 23 08:06 KSMserver__0
  drwx--. 2 rm3  rm3   80 Jun 23 08:07 pulse
  drwxr-xr-x. 3 rm3  rm3  100 Jun 23 08:06 systemd

and the smb mounted directory is available.

  /run/user/1001/gvfs:
  total 0
  dr-x--. 3 rm3 rm3   0 Jun 23 08:06 .
  drwx--. 9 rm3 rm3 260 Jun 23 10:18 ..
  drwx--. 1 rm3 rm3   0 Jun 11 14:57 
smb-share:server=linksys00270,share=seagt1


What has happend to root?

Robert
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/4TY5AIVCGYMOAYTOOTMBNKMGB2O3K6UX/

Re: >60gb of reserved memory??

[Samuel Sieb]

On 06/21/2018 09:55 AM, Rick Stevens wrote:

RAMdisk (e.g. /tmp). By default, Fedora uses 50% of your RAM for /tmp
(an absolutely idiotic idea, IMHO, which is why I turn that off and use
a normal filesystem directory for /tmp).


Are you aware that the tmpfs memory is not reserved, that the size is 
only a limit for how much it can use?  Also, the used memory can be 
swapped out if the memory pressure gets too high.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/XVQZW6JQSBC7ZBSVUYKXXUF7F5SLEWK4/

Re: SSH private keys?

[Mike Wright]

On 06/23/2018 01:35 PM, Jeffrey Ross wrote:


my .ssh directory has my private key in a file called "id_rsa" nothing 
with .pub on the end and if I understand correctly running ssh will look 
for the private key in a few different file names, none of which end 
with .pub.



Gotta have both halves.  "ssh-keygen" will give you new keys.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/UFLQVN5BTHFQJ7YUPMIQAHBUDLZGGNSY/

Re: SSH private keys?

[Gordon Messmer]

On 06/23/2018 01:40 PM, Jeffrey Ross wrote:

ok, I used the two commands -

eval "$(ssh-agent -s)"
ssh-add ~/.ssh/id_rsa

and this works for the one terminal shell I entered the commands in, 
any other terminal I either need to re-run the commands in that shell 
or unlock my private key when I type ssh 


The "eval" line runs a new ssh-agent and replaces the environment 
variables that normally refer to the ssh-agent run by gnome-keyring.  If 
you exclude that line, and only run ssh-add, then you'll add keys to the 
gnome-keyring's ssh-agent, and those keys will be available in all of 
the terminals.


not sure if putting the commands in the rc file to run would be the 
best thing to do, I suspect I'll have to unlock every time I open a 
new window, plus this is not what I remember, I remember (maybe 
incorrectly) getting a graphical dialogue box asking me to unlock my key. 


Yes, gnome-keyring will do that if you have the public keys present.
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/YDW3DSI2HR35GFKX6RWTDSUUA7KNAPFJ/

Re: SSH private keys?

[Gordon Messmer]

On 06/23/2018 01:35 PM, Jeffrey Ross wrote:
my .ssh directory has my private key in a file called "id_rsa" nothing 
with .pub on the end and if I understand correctly running ssh will 
look for the private key in a few different file names, none of which 
end with .pub. 



Yes, that's how ssh behaves.  However, as I said, gnome-keyring will 
only automatically load a private key if the public key is also present, 
with the same filename plus a .pub suffix.  If you don't have the public 
keys in your .ssh folder, then that is the reason that GNOME is not 
prompting you to unlock your private files.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/WHO3V4L7SDJSCOXPJKMWV2M2NI3G3IDW/

Re: SSH private keys?

[Jeffrey Ross]

On 06/22/2018 07:54 AM, Berend De Schouwer wrote:

On Fri, 2018-06-22 at 07:37 -0400, Jeffrey Ross wrote:

At one point Fedora had something (keyring?) that would allow me to
unlock my SSH private keys and it would keep the unlocked key
available
so I could ssh without having to unlock my key every time.  I
typically
run a simple "terminal" window and then "ssh " since my key
is
not retained unlocked I'm prompted for a password.

Fast forward to today, the system had been reinstalled (new
hardware,
new disks, etc) and I no longer have that ability.  I'm currently
runn
Fedora 28 and the desktop is "Gnome", I'm sure it is just a matter
of
installing/configuring/running the correct application but which
one?

You're *probably* missing the gnome-keyring package.

you'll need:
- ssh-agent (to remember)
- an app that processes your passphrase (gnome-keyring or pinentry-gtk)

ssh-agent is part of openssh-clients.  It's usually run by gnome-
keyring-daemon.  Look in the process list for it.  It should be
running.

ssh-add is a cli app that will let you add the key and trigger a
passphrase without a GUI.

You can see if a key is being remembered by running 'ssh-add -l'

gnome-shell should prompt for the key (the prompt will be themed like
gnome-shell), but so can pinentry/pinentry-gtk (themed like a Gtk2 app)
___


ok, I used the two commands -

eval "$(ssh-agent -s)"
ssh-add ~/.ssh/id_rsa

and this works for the one terminal shell I entered the commands in, any 
other terminal I either need to re-run the commands in that shell or 
unlock my private key when I type ssh 


not sure if putting the commands in the rc file to run would be the best 
thing to do, I suspect I'll have to unlock every time I open a new 
window, plus this is not what I remember, I remember (maybe incorrectly) 
getting a graphical dialogue box asking me to unlock my key.


Jeff
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/3F34ORCFYOJUHP4BOLFXVHX444TKFVO7/

Re: Redshift has an issue with geoclue2

[ToddAndMargo]

On 06/23/2018 10:50 AM, John Pilkington wrote:

On 22/06/18 22:24, ToddAndMargo wrote:

Hi All,

Fedora 28, x64

redshift-gtk-1.11-8.fc28.x86_64
redshift-1.11-8.fc28.x86_64
geoclue2-libs-2.4.10-2.fc28.x86_64
geoclue2-2.4.10-2.fc28.x86_64

When starting Redshift, I get the following error

$ redshift
 Trying location provider `geoclue2'...
 Using provider `geoclue2'.
 Unable to start GeoClue client:
 GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message
 recipient disconnected from message bus without replying.
 Unable to connect to GeoClue.
 Unable to get location from provider.

the pop up says:
 GDBus.Error" org.freedesktop.DBus.Error.AccessDenied

Any word of wisdom?  It worked under Fedora 27.

-T


Not tried, but the FAQ has

There is currently no way for Redshift to adjust the color temperature 
in Wayland. (quotes f25)


?


I am using Xfce 4,12 which does not use Wayland.

___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/FJLQYWV2S2SCAQK4QZDLTQD2FI4XVP7O/

Re: SSH private keys?

[Jeffrey Ross]

On 06/22/2018 03:45 PM, Gordon Messmer wrote:

On 06/22/2018 04:37 AM, Jeffrey Ross wrote:
Fast forward to today, the system had been reinstalled (new hardware, 
new disks, etc) and I no longer have that ability.  I'm currently 
runn Fedora 28 and the desktop is "Gnome", I'm sure it is just a 
matter of installing/configuring/running the correct application 
but which one? 


That's handled by gnome-keyring and, as of this version of GNOME, 
ssh-agent.  As far as I can tell, those are both required components, 
so they're probably not missing on your workstation. The problem 
*might* be that GNOME keyring will only automatically unlock private 
keys if there is a valid public key with the same name, and a .pub 
suffix.  So, you might not have the public keys. Or, you might have a 
.pub file that's *really* old and no longer valid.


There is an open bug concerning the fact that if there is an invalid 
.pub file in .ssh, GNOME keyring won't automatically unlock *any* 
keys, so remove any old key files.


https://bugzilla.redhat.com/show_bug.cgi?id=1568895
my .ssh directory has my private key in a file called "id_rsa" nothing 
with .pub on the end and if I understand correctly running ssh will look 
for the private key in a few different file names, none of which end 
with .pub.


Jeff
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/MXBNVTPA3WGNGSQ3745QHC76P62QIFXN/

Re: Redshift has an issue with geoclue2

[John Pilkington]

On 22/06/18 22:24, ToddAndMargo wrote:

Hi All,

Fedora 28, x64

redshift-gtk-1.11-8.fc28.x86_64
redshift-1.11-8.fc28.x86_64
geoclue2-libs-2.4.10-2.fc28.x86_64
geoclue2-2.4.10-2.fc28.x86_64

When starting Redshift, I get the following error

$ redshift
     Trying location provider `geoclue2'...
     Using provider `geoclue2'.
     Unable to start GeoClue client:
     GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message
     recipient disconnected from message bus without replying.
     Unable to connect to GeoClue.
     Unable to get location from provider.

the pop up says:
     GDBus.Error" org.freedesktop.DBus.Error.AccessDenied

Any word of wisdom?  It worked under Fedora 27.

-T


Not tried, but the FAQ has

There is currently no way for Redshift to adjust the color temperature 
in Wayland. (quotes f25)


?
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/GOLNW6HH2PVMX4KGP7SWRPUUESTRKIVI/

Fedora's OwnCloud and NextCloud Broke - What I did

[Clifford Snow]

When I upgraded to F28, OwnCloud stopped working. Another reported the same
problem with NextCloud. The problem has been reported in bugzilla [1] as
Cannot login after upgrading from F27 to F28. Patrick Reeb provided a fix
with a fix-owncloud [2] script which downgrades php-sabre to F25.

Because both of the Fedora packages of OwnCloud and NextCloud are dated I
decided to use the NextCloud zip package of their current version 13.

Basically what I did was to install Fedora's NextCloud package to get the
basic configuration files and then removed the package so all what was left
was configuration files with a .rpmsave extension. Using the
nextcloud-13.0.4.zip package [3] I moved the files to my nextcloud
directory from the Fedora's package.

After a few tweaks to /etc/httpd/conf/httpd.conf files, the login prompt
appeared on my localhost/nextcloud.  I was unable to configure my
postgresql database from the web browser, so I used the command line tool
[4] (occ) to finish the install.

I did try the snap install of the nextcloud-server, but couldn't get it to
work. However, the snap nextcloud-client works like a charm.

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1562949
[2] https://bugzilla.redhat.com/attachment.cgi?id=1431595
[3] https://nextcloud.com/install/#instructions-server
[4] https://nextcloud.com/install/#instructions-server

-- 
@osm_seattle
osm_seattle.snowandsnow.us
OpenStreetMap: Maps with a human touch
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/WTA4HXRXUAXRJPZO2UOIDIG4JDYIBBJO/

Re: better subject

[Rex Dieter]

Wolfgang Pfeiffer wrote:

> On Fri, Jun 22, 2018 at 08:28:59AM -0500, Rex Dieter wrote:
>>François Patte wrote:
>>
>>> Bonjour,
>>
>>such inflammatory subject lines are not welcome, please do better next
>>time.

> I agree the subject line (like the rest of the mail) wasn't helpful to
> solve the OP's problem. But please keep perspective: no one in his
> right mind will become suicidal because of a messed up subject line.

I'm simply making it clear such commentary is not welcome nor is in the 
spirit or letter of the fedora code of conduct.  If we are not diligent on 
making clear what is and is not acceptable, then the quality of future 
discourse here can be harmed.  I very much want to ensure fedora 
communications remain friendly, constructive, and helpful.

> And I obviously cannot talk for the rest of us here: but I'm grown
> up - no need to protect my tender heart.

I appreciate that.  :)  I'm doing this more as a public service for 
posterity, not for any specific individuals.

-- Rex
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/PFZ6XOET5X3MZMRUDOGLLSTVILSA7TPN/

Re: better subject

[Wolfgang Pfeiffer]

On Fri, Jun 22, 2018 at 08:28:59AM -0500, Rex Dieter wrote:

François Patte wrote:


Bonjour,


such inflammatory subject lines are not welcome, please do better next time.



I wasn't "inflamed" in any way by some subject line. Ever.

I agree the subject line (like the rest of the mail) wasn't helpful to
solve the OP's problem. But please keep perspective: no one in his
right mind will become suicidal because of a messed up subject line.

And I obviously cannot talk for the rest of us here: but I'm grown
up - no need to protect my tender heart.

Thank you.
Wolfgang
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org/message/OG5YEKHN7T7AJSHGUX357MLM5YSDRBM2/