Discuss

discuss@lists.centos.org

34753 discussions

/tmp full with systemd-private*
by Kai Bojens 09 Feb '16

09 Feb '16

CentOS: 7.1.1503 I have a problem with systemd which somehow manages to fill /tmp up with a lot of files. These files obviously are from the Apache server and don't pose a problem per se. The problem is that these files don't get removed daily: du -hs systemd-private-* 7,7G systemd-private-mpg7rm 0 systemd-private-olXnby 0 systemd-private-qvJJ5o 0 systemd-private-Rs2nBv It was my understanding that these temp-files should have been removed daily as it is stated here: $: grep -v '^#' /usr/lib/systemd/system/systemd-tmpfiles-clean.timer [Unit] Description=Daily Cleanup of Temporary Directories Documentation=man:tmpfiles.d(5) man:systemd-tmpfiles(8) [Timer] OnBootSec=15min OnUnitActiveSec=1d Am I missing something? Is there a better way with a systemd based systemd to have these files removed daily?

3 4

Seeking Clarification CentOS 7 as Samba 4 Active Directory Domain Controller
by Mike 09 Feb '16

09 Feb '16

I performed a Samba 4 Active Directory Domain Controller install in June of 2015 on CentOS 7. At that time I used the Samba 4.1.XX package from SerNet due to the absence of necessary heimdal packages and libraries not provided in the CentOS 7 Samba package. Since the the 4.1 series is on security fix only, I'd like to upgrade to the latest package that tracks with CentOS 7. When searching the samba packages, I've found: samba-client.x86_64 : Samba client programs samba-client-libs.i686 : Samba client libraries samba-client-libs.x86_64 : Samba client libraries samba-common.x86_64 : Files used by both Samba servers and clients samba-common.noarch : Files used by both Samba servers and clients samba-common-libs.x86_64 : Libraries used by both Samba servers and clients samba-common-tools.x86_64 : Tools for Samba servers and clients samba-dc.x86_64 : Samba AD Domain Controller samba-dc-libs.x86_64 : Samba AD Domain Controller Libraries samba-devel.i686 : Developer tools for Samba libraries samba-devel.x86_64 : Developer tools for Samba libraries samba-libs.x86_64 : Samba libraries samba-libs.i686 : Samba libraries samba-python.x86_64 : Samba Python libraries samba-test.x86_64 : Testing tools for Samba servers and clients samba-test-devel.x86_64 : Testing devel files for Samba servers and clients samba-test-libs.i686 : Libraries need by teh testing tools for Samba servers and clients samba-test-libs.x86_64 : Libraries need by teh testing tools for Samba servers and clients It appears the CentOS 7 packages now support full provisioning of a Samba 4 AD DC but I'd like to obtain guidance regarding all necessary packages and libraries necessary to do so on CentOS7. Has anyone on the list used CentOS7 packages (not samba source tarball or SerNet package) to install and provision a Samba4 AD DC. Which combination of repository packages did you use? Thanks for your help. Mike

2 2

[SOLVED] Seeking Clarification CentOS 7 as Samba 4 Active Directory Domain Controller
by Mike 09 Feb '16

09 Feb '16

I'm putting the Centos 7 repository Samba 4 packages on hold. Going to work with Samba 4 source with embedded heimdal. I see this suggested often on the samba mailing list. On Mon, Feb 8, 2016 at 3:41 PM, Mike <1100100(a)gmail.com> wrote: > I performed a Samba 4 Active Directory Domain Controller install in June > of 2015 on CentOS 7. > At that time I used the Samba 4.1.XX package from SerNet due to the > absence of necessary heimdal packages and libraries not provided in the > CentOS 7 Samba package. > Since the the 4.1 series is on security fix only, I'd like to upgrade to > the latest package that tracks with CentOS 7. > > When searching the samba packages, I've found: > > samba-client.x86_64 : Samba client programs > samba-client-libs.i686 : Samba client libraries > samba-client-libs.x86_64 : Samba client libraries > samba-common.x86_64 : Files used by both Samba servers and clients > samba-common.noarch : Files used by both Samba servers and clients > samba-common-libs.x86_64 : Libraries used by both Samba servers and clients > samba-common-tools.x86_64 : Tools for Samba servers and clients > > samba-dc.x86_64 : Samba AD Domain Controller > samba-dc-libs.x86_64 : Samba AD Domain Controller Libraries > > samba-devel.i686 : Developer tools for Samba libraries > samba-devel.x86_64 : Developer tools for Samba libraries > samba-libs.x86_64 : Samba libraries > samba-libs.i686 : Samba libraries > samba-python.x86_64 : Samba Python libraries > samba-test.x86_64 : Testing tools for Samba servers and clients > samba-test-devel.x86_64 : Testing devel files for Samba servers and clients > samba-test-libs.i686 : Libraries need by teh testing tools for Samba > servers and clients > samba-test-libs.x86_64 : Libraries need by teh testing tools for Samba > servers and clients > > It appears the CentOS 7 packages now support full provisioning of a Samba > 4 AD DC but I'd like to obtain guidance regarding all necessary packages > and libraries necessary to do so on CentOS7. > > Has anyone on the list used CentOS7 packages (not samba source tarball or > SerNet package) to install and provision a Samba4 AD DC. Which combination > of repository packages did you use? > > Thanks for your help. > > Mike > >

