Discuss

discuss@lists.centos.org

34753 discussions

Happy new years everyone
by Karanbir Singh 01 Jan '13

01 Jan '13

hi, 2012 has been a great and eventful year for CentOS, the project. CentOS the Linux Distribution and for everyone involved, including the users. Along with new initiatives, lots of new relationships came up - and most of all, lots of new people stepped up to help in various corners of the project. Hope to see even more new efforts kicking off in 2013 and even more people getting involved. Everyone, have a great and safe new years. See you all in 2013. Regards, -- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh ICQ: 2522219 | Yahoo IM: z00dax | Gtalk: z00dax GnuPG Key : http://www.karan.org/publickey.asc

6 5

Samba vs. Firewall and/or SELinux
by Ibrahim Yurtseven 01 Jan '13

01 Jan '13

Hi all. I created a smb-share on my el6 for all windows-pcs in my home-network (I'm the only Linux-User in my family) for sharing all the stuff we have, like music and videos and documents. The share will be shown on the other pcs (Windows XP), but they can't open it. The error-message ist "Share not found" on our preferred language of course! SELINUX-CONFIG sh-4.1# cat /etc/selinux/targeted/contexts/files/file_contexts.local # This file is auto-generated by libsemanage # Do not edit directly. /data(/.*)? system_u:object_r:samba_share_t:s0 FIREWALL-CONFIG (Port 901 is for SWAT) sh-4.1# cat /etc/sysconfig/iptables # Generated by iptables-save v1.4.7 on Thu Dec 20 17:28:14 2012 *filter :INPUT ACCEPT [0:0] :FORWARD ACCEPT [0:0] :OUTPUT ACCEPT [0:0] -A INPUT -p tcp -m state --state NEW -m tcp --dport 901 -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp --dport 445 -j ACCEPT -A INPUT -p tcp -m state --state NEW -m tcp --dport 139 -j ACCEPT -A INPUT -p udp -m state --state NEW -m udp --dport 138 -j ACCEPT -A INPUT -p udp -m state --state NEW -m udp --dport 137 -j ACCEPT COMMIT # Completed on Thu Dec 20 17:28:14 2012 SAMBA-CONFIG "Alice im Wunderland" is the testfile I uploaded with disabled Firewall and disabled SELinux sh-4.1# testparm Load smb config files from /etc/samba/smb.conf rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384) Processing section "[public]" Loaded services file OK. Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions [global] workgroup = NETZWERK server string = Samba Server Version %v security = SHARE log file = /var/log/samba/log.%m max log size = 50 cups options = raw [public] comment = hier kannn reinkopiert werden path = /data/public read only = No create mask = 0777 guest only = Yes guest ok = Yes sh-4.1# cat /etc/samba/smbusers # Unix_name = SMB_name1 SMB_name2 ... root = administrator admin nobody = guest pcguest smbguest sh-4.1# ls -lisah /data/public total 144M 1703938 12K drwxrwxrwx. 4 nobody users 12K Dec 27 13:39 . 1703937 4.0K drwxr-xr-x. 3 root root 4.0K Dec 22 19:43 .. 1706985 144M -rwxrw-rw- 1 nobody nobody 144M Dec 27 13:39 Disney_ Alice im Wunderland (1951).mp4 -- Ibrahim "Arastirmacilar" Yurtseven 2.6.32-279.19.1.el6.i686

7 12

Hi
by Derek Stewart 31 Dec '12

31 Dec '12

Hi, Just joinedthe mailing list. I am new to Centos, anybody got any tips. Derek

9 12

xoscope
by Mark LaPierre 30 Dec '12

30 Dec '12

Is xoscope available in any available CentOS repo? http://xoscope.sourceforge.net/ -- _ °v° /(_)\ ^ ^ Mark LaPierre Registerd Linux user No #267004 https://linuxcounter.net/ ****

3 4

Live CD iso
by James Freer 30 Dec '12

30 Dec '12

Hi folks I'm just about to start using Centos again. I used it briefly a couple of years ago but found the switch to rpm a bit much after using deb for 5 years. Now there seem to be a lot of changes on the deb front so i'm going to try again with rpm. I noticed that there is now a live CD (as well as the DVD) instead of the six CDs that i used before (iirc). I would just be grateful if someone could confirm that... i've been an xfce user so i was thinking that i've either got to go back to gnome and load the xfce desktop or use the DVD (and install xfce straight). thanks james

5 15

Ethernet puzzle
by Ashley M. Kirchner 28 Dec '12

28 Dec '12

So I just finished doing a fresh install of CentOS 6.3. The machine has three ethernet ports in it: one on the motherboard (VIA Rhine), and two add-on cards, an Intel Pro100 and an old SMC1255TX. When CentOS comes up, this is what I see in the dmesg output: # dmesg | grep eth e100 0000:00:08.0: eth0: addr 0xf6043000, irq 16, MAC addr 00:02:b3:be:02:87 eth1: ADMtek Comet rev 17 at MMIO 0xf6040000, 00:4c:69:6e:75:79, IRQ 17. udev: renamed network interface eth0 to rename2 udev: renamed network interface eth1 to eth3 udev: renamed network interface rename2 to eth1 eth0: VIA Rhine II at 0xf6042000, 00:16:17:17:22:8e, IRQ 23. eth0: MII PHY found at address 1, status 0x786d advertising 05e1 Link 45e1. eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 eth0: no IPv6 routers present So, according to the musical playing going on there, the result is: eth0: VIA Rhine eth1: IntelPro 100 (originally comes up as eth0 but gets renamed eth1) eth3: SMC1255TX (originally comes up as eth1 but gets renamed eth3) Here's my issue: In udev rules (/etc/udev/rules.d/70-persistent-net.rules I see: # PCI device 0x1113:0x1216 (tulip) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:4c:68:6e:ff:ff", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2" # PCI device 0x8086:0x1229 (e100) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:02:b3:be:02:87", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1" # PCI device 0x1106:0x3065 (via-rhine) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:16:17:17:22:8e", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0" # PCI device 0x1113:0x1216 (tulip) SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:4c:69:6e:75:79", ATTR{type}=="1", KERNEL=="eth*", NAME="eth3" Question is, where did the first tulip interface come from? That's not any of the interfaces on the machine, it doesn't match the MAC address of any of the interfaces, so where'd it come from? Furthermore, when I look in /etc/sysconfig/network-scripts/ifcfg-eth2, the HWADDR there is the same as the first interface listed above. But again, it's not in dmesg's output. As far as I can tell, it's a ghost interface ... What gives, and how can I get rid of it so that the proper interface gets the eth2 spot? A

5 11

Help Getting Postfix relaying via Gmail
by Clint Dilks 28 Dec '12

28 Dec '12

Hi, I am trying to get a CentOS 6 system relaying mail via my G-Mail account. I followed the instructions found at https://www.zulius.com/how-to/set-up-postfix-with-a-remote-smtp-relay-host/… there seems to be a problem with authentication. I have done some research but still can't get this working. Any suggestions ? It seems the user and password are correct. Dec 27 23:15:36 hbc postfix/pickup[2588]: 8DEB1410B3: uid=0 from=<root> Dec 27 23:15:36 hbc postfix/cleanup[2603]: 8DEB1410B3: message-id=< 20121227101536.8DEB1410B3(a)hbc.hillcrest.org.nz> Dec 27 23:15:36 hbc postfix/qmgr[2589]: 8DEB1410B3: from=< root(a)hbc.hillcrest.org.nz>, size=317, nrcpt=1 (queue active) Dec 27 23:15:37 hbc postfix/smtp[2605]: connect to smtp.gmail.com[2607:f8b0:400e:c00::6d]:587: Network is unreachable Dec 27 23:15:37 hbc postfix/smtp[2605]: vstream_buf_get_ready: fd 15 got 45 Dec 27 23:15:37 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.109]:587: 220 mx.google.com ESMTP vo8sm17581810pbc.16 Dec 27 23:15:37 hbc postfix/smtp[2605]: > smtp.gmail.com[173.194.79.109]:587: EHLO hbc.hillcrest.org.nz Dec 27 23:15:37 hbc postfix/smtp[2605]: vstream_fflush_some: fd 15 flush 27 Dec 27 23:15:37 hbc postfix/smtp[2605]: vstream_buf_get_ready: fd 15 got 122 Dec 27 23:15:37 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.109]:587: 250-mx.google.com at your service, [121.75.4.39] Dec 27 23:15:37 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.109]:587: 250-SIZE 35882577 Dec 27 23:15:37 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.109]:587: 250-8BITMIME Dec 27 23:15:37 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.109]:587: 250-STARTTLS Dec 27 23:15:37 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.109]:587: 250 ENHANCEDSTATUSCODES Dec 27 23:15:37 hbc postfix/smtp[2605]: server features: 0x101b size 35882577 Dec 27 23:15:37 hbc postfix/smtp[2605]: > smtp.gmail.com[173.194.79.109]:587: STARTTLS Dec 27 23:15:37 hbc postfix/smtp[2605]: vstream_fflush_some: fd 15 flush 10 Dec 27 23:15:37 hbc postfix/smtp[2605]: vstream_buf_get_ready: fd 15 got 30 Dec 27 23:15:37 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.109]:587: 220 2.0.0 Ready to start TLS Dec 27 23:15:37 hbc postfix/smtp[2605]: event_request_timer: reset 0x7f79a9113bb0 0x7f79aa8429d0 5 Dec 27 23:15:37 hbc postfix/smtp[2605]: send attr request = seed Dec 27 23:15:37 hbc postfix/smtp[2605]: send attr size = 32 Dec 27 23:15:37 hbc postfix/smtp[2605]: vstream_fflush_some: fd 9 flush 22 Dec 27 23:15:37 hbc postfix/smtp[2605]: vstream_buf_get_ready: fd 9 got 60 Dec 27 23:15:37 hbc postfix/smtp[2605]: private/tlsmgr: wanted attribute: status Dec 27 23:15:37 hbc postfix/smtp[2605]: input attribute name: status Dec 27 23:15:37 hbc postfix/smtp[2605]: input attribute value: 0 Dec 27 23:15:37 hbc postfix/smtp[2605]: private/tlsmgr: wanted attribute: seed Dec 27 23:15:37 hbc postfix/smtp[2605]: input attribute name: seed Dec 27 23:15:37 hbc postfix/smtp[2605]: input attribute value: xIHq7bnC7bggzN5/v38KVLhUrfnowW/aYWlTcvBI1LM= Dec 27 23:15:37 hbc postfix/smtp[2605]: private/tlsmgr: wanted attribute: (list terminator) Dec 27 23:15:37 hbc postfix/smtp[2605]: input attribute name: (end) Dec 27 23:15:38 hbc postfix/smtp[2605]: > smtp.gmail.com[173.194.79.109]:587: EHLO hbc.hillcrest.org.nz Dec 27 23:15:38 hbc postfix/smtp[2605]: vstream_fflush_some: fd 15 flush 27 Dec 27 23:15:38 hbc postfix/smtp[2605]: vstream_buf_get_ready: fd 15 got 145 Dec 27 23:15:38 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.109]:587: 250-mx.google.com at your service, [121.75.4.39] Dec 27 23:15:38 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.109]:587: 250-SIZE 35882577 Dec 27 23:15:38 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.109]:587: 250-8BITMIME Dec 27 23:15:38 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.109]:587: 250-AUTH LOGIN PLAIN XOAUTH XOAUTH2 Dec 27 23:15:38 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.109]:587: 250 ENHANCEDSTATUSCODES Dec 27 23:15:38 hbc postfix/smtp[2605]: server features: 0x102b size 35882577 Dec 27 23:15:38 hbc postfix/smtp[2605]: maps_find: smtp_sasl_passwd: smtp.gmail.com: not found Dec 27 23:15:38 hbc postfix/smtp[2605]: maps_find: smtp_sasl_passwd: hash:/etc/postfix/sasl_passwd(0,lock|fold_fix): smtp.gmail.com:587 = clint.dilks(a)gmail.com: Dec 27 23:15:38 hbc postfix/smtp[2605]: smtp_sasl_passwd_lookup: host ` smtp.gmail.com' user `<user>@gmail.com' pass `<correct password>' Dec 27 23:15:38 hbc postfix/smtp[2605]: starting new SASL client Dec 27 23:15:38 hbc postfix/smtp[2605]: name_mask: noanonymous Dec 27 23:15:38 hbc postfix/smtp[2605]: smtp_sasl_authenticate: smtp.gmail.com[173.194.79.109]:587: SASL mechanisms LOGIN PLAIN XOAUTH XOAUTH2 Dec 27 23:15:38 hbc postfix/smtp[2605]: warning: SASL authentication failure: No worthy mechs found Dec 27 23:15:38 hbc postfix/smtp[2605]: 8DEB1410B3: SASL authentication failed; cannot authenticate to server smtp.gmail.com[173.194.79.109]: no mechanism available Dec 27 23:15:38 hbc postfix/smtp[2605]: > smtp.gmail.com[173.194.79.109]:587: QUIT Dec 27 23:15:38 hbc postfix/smtp[2605]: name_mask: resource Dec 27 23:15:38 hbc postfix/smtp[2605]: name_mask: software Dec 27 23:15:38 hbc postfix/smtp[2605]: vstream_fflush_some: fd 15 flush 6 Dec 27 23:15:38 hbc postfix/smtp[2605]: vstream_fflush_some: fd 15 flush 0 Dec 27 23:15:38 hbc postfix/smtp[2605]: disposing SASL state information Dec 27 23:15:39 hbc postfix/smtp[2605]: vstream_buf_get_ready: fd 15 got 45 Dec 27 23:15:39 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.108]:587: 220 mx.google.com ESMTP bi8sm14464509pab.15 Dec 27 23:15:39 hbc postfix/smtp[2605]: > smtp.gmail.com[173.194.79.108]:587: EHLO hbc.hillcrest.org.nz Dec 27 23:15:39 hbc postfix/smtp[2605]: vstream_fflush_some: fd 15 flush 27 Dec 27 23:15:39 hbc postfix/smtp[2605]: vstream_buf_get_ready: fd 15 got 122 Dec 27 23:15:39 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.108]:587: 250-mx.google.com at your service, [121.75.4.39] Dec 27 23:15:39 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.108]:587: 250-SIZE 35882577 Dec 27 23:15:39 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.108]:587: 250-8BITMIME Dec 27 23:15:39 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.108]:587: 250-STARTTLS Dec 27 23:15:39 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.108]:587: 250 ENHANCEDSTATUSCODES Dec 27 23:15:39 hbc postfix/smtp[2605]: server features: 0x101b size 35882577 Dec 27 23:15:39 hbc postfix/smtp[2605]: > smtp.gmail.com[173.194.79.108]:587: STARTTLS Dec 27 23:15:39 hbc postfix/smtp[2605]: vstream_fflush_some: fd 15 flush 10 Dec 27 23:15:39 hbc postfix/smtp[2605]: vstream_buf_get_ready: fd 15 got 30 Dec 27 23:15:39 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.108]:587: 220 2.0.0 Ready to start TLS Dec 27 23:15:39 hbc postfix/smtp[2605]: event_request_timer: reset 0x7f79a9113bb0 0x7f79aa8429d0 5 Dec 27 23:15:39 hbc postfix/smtp[2605]: send attr request = seed Dec 27 23:15:39 hbc postfix/smtp[2605]: send attr size = 32 Dec 27 23:15:39 hbc postfix/smtp[2605]: vstream_fflush_some: fd 9 flush 22 Dec 27 23:15:39 hbc postfix/smtp[2605]: vstream_buf_get_ready: fd 9 got 60 Dec 27 23:15:39 hbc postfix/smtp[2605]: private/tlsmgr: wanted attribute: status Dec 27 23:15:39 hbc postfix/smtp[2605]: input attribute name: status Dec 27 23:15:39 hbc postfix/smtp[2605]: input attribute value: 0 Dec 27 23:15:39 hbc postfix/smtp[2605]: private/tlsmgr: wanted attribute: seed Dec 27 23:15:39 hbc postfix/smtp[2605]: input attribute name: seed Dec 27 23:15:39 hbc postfix/smtp[2605]: input attribute value: Gvb7N21DayqKfDwTIIHM/2DY92tqdHFajB++bXjpXwE= Dec 27 23:15:39 hbc postfix/smtp[2605]: private/tlsmgr: wanted attribute: (list terminator) Dec 27 23:15:39 hbc postfix/smtp[2605]: input attribute name: (end) Dec 27 23:15:39 hbc postfix/smtp[2605]: > smtp.gmail.com[173.194.79.108]:587: EHLO hbc.hillcrest.org.nz Dec 27 23:15:39 hbc postfix/smtp[2605]: vstream_fflush_some: fd 15 flush 27 Dec 27 23:15:39 hbc postfix/smtp[2605]: vstream_buf_get_ready: fd 15 got 145 Dec 27 23:15:39 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.108]:587: 250-mx.google.com at your service, [121.75.4.39] Dec 27 23:15:39 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.108]:587: 250-SIZE 35882577 Dec 27 23:15:39 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.108]:587: 250-8BITMIME Dec 27 23:15:39 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.108]:587: 250-AUTH LOGIN PLAIN XOAUTH XOAUTH2 Dec 27 23:15:39 hbc postfix/smtp[2605]: < smtp.gmail.com[173.194.79.108]:587: 250 ENHANCEDSTATUSCODES Dec 27 23:15:39 hbc postfix/smtp[2605]: server features: 0x102b size 35882577 Dec 27 23:15:39 hbc postfix/smtp[2605]: maps_find: smtp_sasl_passwd: smtp.gmail.com: not found Dec 27 23:15:39 hbc postfix/smtp[2605]: maps_find: smtp_sasl_passwd: hash:/etc/postfix/sasl_passwd(0,lock|fold_fix): smtp.gmail.com:587 = <user>@ gmail.com:<correct password> Dec 27 23:15:39 hbc postfix/smtp[2605]: smtp_sasl_passwd_lookup: host ` smtp.gmail.com' user `' pass `' Dec 27 23:15:39 hbc postfix/smtp[2605]: starting new SASL client Dec 27 23:15:39 hbc postfix/smtp[2605]: name_mask: noanonymous Dec 27 23:15:39 hbc postfix/smtp[2605]: smtp_sasl_authenticate: smtp.gmail.com[173.194.79.108]:587: SASL mechanisms LOGIN PLAIN XOAUTH XOAUTH2 Dec 27 23:15:39 hbc postfix/smtp[2605]: warning: SASL authentication failure: No worthy mechs found Dec 27 23:15:39 hbc postfix/smtp[2605]: connect to subsystem private/defer Dec 27 23:15:39 hbc postfix/smtp[2605]: send attr nrequest = 0 Dec 27 23:15:39 hbc postfix/smtp[2605]: send attr flags = 0 Dec 27 23:15:39 hbc postfix/smtp[2605]: send attr queue_id = 8DEB1410B3 Dec 27 23:15:39 hbc postfix/smtp[2605]: send attr original_recipient = clint.dilks(a)gmail.com Dec 27 23:15:39 hbc postfix/smtp[2605]: send attr recipient = clint.dilks(a)gmail.com Dec 27 23:15:39 hbc postfix/smtp[2605]: send attr offset = 203 Dec 27 23:15:39 hbc postfix/smtp[2605]: send attr dsn_orig_rcpt = Dec 27 23:15:39 hbc postfix/smtp[2605]: send attr notify_flags = 0 Dec 27 23:15:39 hbc postfix/smtp[2605]: send attr status = 4.7.0 Dec 27 23:15:39 hbc postfix/smtp[2605]: send attr diag_type = x-sasl Dec 27 23:15:39 hbc postfix/smtp[2605]: send attr diag_text = no mechanism available Dec 27 23:15:39 hbc postfix/smtp[2605]: send attr mta_type = Dec 27 23:15:39 hbc postfix/smtp[2605]: send attr mta_mname = Dec 27 23:15:39 hbc postfix/smtp[2605]: send attr action = delayed Dec 27 23:15:39 hbc postfix/smtp[2605]: send attr reason = SASL authentication failed; cannot authenticate to server smtp.gmail.com[173.194.79.108]: no mechanism available Dec 27 23:15:39 hbc postfix/smtp[2605]: vstream_fflush_some: fd 16 flush 373 Dec 27 23:15:40 hbc postfix/smtp[2605]: vstream_buf_get_ready: fd 16 got 10 Dec 27 23:15:40 hbc postfix/smtp[2605]: private/defer socket: wanted attribute: status Dec 27 23:15:40 hbc postfix/smtp[2605]: input attribute name: status Dec 27 23:15:40 hbc postfix/smtp[2605]: input attribute value: 0 Dec 27 23:15:40 hbc postfix/smtp[2605]: private/defer socket: wanted attribute: (list terminator) Dec 27 23:15:40 hbc postfix/smtp[2605]: input attribute name: (end) Dec 27 23:15:40 hbc postfix/smtp[2605]: 8DEB1410B3: to=< clint.dilks(a)gmail.com>, relay=smtp.gmail.com[173.194.79.108]:587, delay=23, delays=20/0.04/3.3/0, dsn=4.7.0, status=deferred (SASL authentication failed; cannot authenticate to server smtp.gmail.com[173.194.79.108]: no mechanism available) Dec 27 23:15:40 hbc postfix/smtp[2605]: flush_add: site gmail.com id 8DEB1410B3 Dec 27 23:15:40 hbc postfix/smtp[2605]: match_hostname: gmail.com ~? hbc.hillcrest.org.nz Dec 27 23:15:40 hbc postfix/smtp[2605]: match_hostname: gmail.com ~? localhost.hillcrest.org.nz Dec 27 23:15:40 hbc postfix/smtp[2605]: match_hostname: gmail.com ~? localhost Dec 27 23:15:40 hbc postfix/smtp[2605]: match_list_match: gmail.com: no match Dec 27 23:15:40 hbc postfix/smtp[2605]: flush_add: site gmail.com id 8DEB1410B3 status 4 Dec 27 23:15:40 hbc postfix/smtp[2605]: > smtp.gmail.com[173.194.79.108]:587: QUIT Dec 27 23:15:40 hbc postfix/smtp[2605]: name_mask: resource Dec 27 23:15:40 hbc postfix/smtp[2605]: name_mask: software Dec 27 23:15:40 hbc postfix/smtp[2605]: vstream_fflush_some: fd 15 flush 6 Dec 27 23:15:40 hbc postfix/smtp[2605]: vstream_fflush_some: fd 15 flush 0 Dec 27 23:15:40 hbc postfix/smtp[2605]: disposing SASL state information My Postfix Config is currently alias_database = hash:/etc/aliases alias_maps = hash:/etc/aliases command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix data_directory = /var/lib/postfix debug_peer_level = 3 debug_peer_list = smtp.gmail.com html_directory = no inet_interfaces = localhost inet_protocols = all mail_owner = postfix mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man mydestination = $myhostname, localhost.$mydomain, localhost newaliases_path = /usr/bin/newaliases.postfix queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.6.6/README_FILES relayhost = smtp.gmail.com:587 sample_directory = /usr/share/doc/postfix-2.6.6/samples sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd smtp_sasl_security_options = noanonymous smtp_sasl_tls_security_options = noanonymous smtp_sasl_type = cyrus smtp_tls_CAfile = /etc/pki/tls/certs/ca-bundle.crt smtp_use_tls = yes smtpd_sasl_path = smtpd unknown_local_recipient_reject_code = 550 # rpm -qa | grep -i sasl cyrus-sasl-lib-2.1.23-13.el6_3.1.x86_64 cyrus-sasl-2.1.23-13.el6_3.1.x86_64 Any help appreciated :)

6 14

Re: [CentOS] Where is timezone string stored?
by Robert Moskowitz 28 Dec '12

28 Dec '12

On 12/27/2012 05:01 PM, Reindl Harald wrote: > > Am 27.12.2012 22:08, schrieb Robert Moskowitz: >> On 12/27/2012 03:26 PM, Reindl Harald wrote: >>> Am 27.12.2012 21:17, schrieb Robert Moskowitz: >>>> I am having problems with RoundCube: >>>> >>>> 'Your session is invalid or expired' >>>> >>>> So I went looking for logs and in /var/log/roundcube/errors I find LOTS >>>> of warnings about problems with my timezone. Kind of a challenge to >>>> copy the log entries over here (will do if needed). >>>> >>>> Anyway, for right now I am looking as to where my 'Detroit >>>> American/New_York' (what I am seeing in Gnomes calendar preferences) >>>> string is stored. >>>> >>>> Roundcube seems to want 'America/New_York'? >>>> >>>> Shouldn't I be seeing 'America/Detroit' when I look at the calendar >>>> selection in Gnome? >>> https://www.google.com/search?q=php+timezone >>> >>> php.ini: >>> date.timezone = "your-timezone" >> Not the place where Centos is storing timezone. Or perhaps this is where RoundCube is expecting it? > but the place where the timezone for php is configured > you may guess in which language roundcube is written I guessed this from looking at the roundcube errors. So now to dig up how to configure php, and not expect the packages that use it to configure such base requirements. Got to love it. > on a proper configured php-setup with full error-reporting > you get even warnings if the timezone is not configured, but > hey why should people enable warnings on their servers :-) Becuase we expect it to work right the first time! DIRTFT! Actually, there were some decent error messages from Roundcube: [27-Dec-2012 14:56:47] PHP Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /usr/share/roundcubemail/program/include/rcube_config.php on line 96 [27-Dec-2012 14:56:47] PHP Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /usr/share/roundcubemail/program/include/rcube_config.php on line 97 [27-Dec-2012 14:56:47] PHP Warning: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /usr/share/roundcubemail/program/include/rcube_session.php on line 134 [27-Dec-2012 14:56:47] PHP Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in /usr/share/roundcubemail/program/include/rcube_mdb2.php on line 603 So I have taken this problem over to the Roundcube list. But will dig into php configuration. Seems Roundcube is expecting more than say phpmysqladmin...

4 7

Excluding file systems from autorelabel
by James A. Peltier 28 Dec '12

28 Dec '12

I'm trying to find a way to exclude file systems during the autorelabel process. I have a file system (/exports) that has tens of millions of files on it and I *know* I don't want it relabeled. I've tried semanage fcontext -a -t "<<none>>" "/exports(/.*)?" and it seems to insist on relabeling that file system. I also tried to see if there was a /.autorelabel_exclude option as I saw some patches but can't seem to find indication of them anywhere (perhaps I missed it). I really need to make sure that I can exclude these massive directories if at all possible. Any help? -- James A. Peltier Manager, IT Services - Research Computing Group Simon Fraser University - Burnaby Campus Phone : 778-782-6573 Fax : 778-782-3045 E-Mail : jpeltier(a)sfu.ca Website : http://www.sfu.ca/itservices http://blogs.sfu.ca/people/jpeltier "The smartest people are constantly revising their understanding, reconsidering a problem they thought they’d already solved. They’re open to new points of view, new information, new ideas, contradictions, and challenges to their own way of thinking." - Jeff Bezos

6 10

Re: [CentOS] For what it is worth - Re: Where is timezone string stored?
by Robert Moskowitz 28 Dec '12

28 Dec '12

On 12/27/2012 07:42 PM, Reindl Harald wrote: > > Am 28.12.2012 01:38, schrieb Robert Moskowitz: >>> Roundcube isn't going to tell you to set the timezone in php.ini ... that's >>> an admin's job to have already done. >> I was not clear. It is quite apparent that Roundcube requires timezone >> set in php.ini. This is an application requirement > boah it is NOT an application requirement > > it is a BASIC requirment for any proper configured server > with PHP >= 5.3.0, as said: if you refuse to understand > basics of webserver-configuration please hire someone who does When I saw that I needed PHP for this setup, I began researching how to limit php usage to the apps installed. I have lots of reading on this. I know this is hard. I do have access to resources to harden this php setup. > with your "ignorance is a bliss"-attitude it is pretty clear that > you are also missing and ignoring security basics as so many out > there are doing while think the must setup their own server and > the result are botnets attacking thrid parties Ignorance is frustration. I have been reading steadily since I started on this a month ago. Just, it seems not dealing with the actual setup requirements. So far, I will start with limiting web access to local systems only. Remote systems will have to VPN in. This is only a start, I know there is more to do. If it was not for a couple users, I would not provide a webmail interface even with them having to VPN in.

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss