I havent tried comparing yet but ive verified that disabling various combinations on the cent machine does not produce the same results.

On 08/19/15 00:10, Patrick O'Callaghan wrote: > On Wed, 2015-08-19 at 00:13 +0900, Scott Mattan wrote: > > I havent tried comparing yet but ive verified that disabling > > various > > combinations on the cent machine does not produce the same > > results. > Same results as what? Is this part of some other thread? > Yes, the OP sent a new message with the same subject in response to an answer that I gave.

password echo "" id EOF

Sorry about the other post, this one may not come in correctly either... In anycase, I will explain this after the main issue... I have the following differences in my /etc/pam.d/su file: Fedora22: #%PAM-1.0 auth sufficient pam_rootok.so # Uncomment the following line to implicitly trust users in the "wheel" group. #auth sufficient pam_wheel.so trust use_uid # Uncomment the following line to require a user to be in the "wheel" group. #auth required pam_wheel.so use_uid auth substack system-auth auth include postlogin account sufficient pam_succeed_if.so uid = 0 use_uid quiet account include system-auth password include system-auth session include system-auth session include postlogin session optional pam_xauth.so CentOS6.6: #%PAM-1.0 auth sufficient pam_rootok.so # Uncomment the following line to implicitly trust users in the "wheel" group. #auth sufficient pam_wheel.so trust use_uid # Uncomment the following line to require a user to be in the "wheel" group. #auth required pam_wheel.so use_uid auth include system-auth account sufficient pam_succeed_if.so uid = 0 use_uid quiet account include system-auth password include system-auth session include system-auth session optional pam_xauth.so When I try to mimic the settings for Fedora 22 in CentOS6.6 to test if this is the cause I become unable to open sockets. [ root@localhost ~ ]# su user could not open session So while this may be the issue, I have to believe that it is not the sole issue and there must be another cause. I hadn't tested the su-l file for differences yet, but it is primarily for login-shells... which admittedly my CenOS6.6 connection is through a login-shell as it is through ssh, whereas the Fedora22 is through a non-login-shell from the GUI. Luckily this CentOS6.6 system is also has a GUI so I will try to replicate from a non-login-shell and get back to you with more information. Now for my lack of understanding of the mailing list. On the computer, I don't understand how to reply without having to copy information from multiple sources. The entire list comes in a single post (very difficult to read) and replying to one means replying to all. Additionally, operating on my phone doesn't even permit me to view the posts, and I must manually go to the archives to read any of the new additions. Is there a better way of viewing this list without having to copy paste titles and contents?

On 08/19/15 08:55, Scott Mattan wrote: > Sorry about the other post, this one may not come in correctly either... > > In anycase, I will explain this after the main issue... > > I have the following differences in my /etc/pam.d/su file: > > Fedora22: > #%PAM-1.0 > auth sufficient pam_rootok.so > # Uncomment the following line to implicitly trust users in the "wheel" group. > #auth sufficient pam_wheel.so trust use_uid > # Uncomment the following line to require a user to be in the "wheel" group. > #auth required pam_wheel.so use_uid > auth substack system-auth > auth include postlogin > account sufficient pam_succeed_if.so uid = 0 use_uid quiet > account include system-auth > password include system-auth > session include system-auth > session include postlogin > session optional pam_xauth.so > > CentOS6.6: > > #%PAM-1.0 > auth sufficient pam_rootok.so > # Uncomment the following line to implicitly trust users in the "wheel" group. > #auth sufficient pam_wheel.so trust use_uid > # Uncomment the following line to require a user to be in the "wheel" group. > #auth required pam_wheel.so use_uid > auth include system-auth > account sufficient pam_succeed_if.so uid = 0 use_uid quiet > account include system-auth > password include system-auth > session include system-auth > session optional pam_xauth.so > > When I try to mimic the settings for Fedora 22 in CentOS6.6 to test if this is the cause I become unable to open sockets. > > [ root@localhost ~ ]# su user > could not open session Use the original file in pam.d for su and try adding this after the pam_rootok.so line... auth required pam_securetty.so > > > > Now for my lack of understanding of the mailing list. > > On the computer, I don't understand how to reply without having to copy information from multiple sources. The entire list comes in a single post (very difficult to read) and replying to one means replying to all. Sounds like you've picked "digest" for the list messages and your mailer doesn't quite know how to handle them. > > Additionally, operating on my phone doesn't even permit me to view the posts, and I must manually go to the archives to read any of the new additions. > > Is there a better way of viewing this list without having to copy paste titles and contents? > Modify your settings to not get a digest. -- It seems most people that say they are "done talking about it" never really are until given the last word.

On Wed, 2015-08-19 at 09:55 +0900, Scott Mattan wrote: > Is there a better way of viewing this list without having to copy > paste titles and contents? Don't use digests (they are a waste of time in this day and age), or if you do then use a mailer that supports direct replying to a digest message (not to the digest itself). Evolution can do this and I think Thunderbird also. Cutting and pasting subject lines does not preserve proper threading and should be avoided.

On Wed, 2015-08-19 at 15:04 +0200, Suvayu Ali wrote: >> Don't use digests (they are a waste of time in this day and age), > or if >> you do then use a mailer that supports direct replying to a digest >> message (not to the digest itself). Evolution can do this and I > think >> Thunderbird also. Cutting and pasting subject lines does not > preserve >> proper threading and should be avoided. > > Actually, afaiU, there is one more step involved. Replying in thread > works only with MIME digests, not plain text. It is a separate > option > in the mailman settings page. This is true, however I'm assuming this list's digests are MIME -formatted.