1 0

Squid as interception HTTPS proxy under CentOS 7
by C. L. Martinez 08 Feb '16

08 Feb '16

Hi all, I am trying to configure squid as a interception HTTPS proxy under CentOS 7. At every https request, I am receiving a certificate error. My current config for squid is: # My localnet acl localnet src 172.22.55.0/28 acl localnet src 172.22.58.0/29 acl SSL_ports port 443 acl Safe_ports port 80 # http acl Safe_ports port 21 # ftp acl Safe_ports port 443 # https acl Safe_ports port 70 # gopher acl Safe_ports port 210 # wais acl Safe_ports port 1025-65535 # unregistered ports acl Safe_ports port 280 # http-mgmt acl Safe_ports port 488 # gss-http acl Safe_ports port 591 # filemaker acl Safe_ports port 777 # multiling http acl CONNECT method CONNECT # # Recommended minimum Access Permission configuration: # # Deny requests to certain unsafe ports http_access deny !Safe_ports # Deny CONNECT to other than secure SSL ports http_access deny CONNECT !SSL_ports # Only allow cachemgr access from localhost http_access allow localhost manager http_access deny manager # We strongly recommend the following be uncommented to protect innocent # web applications running on the proxy server who think the only # one who can access services on "localhost" is a local user #http_access deny to_localhost # # INSERT YOUR OWN RULE(S) HERE TO ALLOW ACCESS FROM YOUR CLIENTS # # Example rule allowing access from your local networks. # Adapt localnet in the ACL section to list your (internal) IP networks # from where browsing should be allowed http_access allow localnet http_access allow localhost # And finally deny all other access to this proxy http_access deny all # Squid normally listens to port 3128 #http_port 3128 # Uncomment and adjust the following to add a disk cache directory. #cache_dir ufs /var/spool/squid 100 16 256 # Leave coredumps in the first cache dir coredump_dir /var/spool/squid # # Add any of your own refresh_pattern entries above these. # refresh_pattern ^ftp: 1440 20% 10080 refresh_pattern ^gopher: 1440 0% 1440 refresh_pattern -i (/cgi-bin/|\?) 0 0% 0 refresh_pattern . 0 20% 4320 # My custom configuration http_port 8079 http_port 8080 intercept https_port 8081 ssl-bump intercept generate-host-certificates=on dynamic_cert_mem_cache_size=4MB key=/etc/squid/custom.private cert=/etc/squid/custom.cert # Anonymous proxy forwarded_for off request_header_access Allow allow all request_header_access Authorization allow all request_header_access WWW-Authenticate allow all request_header_access Proxy-Authorization allow all request_header_access Proxy-Authenticate allow all request_header_access Cache-Control allow all request_header_access Content-Encoding allow all request_header_access Content-Length allow all request_header_access Content-Type allow all request_header_access Date allow all request_header_access Expires allow all request_header_access Host allow all request_header_access If-Modified-Since allow all request_header_access Last-Modified allow all request_header_access Location allow all request_header_access Pragma allow all request_header_access Accept allow all request_header_access Accept-Charset allow all request_header_access Accept-Encoding allow all request_header_access Accept-Language allow all request_header_access Content-Language allow all request_header_access Mime-Version allow all request_header_access Retry-After allow all request_header_access Title allow all request_header_access Connection allow all request_header_access Proxy-Connection allow all request_header_access User-Agent allow all request_header_access Cookie allow all request_header_access All deny all # SSL Bump Config always_direct allow all ssl_bump server-first all sslproxy_cert_error deny all sslproxy_flags DONT_VERIFY_PEER I have tried disabling "sslproxy_cert_error" and "sslproxy_flags" directives, without luck. Any ideas about what am I doing wrong? Thanks. -- Greetings, C. L. Martinez

4 5

Re: [CentOS] C7 AD server
by Miguel Medalha 07 Feb '16

07 Feb '16

>> How I can assing permission on this share? You can easily do it by following the instructions on the Samba Wiki: https://wiki.samba.org/index.php/User_Documentation

1 0

Re: [CentOS] C7 AD server
by Erkin Aka 07 Feb '16

07 Feb '16

