similar to: Release 5.5 64-bit hangs on boot

Hi there -- I am trying to install the 64-bit version onto one of our servers. When I get to the point of loading various software packages, I normally select KDE desktop, and also make sure that CentOS extras is also selected. Once that is done, I click on Next to have the installation continue. Every attempt that I have made has resulted in an exception error occurring with the python

Hello -- We completed an installation of CentOS 5.11 32-bit onto a Vmware ESXi 6.0.0 appliance for the purpose of running a legacy application. The hardware in question is a Dell PowerEdge R730xd system. The Vmware tools utility was installed onto the virtual machine, and that initially provided access to the network. Once that was done, patches from the CentOS repository were installed onto the

Hi there -- I need to upgrade one of our systems from its current distribution, Fedora Core 7, to the most recent version distribution, release 5.4, of the CentOS operating system. Can I do an in-place upgrade of the operating system without any adverse side-effects? Are there any issues that I should be concerned with before proceeding? Thanks. The information in this e-mail is intended only

Hello -- When I ran the pam-auth-update command, the PAM configuration window did list Winbind NT/Active Directory authentication as being enabled. This was in addition to the following also being active: Pwquality password strength checking Unix authentication SSS authentication LDAP Authentication Register user sessions in the systemd control group hierarchy Inheritable Capabilites Management

OK, lets dig further. Does your sssd.conf have [sssd] section? Something like [sssd] debug_level = 4 config_file_version = 2 domains = your-domain-name-here If it's not there, add it and modify the [your-domain-name-here] section so it'll look like this: [domain/your-domain-name-here] 23.06.2016, 15:51, "Kaplan, Andrew H." <ahkaplan at partners.org>: > Hello ?

Hello ? Thank-you for your e-mail. I corrected the syntax in the file, and I have confirmed the permissions are correct: -rw-------. 1 root root 266 Jun 23 08:45 sssd.conf Unfortunately, the error condition and messages listed in my initial e-mail are still present. From: l at avc.su [mailto:l at avc.su] Sent: Thursday, June 23, 2016 8:34 AM To: CentOS mailing list; Kaplan, Andrew H.

Try reinstalling vmware-tools Eero 24.8.2016 7.41 ip. "Kaplan, Andrew H." <AHKAPLAN at partners.org> kirjoitti: > Hello -- > > We completed an installation of CentOS 5.11 32-bit onto a Vmware ESXi > 6.0.0 appliance for the purpose of running a legacy application. The > hardware in question is a Dell PowerEdge R730xd system. The Vmware tools > utility was

Hi there -- I am running CentOS 5.3, and I need to have NTFS filesystem support as part of the kernel. Can someone direct me to the correct location for the file(s) and procedure necessary to download and compile? Thanks. The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the e-mail contains patient

Hello -- What repository, or other website, can I access in order to get the latest version of freetds? The version that comes with centos 6.2 is the 0.64 release, and it has a bug in it that is preventing me from running another application. The information in this e-mail is intended only for the person to whom it is addressed. If you believe this e-mail was sent to you in error and the

Hello -- We are running CentOS 6.3 64-bit distribution on one of our servers, and I am involved in upgrading the Apache and OpenSSL packages. I completed an upgrade to both where the version of each that is installed on the server is the following: httpd 2.2.15-29.el6.centos httpd-manual 2.2.15-29.el6.centos httpd-tools 2.2.15-29.el6.centos openssl 1.0.0-27.el6_4.2 openssl-devel 1.0.0-27.el6_4.2

Kaplan, Andrew H. wrote: > Hello -- > > I made the suggested changes to the sssd.conf file, and the results are > the same. > > Just to make sure my syntax is correct: > > The following section was added to the end of the file: > > [sssd] > debug_level = 4 > config_file_version = 2 > domains = company/company.org > One little detail you may have missed:

Hi there -- I am having an issue with the Samba package, release 3.033375, that came bundled with the CentOS 5.3 distribution. It seems that even though I created the smbpasswd file, located at the /etc/samba directory, I am unable to modify the password of the users listed in it. I can run the /usr/bin/smbpasswd -a <username> command as root, and even though there are no errors, a

Hello -- I tried the two methods listed in your e-mail, and unfortunately neither worked. The connection simply closed, or timed out, after about a minute. I mentioned the possibility of creating a symbolic link to the bash shell in my previous e-mail, could that be part of the solution? Thanks. ________________________________ From: Data Control Systems - Mike Elkevizth [mike at

A thought came to me: The smb.conf file on the system has the following entry: template shell = /bin/bash Would creating a symbolic link with the name PHSshell pointing to the /bin/bash shell solve the problem? ________________________________ From: Kaplan, Andrew H. Sent: Thursday, June 09, 2016 11:00 AM To: Data Control Systems - Mike Elkevizth Cc: samba-technical at lists.samba.org; samba

Hello -- I have not touched that file. What change(s) do I need to make there? -----Original Message----- From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On Behalf Of m.roth at 5-cent.us Sent: Thursday, June 23, 2016 9:36 AM To: CentOS mailing list Subject: Re: [CentOS] sssd.conf file missing Kaplan, Andrew H. wrote: > Hello -- > > I made the suggested

Hello -- I made the suggested changes to the sssd.conf file, and the results are the same. Just to make sure my syntax is correct: The following section was added to the end of the file: [sssd] debug_level = 4 config_file_version = 2 domains = company/company.org -----Original Message----- From: l at avc.su [mailto:l at avc.su] Sent: Thursday, June 23, 2016 9:08 AM To: Kaplan, Andrew H.;

What have people found with oplocks in the realm of really saving time? Is it something that's always good to have in an environment where two files being accessed simultaneously is rare? My shared volume is an NFS on a remote server. Just curious what folks have experienced. Terry The information in this e-mail is intended only for the person to whom it is addressed. If you

Hello -- The output of the getent passwd command was the following: <username>@<domainname>:*:##########:##########::/PHShome/<username>:/bin/PHSshell ________________________________ From: Data Control Systems - Mike Elkevizth [mike at datacontrolsystems.com] Sent: Wednesday, June 08, 2016 6:12 PM To: Kaplan, Andrew H. Cc: samba-technical at lists.samba.org; samba at

What does "getent passwd <username>@<domainname>" return on the server for the login shell. By default a samba AD DC sets the login shell for all Active Directory user accounts to /bin/false. The only way I've found to change this, is to override that globally with the "template shell = /bin/bash" option in smb.conf, which enables it globally for all Active

Hi, Try using the format <domainname><winbind separator><username> to login instead of <username>@<domainname>. I'm not sure why, and don't have time to check into it right now, but ssh doesn't like the <username>@<domainname> format for me either. The default winbind separator is a backslash "\", so you'll have to escape it,