these articles could help you. first one is english and second is turkish http://www.alexwyn.com/computer-tips/centos-samba4-active-directory-domain-… http://www.koraykey.com/?p=3842 From: Miguel Medalha <miguelmedalha(a)sapo.pt> To: chris weisiger <cweisiger(a)bellsouth.net> Cc: CentOS mailing list <centos(a)centos.org> Sent: Sunday, February 7, 2016 2:11 AM Subject: Re: [CentOS] C7 AD server >> Try this. I have been thinking of trying it on C7. >> http://www.linuxhelp.net/forums/index.php?showtopic=10868 I wouldn't follow the instructions on that link. Disable iptables? Nah! The author lumps SELinux and the firewall together. What is said about DNS is also misleading. DNS is crucial for AD. Please look at the Samba Wiki instead. _______________________________________________ CentOS mailing list CentOS(a)centos.org https://lists.centos.org/mailman/listinfo/centos

1 0

Re: [CentOS] C7 AD server
by Alessandro Baggi 07 Feb '16

07 Feb '16

Il 07/02/2016 01:11, Miguel Medalha ha scritto: >>> Try this. I have been thinking of trying it on C7. >>> http://www.linuxhelp.net/forums/index.php?showtopic=10868 > > I wouldn't follow the instructions on that link. > > Disable iptables? Nah! > > The author lumps SELinux and the firewall together. > > What is said about DNS is also misleading. DNS is crucial for AD. > > Please look at the Samba Wiki instead. > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://lists.centos.org/mailman/listinfo/centos > Hi Miguel, last link was outdated and I'm using samba4. Over this, I've used sernet samba version to accomplish this work. First, the configuration with samba-tool is simpler. The new approach is a AIO solution. Then, I've provisioned the domain without any problems and joined from win7 host. All works fine. The next step that I tried to accomplish is create a share on this host and I've encountered problem with permission on shared dir. If I try to access/write/read this share I get permission denied. Setting permission on 777 all works but this is not what I want. I've tried to verify the existence of create users and groups but on system (using getent) users are not seen on system and the same for groups. On DC side, I can see user and group with wbinfo command. Share file system is xfs. At the moment Selinux and firewalld are disable for test purpose. How I can assing permission on this share?

1 0

Re: [CentOS] C7 AD server
by Miguel Medalha 07 Feb '16

07 Feb '16

>> Try this. I have been thinking of trying it on C7. >> http://www.linuxhelp.net/forums/index.php?showtopic=10868 I wouldn't follow the instructions on that link. Disable iptables? Nah! The author lumps SELinux and the firewall together. What is said about DNS is also misleading. DNS is crucial for AD. Please look at the Samba Wiki instead.

1 0

C7 AD server
by Alessandro Baggi 06 Feb '16

06 Feb '16

Hi there, I want to setup a AD server with C7. Is this supported using samba release shipped with C7? I can't found Centos7 related how-to for study this setup. Can someone point me in the right direction? Thanks in advance

2 3

Issue with installation on wireless-only desktop workstation, CentOS 7(1511)
by Lamar Owen 05 Feb '16

05 Feb '16

I realize that many on this list have likely applauded the NetworkManager package split that removed wireless stuff into its own package, NetworkManager-wifi, because for wired workstations and servers it might be desirable to not have any wifi software installed. And I believe it was a sound technical decision to do the split. However, in doing a fresh installation of what most call CentOS 7.2, or 7.2.1511, I ran into a real issue that required a bit of deep-diving to find, and a simple 'yum install NetworkManager-wifi' to fix. (although my actual 'yum install' command included the full path to the actual RPM on the install media.......) I have a personal workstation at home, a Dell Optiplex 745 with a Core2Quad Q6600, that is on the other end of the house from the router. While I could run cat5 to the location, it would involve quite a bit of labor, and I have a known-supported USB wifi nic based on the ralink rt3070 (cheap, but works well), so why should I run the cable when wifi should work well? Especially given that the Dell is not going to be there for very long it wouldn't make sense to run cable. Anyway, I configured the wifi network during installation (I actually am growing to like, even prefer, the hub-and-spoke anaconda), it associated with the WPA2-protected AP, grabbed an IP address, and all was good. Did the install; no errors. I rebooted, and now there is no wireless. At all. Doing a bit of troubleshooting shows that the kernel sees the NIC, but NetworkManager shows it as 'unmanaged' ('nmcli d' is the command to use from a shell). So I warmed up my google-fu on my laptop and finally tracked it to a post that mentioned having to install NetworkManager-wifi. Sure enough, on the workstation NetworkManager-wifi was not installed. I mounted the USB install drive's ISO partition and manually installed it, restarted NetworkManager, and it now works just fine. But why did anaconda not select the NetworkManager-wifi package to be installed if a wireless network connection was configured in the installer? Anaconda should have some way of forcing the install of the appropriate NetworkManager modules if those are needed (but only if they are actually needed) for a configured connection during install. I can file a bugzilla, but I thought I'd post about it here first to get an idea of which package in which to file the report, since it's not a bug in NetworkManager-wifi. Anaconda? (that is my first impression of the proper place). So if you have this situation arise where wifi doesn't work after install of current CentOS 7(1511) but does during install, manually install NetworkManager-wifi from the install media and that should clear it up.

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss