Discuss

discuss@lists.centos.org

8 participants
34745 discussions

Postfix, system notifications and local servers
by Nicolas Kovacs 28 Jun '18

28 Jun '18

Hi, I have CentOS 7 running on half a dozen public servers. For some stuff like automatic updates using yum-cron, I have Postfix installed with a relatively basic configuration. This allows me to send important notifications to my mail address info(a)microlinux.fr. When there's a batch of updates, I get one mail per machine, so I can check quickly if everything went OK without having to connect to the server. Now I'd also like to use this setup on machines that aren't in a datacenter and facing the Internet. For example, servers that have "dummy" hostnames like nestor.microlinux.lan or sauvegarde.scholae.lan. Is there a way I can setup Postfix so this machine can send an e-mail to info(a)microlinux.fr, even if 'hostname --fqdn' returns a "dummy" hostname? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

3 2

Install C7 on HP DL360e G8
by Jerry Geis 27 Jun '18

27 Jun '18

HI All - I am trying to install the above... The BIOS reports 1 virtual drive, but when C7 is installing there are 0 disks found. >From the hardware it says the raid card is a P420 ... I did a little searching and saw it talking about B320i card - which does not seem to be my card. I'm stuck. Any thoughts? Thanks, Jerry

3 3

Semi-OT: ipmitool or ipmicfg: set BMC to use NIC 2
by mark 26 Jun '18

26 Jun '18

The man page isn't helping, nor have I been able to find examples that work. For example, the man page claims I can do ipmitool lan get active, and I try, and it says, "invaling lan command, get". Do I set the MAC address for the lan to NIC 2? Anyone have a clue - I do *not* want martians on the real network. mark

2 4

Re: [CentOS] Semi-OT: ipmitool or ipmicfg: set BMC to use NIC 2
by mark 26 Jun '18

26 Jun '18

Michael C. Tiernan wrote: > ipmitool -I open lan get *NUMBER* > Description: CentOS Linux release 7.5.1804 (Core) Release: 7.5.1804 ipmitool -I open lan get 1 Invalid LAN command: get I'm saying that the get command with lan DOES NOT WORK. ipmitool doesn't understand it.... <SNIP> mark

1 0

lightdm + xorg.conf + nvidia driver
by Felix Kölzow 26 Jun '18

26 Jun '18

Hello CentOS-Community, I have to maintain a server that should be useable with VNC and some software requires to run VirtualGL. Also a nvidia graphic card is installed. After downloading and installing the nvidia driver from nvidias homepage and modifying the xorg.conf as mentioned on the virtualgL-homepage, I am not able to restart lightdm anymore. Lightdm should be running, otherwise it is not possible to run virtualgl in an appropriate way. I had the same/similar issues on three different servers with three different nvidia graphic cards. Any help is appreciated. Best Regards, Felix Kölzow ###### log files and xorg.conf ####### nvidia-detect leads to: [10de:11fa] NVIDIA Corporation GK106GL [Quadro K4000] This device requires the current 390.59 NVIDIA driver kmod-nvidia My xorg.conf file looks like: # nvidia-xconfig: X configuration file generated by nvidia-xconfig # nvidia-xconfig: version 390.59 (buildmeister@swio-display-x64-rhel04-13) Wed May 9 23:09:38 PDT 2018 Section "ServerLayout" Identifier "Layout0" Screen 0 "Screen0" InputDevice "Keyboard0" "CoreKeyboard" InputDevice "Mouse0" "CorePointer" EndSection Section "Files" FontPath "/usr/share/fonts/default/Type1" EndSection Section "InputDevice" # generated from default Identifier "Mouse0" Driver "mouse" Option "Protocol" "auto" Option "Device" "/dev/input/mice" Option "Emulate3Buttons" "no" Option "ZAxisMapping" "4 5" EndSection Section "InputDevice" # generated from default Identifier "Keyboard0" Driver "kbd" EndSection Section "Monitor" Identifier "Monitor0" VendorName "Unknown" ModelName "Unknown" HorizSync 28.0 - 33.0 VertRefresh 43.0 - 72.0 Option "DPMS" EndSection Section "Device" Identifier "Device0" Driver "nvidia" VendorName "NVIDIA Corporation" BusID "PCI:42:00:0" EndSection Section "Screen" Identifier "Screen0" Device "Device0" Monitor "Monitor0" DefaultDepth 24 SubSection "Display" Depth 24 EndSubSection EndSection and the lightdm.conf looks like: [root@sv199 X11]# cat /etc/lightdm/lightdm.conf # # General configuration # # start-default-seat = True to always start one seat if none are defined in the configuration # greeter-user = User to run greeter as # minimum-display-number = Minimum display number to use for X servers # minimum-vt = First VT to run displays on # lock-memory = True to prevent memory from being paged to disk # user-authority-in-system-dir = True if session authority should be in the system location # guest-account-script = Script to be run to setup guest account # logind-check-graphical = True to on start seats that are marked as graphical by logind # log-directory = Directory to log information to # run-directory = Directory to put running state in # cache-directory = Directory to cache to # sessions-directory = Directory to find sessions # remote-sessions-directory = Directory to find remote sessions # greeters-directory = Directory to find greeters # backup-logs = True to move add a .old suffix to old log files when opening new ones # dbus-service = True if LightDM provides a D-Bus service to control it # [LightDM] #start-default-seat=true #greeter-user=lightdm #minimum-display-number=0 #minimum-vt=7 #lock-memory=true #user-authority-in-system-dir=false #guest-account-script=guest-account #logind-check-graphical=false #log-directory=/var/log/lightdm #run-directory=/var/run/lightdm #cache-directory=/var/cache/lightdm #sessions-directory=/usr/share/lightdm/sessions:/usr/share/xsessions:/usr/share/wayland-sessions #remote-sessions-directory=/usr/share/lightdm/remote-sessions #greeters-directory=$XDG_DATA_DIRS/lightdm/greeters:$XDG_DATA_DIRS/xgreeters greeters-directory=/usr/share/xgreeters/ #backup-logs=true #dbus-service=true # # Seat configuration # # Seat configuration is matched against the seat name glob in the section, for example: # [Seat:*] matches all seats and is applied first. # [Seat:seat0] matches the seat named "seat0". # [Seat:seat-thin-client*] matches all seats that have names that start with "seat-thin-client". # # type = Seat type (local, xremote, unity) # pam-service = PAM service to use for login # pam-autologin-service = PAM service to use for autologin # pam-greeter-service = PAM service to use for greeters # xserver-backend = X backend to use (mir) # xserver-command = X server command to run (can also contain arguments e.g. X -special-option) # xmir-command = Xmir server command to run (can also contain arguments e.g. Xmir -special-option) # xserver-config = Config file to pass to X server # xserver-layout = Layout to pass to X server # xserver-allow-tcp = True if TCP/IP connections are allowed to this X server # xserver-share = True if the X server is shared for both greeter and session # xserver-hostname = Hostname of X server (only for type=xremote) # xserver-display-number = Display number of X server (only for type=xremote) # xdmcp-manager = XDMCP manager to connect to (implies xserver-allow-tcp=true) # xdmcp-port = XDMCP UDP/IP port to communicate on # xdmcp-key = Authentication key to use for XDM-AUTHENTICATION-1 (stored in keys.conf) # unity-compositor-command = Unity compositor command to run (can also contain arguments e.g. unity-system-compositor -special-option) # unity-compositor-timeout = Number of seconds to wait for compositor to start # greeter-session = Session to load for greeter # greeter-hide-users = True to hide the user list # greeter-allow-guest = True if the greeter should show a guest login option # greeter-show-manual-login = True if the greeter should offer a manual login option # greeter-show-remote-login = True if the greeter should offer a remote login option # user-session = Session to load for users # allow-user-switching = True if allowed to switch users # allow-guest = True if guest login is allowed # guest-session = Session to load for guests (overrides user-session) # session-wrapper = Wrapper script to run session with # greeter-wrapper = Wrapper script to run greeter with # guest-wrapper = Wrapper script to run guest sessions with # display-stopped-script = Script to run after stopping the display server (runs as root) # greeter-setup-script = Script to run when starting a greeter (runs as root) # session-setup-script = Script to run when starting a user session (runs as root) # session-cleanup-script = Script to run when quitting a user session (runs as root) # autologin-guest = True to log in as guest by default # autologin-user = User to log in with by default (overrides autologin-guest) # autologin-user-timeout = Number of seconds to wait before loading default user # autologin-session = Session to load for automatic login (overrides user-session) # autologin-in-background = True if autologin session should not be immediately activated # exit-on-failure = True if the daemon should exit if this seat fails # [Seat:*] #type=local #pam-service=lightdm #pam-autologin-service=lightdm-autologin #pam-greeter-service=lightdm-greeter #xserver-backend= #xserver-command=X #xmir-command=Xmir #xserver-config= #xserver-layout= #xserver-allow-tcp=false #xserver-share=true #xserver-hostname= #xserver-display-number= #xdmcp-manager= #xdmcp-port=177 #xdmcp-key= #unity-compositor-command=unity-system-compositor #unity-compositor-timeout=60 #greeter-session=lightdm-slick-greeter #greeter-hide-users=false #greeter-allow-guest=true #greeter-show-manual-login=false #greeter-show-remote-login=true #user-session=default #allow-user-switching=true #allow-guest=true #guest-session= #session-wrapper=lightdm-session #greeter-wrapper= #guest-wrapper= #display-stopped-script= #greeter-setup-script= #session-setup-script= #session-cleanup-script= #autologin-guest=false #autologin-user= #autologin-user-timeout=0 #autologin-in-background=false #autologin-session= #exit-on-failure=false # # XDMCP Server configuration # # enabled = True if XDMCP connections should be allowed # port = UDP/IP port to listen for connections on # listen-address = Host/address to listen for XDMCP connections (use all addresses if not present) # key = Authentication key to use for XDM-AUTHENTICATION-1 or blank to not use authentication (stored in keys.conf) # hostname = Hostname to report to XDMCP clients (defaults to system hostname if unset) # # The authentication key is a 56 bit DES key specified in hex as 0xnnnnnnnnnnnnnn. Alternatively # it can be a word and the first 7 characters are used as the key. # [XDMCPServer] #enabled=false #port=177 #listen-address= #key= #hostname= # # VNC Server configuration # # enabled = True if VNC connections should be allowed # command = Command to run Xvnc server with # port = TCP/IP port to listen for connections on # listen-address = Host/address to listen for VNC connections (use all addresses if not present) # width = Width of display to use # height = Height of display to use # depth = Color depth of display to use # [VNCServer] #enabled=false #command=Xvnc #port=5900 #listen-address= #width=1024 #height=768 #depth=8 [SeatDefaults] display-setup-script=xhost +LOCAL: This is lightdm.log file looks like: [root@sv199 X11]# cat /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Logging to /var/log/lightdm/lightdm.log [+0.00s] DEBUG: Starting Light Display Manager 1.25.0, UID=0 PID=3411 [+0.00s] DEBUG: Loading configuration dirs from /usr/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-backup-logs.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-disable-guest.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-minimum-vt.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-session-wrapper.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-user-authority-in-system-dir.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/50-xserver-command.conf [+0.00s] DEBUG: Loading configuration from /usr/share/lightdm/lightdm.conf.d/90-slick-greeter.conf [+0.00s] DEBUG: Loading configuration dirs from /usr/local/share/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration dirs from /etc/xdg/lightdm/lightdm.conf.d [+0.00s] DEBUG: Loading configuration from /etc/lightdm/lightdm.conf [+0.00s] DEBUG: [SeatDefaults] is now called [Seat:*], please update this configuration [+0.00s] DEBUG: Registered seat module local [+0.00s] DEBUG: Registered seat module xremote [+0.00s] DEBUG: Registered seat module unity [+0.00s] DEBUG: Using D-Bus name org.freedesktop.DisplayManager [+0.00s] DEBUG: Monitoring logind for seats [+0.00s] DEBUG: New seat added from logind: seat0 [+0.00s] DEBUG: Seat seat0: Loading properties from config section Seat:* [+0.00s] DEBUG: Seat seat0: Starting [+0.00s] DEBUG: Seat seat0: Creating greeter session [+0.00s] DEBUG: Seat seat0: Creating display server of type x [+0.01s] DEBUG: Using VT 1 [+0.01s] DEBUG: Seat seat0: Starting local X display on VT 1 [+0.01s] DEBUG: XServer 0: Logging to /var/log/lightdm/x-0.log [+0.01s] DEBUG: XServer 0: Writing X server authority to /var/run/lightdm/root/:0 [+0.01s] DEBUG: XServer 0: Launching X Server [+0.01s] DEBUG: Launching process 3417: /usr/bin/X -core -noreset :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt1 -novtswitch -background none [+0.01s] DEBUG: XServer 0: Waiting for ready signal from X server :0 [+0.01s] DEBUG: Acquired bus name org.freedesktop.DisplayManager [+0.01s] DEBUG: Registering seat with bus path /org/freedesktop/DisplayManager/Seat0 [+0.01s] DEBUG: Loading users from org.freedesktop.Accounts [+0.01s] DEBUG: User /org/freedesktop/Accounts/User1000 added [+0.01s] DEBUG: User /org/freedesktop/Accounts/User1002 added [+0.01s] DEBUG: User /org/freedesktop/Accounts/User1003 added [+0.01s] DEBUG: User /org/freedesktop/Accounts/User1001 added [+0.09s] DEBUG: Process 3417 terminated with signal 6 [+0.09s] DEBUG: XServer 0: X server stopped [+0.09s] DEBUG: Releasing VT 1 [+0.09s] DEBUG: XServer 0: Removing X server authority /var/run/lightdm/root/:0 [+0.09s] DEBUG: Seat seat0: Display server stopped [+0.09s] DEBUG: Seat seat0: Stopping session [+0.09s] DEBUG: Seat seat0: Session stopped [+0.09s] DEBUG: Seat seat0: Stopping display server, no sessions require it [+0.09s] DEBUG: Seat seat0: Stopping; greeter display server failed to start [+0.09s] DEBUG: Seat seat0: Stopping [+0.09s] DEBUG: Seat seat0: Stopped [+0.09s] DEBUG: Required seat has stopped [+0.09s] DEBUG: Stopping display manager [+0.09s] DEBUG: Display manager stopped [+0.09s] DEBUG: Stopping daemon [+0.09s] DEBUG: Exiting with return value 1

3 2

dumb shared library question
by Alice Wonder 26 Jun '18

26 Jun '18

Binary compiled on a system with ggc 5.5.0 w/ libstdc++.so.6.0.21 Because the major version is libstdc++.so.6 there shouldn't be any problems running it on CentOS 7 with libstdc++.so.6.0.19, right?

2 1

Specifying different options for different " smb" type gvfs mount
by Toralf Lund 26 Jun '18

26 Jun '18

Hi, I'm trying to use smb:// URLs with gvfs-mount and/or similar desktop functionality to access SMB shares on different servers that support different protocol versions and features. With some of the servers, mount will fail with a default configuration, but I have been able to make it work by editing some of the "client" options in /etc/samba/smb.conf. The problem is, those changes will cause the operation to fail on other servers; I can't seem to find a combination of settings where all shares will work. Does anyone know if there is an alternative way to specify client options that will apply to only specific URLs/shares, and not everything of SMB type? Note that I might be able to get by if I could set the "max protocol" individually for the different file-systems or URLs. I known that I might use mount.cifs and related "fstab" entries as an alternative, but its password handling seems a lot less convenient. I'm on a CentOS 7 system where all updates had been applied as of a few days ago. Thanks, - Toralf

4 7

Dolphin fails to refresh files (cont'd)
by Nicolas Kovacs 25 Jun '18

25 Jun '18

Hi, Some time ago I reported a problem with Dolphin on bugs.centos.org. When extracting an archive, the new files don't appear, and I have to press F5 to refresh the current directory display. I just found out a specificity of this bug. This only seem to happen on those installations where I run the 4.4.x kernel (kernel-lt package from elrepo-kernel repository). Any idea how I could solve that problem ? Cheers, Niki -- Microlinux - Solutions informatiques durables 7, place de l'église - 30730 Montpezat Site : https://www.microlinux.fr Blog : https://blog.microlinux.fr Mail : info(a)microlinux.fr Tél. : 04 66 63 10 32

1 0

Re: [CentOS] NetworkManager updating resolv.cfg
by Maheshwari, Shagun 25 Jun '18

25 Jun '18

Hi, It will be bug on &.2 but we are facing this issue on CentOS 6.8. In 6.8 also has this issue? Please suggest. Regards, Shagun -----Original Message----- From: CentOS [mailto:centos-bounces@centos.org] On Behalf Of centos-request(a)centos.org Sent: Friday, June 22, 2018 5:30 PM To: centos(a)centos.org Subject: [EXTERNAL] CentOS Digest, Vol 161, Issue 22 Send CentOS mailing list submissions to centos(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit https://clicktime.symantec.com/a/1/GaRh-9mT7pT2BGk25Szya6j4lyfBTXokdCA6hocG… or, via email, send a message with subject or body 'help' to centos-request(a)centos.org You can reach the person managing the list at centos-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS digest..." Today's Topics: 1. Re: Specifying different options for different " smb" type gvfs mount (John Hodrien) 2. Re: NetworkManager updating resolv.cfg (peter.winterflood) 3. Re: Updated krb5 rpm package altered existing krb5.conf - No go (G?tz Reinicke) 4. Re: CentOS-6.9 Bind-9.8.2 error messages (James B. Byrne) 5. Imap daemons for CentOS 6 (other then cyrus-imapd) (Robert Heller) 6. Re: Imap daemons for CentOS 6 (other then cyrus-imapd) (James (CentOS ML)) 7. Re: Imap daemons for CentOS 6 (other then cyrus-imapd) (Frank Cox) 8. Re: Imap daemons for CentOS 6 (other then cyrus-imapd) (Walter H.) 9. Re: Imap daemons for CentOS 6 (other then cyrus-imapd) (Jonathan Billings) 10. Re: Specifying different options for different " smb" type gvfs mount (Gordon Messmer) 11. Re: Imap daemons for CentOS 6 (other then cyrus-imapd) (Robert Heller) 12. Re: Imap daemons for CentOS 6 (other then cyrus-imapd) (Valeri Galtsev) 13. Re: Imap daemons for CentOS 6 (other then cyrus-imapd) (Marcelo Ricardo Leitner) 14. Re: Imap daemons for CentOS 6 (other then cyrus-imapd) (Valeri Galtsev) 15. Re: Imap daemons for CentOS 6 (other then cyrus-imapd) (Jonathan Billings) 16. Re: Specifying different options for different " smb" type gvfs mount (John Hodrien) 17. Re: Imap daemons for CentOS 6 (other then cyrus-imapd) (Walter H.) 18. Re: Imap daemons for CentOS 6 (other then cyrus-imapd) (Walter H.) ---------------------------------------------------------------------- Message: 1 Date: Thu, 21 Jun 2018 13:09:38 +0100 (BST) From: John Hodrien <J.H.Hodrien(a)leeds.ac.uk> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] Specifying different options for different " smb" type gvfs mount Message-ID: <nycvar.YEU.7.76.1806211308500.31795(a)pbzc-cp3201.yrrqf.np.hx> Content-Type: text/plain; charset=US-ASCII; format=flowed On Thu, 21 Jun 2018, Toralf Lund wrote: > I known that I might use mount.cifs and related "fstab" entries as an > alternative, but its password handling seems a lot less convenient. If you're in an AD environment, you can probably do nicely with mount.cifs: sec=krb5,multiuser That way you don't have to deal with usernames/passwords at all. jh ------------------------------ Message: 2 Date: Thu, 21 Jun 2018 13:14:08 +0100 From: "peter.winterflood" <peter.winterflood(a)ossi.co.uk> To: CentOS mailing list <centos(a)centos.org>, anax <anax(a)ayni.com> Subject: Re: [CentOS] NetworkManager updating resolv.cfg Message-ID: <16422442280.27db.2b6837a33dad96cb17d193f32630f285(a)ossi.co.uk> Content-Type: text/plain; format=flowed; charset="us-ascii" On 21 June 2018 12:13:02 "anax" <anax(a)ayni.com> wrote: > Hi Shagun > check your settings of PEERDNS and IPV6_PEERDNS... > > suomi > > On 06/21/2018 08:33 AM, Maheshwari, Shagun wrote: >> Hi, >> >> I am facing issue stoping NetworkManager to update resolv.cfg, I am >> using below configuration for eth0 interface: >> >> TYPE=Ethernet >> BOOTPROTO=dhcp >> DEFROUTE=yes >> IPV4_FAILURE_FATAL=no >> IPV6INIT=yes >> IPV6_AUTOCONF=yes >> IPV6_DEFROUTE=yes >> IPV6_FAILURE_FATAL=no >> IPV6_ADDR_GEN_MODE=stable-privacy >> NAME=eth0 >> UUID=93b90a46-dab5-4a67-8fd0-fefe8874a8b9 >> DEVICE=eth0 >> ONBOOT=no >> PEERDNS=no >> PEERROUTES=yes >> IPV6_PEERDNS=yes >> IPV6_PEERROUTES=yes >> DNS1=<ipv4 address> >> DNS2=<ipv6 address> >> >> >> Also, added dns=none in NetworkManager.conf file. >> >> Whenever I am restarting NetworkManager, resolv.cfg gets updated and >> only >> ipv4 nameserver is displaced, whether I am expecting both the ips >> (ipv6 and >> ipv4 address to be present in resolv.cfg file. >> >> Any suggestion here, how to achieve that?? >> >> Regards, >> Shagun >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://clicktime.symantec.com/a/1/GaRh-9mT7pT2BGk25Szya6j4lyfBTXokdC >> A6hocGAkM=?d=jdUOEa0ursy6vviA72Wp9CQyzmNZP0ZhevOrPVBV93kfSdUe78CIUBKV >> Vt6xyIm5Y6SyitPu2KPA0ZGPNr5i96qIZELuM-zDuX-IcuPAbZtv9AIDkJ5sr21UTb0Pj >> QLFAB288PhGEyycPWXt6EcXQP4v75ttvql-G_l869C_llOrrtHDCxvG5N4tEBkTHwMA0Y >> 2NdN16Xz3TyRWMbTpUywmcFKgiWH39hDRz50bU4bEX5OoEqu5GwbkgYVm0wClHPhkWTB6 >> s2ljnB-_WaTuJTIyAqE92od3J9izxcFd-XfdbM8iNC4zZhyaL9UZinHIkddJdNI0zq8RF >> ZXXiXP90NcKqdy9-sKPHjq12lAdprOZoFtvUCIJXX3NKhw%3D%3D&u=https%3A%2F%2F >> lists.centos.org%2Fmailman%2Flistinfo%2Fcentos >> > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://clicktime.symantec.com/a/1/GaRh-9mT7pT2BGk25Szya6j4lyfBTXokdCA > 6hocGAkM=?d=jdUOEa0ursy6vviA72Wp9CQyzmNZP0ZhevOrPVBV93kfSdUe78CIUBKVVt > 6xyIm5Y6SyitPu2KPA0ZGPNr5i96qIZELuM-zDuX-IcuPAbZtv9AIDkJ5sr21UTb0PjQLF > AB288PhGEyycPWXt6EcXQP4v75ttvql-G_l869C_llOrrtHDCxvG5N4tEBkTHwMA0Y2NdN > 16Xz3TyRWMbTpUywmcFKgiWH39hDRz50bU4bEX5OoEqu5GwbkgYVm0wClHPhkWTB6s2ljn > B-_WaTuJTIyAqE92od3J9izxcFd-XfdbM8iNC4zZhyaL9UZinHIkddJdNI0zq8RFZXXiXP > 90NcKqdy9-sKPHjq12lAdprOZoFtvUCIJXX3NKhw%3D%3D&u=https%3A%2F%2Flists.c > entos.org%2Fmailman%2Flistinfo%2Fcentos I think this was a bug in 7.2 have you updated your rpms. Peerdns ignored. Regards peter Sent with AquaMail for Android https://clicktime.symantec.com/a/1/dZe0_kxJdxrnAK4hEWUQEI2odnKSB2kkoxl3Vuci… ------------------------------ Message: 3 Date: Thu, 21 Jun 2018 16:24:04 +0200 From: G?tz Reinicke <goetz.reinicke(a)filmakademie.de> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] Updated krb5 rpm package altered existing krb5.conf - No go Message-ID: <45ACB559-6295-4269-97EC-7353970C9F6F(a)filmakademie.de> Content-Type: text/plain; charset=utf-8 > Am 18.06.2018 um 16:33 schrieb me(a)tdiehl.org: > > On Mon, 18 Jun 2018, G?tz Reinicke wrote: > >> >> >>> Am 15.06.2018 um 01:04 schrieb Gordon Messmer <gordon.messmer(a)gmail.com>: >>> >>> On 06/14/2018 09:30 AM, me(a)tdiehl.org wrote: >>>> On Thu, 14 Jun 2018, Richard Grainger wrote: >>>> >>>>> I looked at the spec file in the source RPM for the krb5-libs >>>>> package and it it has the correct %config(noreplace) directive >>>>> next to that file in the %files section, so this is mysterious. >>>> >>>> I too can confirm this behavior. >>> >>> # rpm -qa krb\* --triggers >>> triggerun scriptlet (using /bin/sh) -- krb5-libs < 1.15.1-13 if ! >>> grep -q 'includedir /etc/krb5.conf.d' /etc/krb5.conf ; then >>> sed -i '1i # Other applications require this directory to perform >>> krb5 configuration.\nincludedir /etc/krb5.conf.d/\n' /etc/krb5.conf >>> fi >>> >>> >>> Looks like that's the culprit. >> >> >> Good to know, but writing a rpmnew or rpmsave file would be nice to check against the life used file. > > Agreed! IMO this is a packaging bug. Triggers do not drop rpmsave > files. I suspect the chances of getting Red Hat to fix it are slim to none. Fixing it would most likely break other things for them. > >> >> The samba people are aware of that problem regarding the include line and are working on a patch ? the support at SerNet told me. > > I agree they are aware of it but I suspect it is a low priority thing > given they have known about this since 2016-12-29. > > I do think it would be relatively easy for SerNet to patch around in > their paid for rpms. alas I do not have the budget for them. :-( > > The bug is available at > https://clicktime.symantec.com/a/1/VxaZZYzfeWRqqUBqdb5dituD6zJkUGPZLQ4 > oVo5wQHg=?d=jdUOEa0ursy6vviA72Wp9CQyzmNZP0ZhevOrPVBV93kfSdUe78CIUBKVVt > 6xyIm5Y6SyitPu2KPA0ZGPNr5i96qIZELuM-zDuX-IcuPAbZtv9AIDkJ5sr21UTb0PjQLF > AB288PhGEyycPWXt6EcXQP4v75ttvql-G_l869C_llOrrtHDCxvG5N4tEBkTHwMA0Y2NdN > 16Xz3TyRWMbTpUywmcFKgiWH39hDRz50bU4bEX5OoEqu5GwbkgYVm0wClHPhkWTB6s2ljn > B-_WaTuJTIyAqE92od3J9izxcFd-XfdbM8iNC4zZhyaL9UZinHIkddJdNI0zq8RFZXXiXP > 90NcKqdy9-sKPHjq12lAdprOZoFtvUCIJXX3NKhw%3D%3D&u=https%3A%2F%2Fbugzill > a.samba.org%2Fshow_bug.cgi%3Fid%3D12488 > <https://clicktime.symantec.com/a/1/VxaZZYzfeWRqqUBqdb5dituD6zJkUGPZLQ > 4oVo5wQHg=?d=jdUOEa0ursy6vviA72Wp9CQyzmNZP0ZhevOrPVBV93kfSdUe78CIUBKVV > t6xyIm5Y6SyitPu2KPA0ZGPNr5i96qIZELuM-zDuX-IcuPAbZtv9AIDkJ5sr21UTb0PjQL > FAB288PhGEyycPWXt6EcXQP4v75ttvql-G_l869C_llOrrtHDCxvG5N4tEBkTHwMA0Y2Nd > N16Xz3TyRWMbTpUywmcFKgiWH39hDRz50bU4bEX5OoEqu5GwbkgYVm0wClHPhkWTB6s2lj > nB-_WaTuJTIyAqE92od3J9izxcFd-XfdbM8iNC4zZhyaL9UZinHIkddJdNI0zq8RFZXXiX > P90NcKqdy9-sKPHjq12lAdprOZoFtvUCIJXX3NKhw%3D%3D&u=https%3A%2F%2Fbugzil > la.samba.org%2Fshow_bug.cgi%3Fid%3D12488> Patched https://clicktime.symantec.com/a/1/HFkDaIm7MZYydWwFqssly0lRa9BWoWEEbokgCi9n… <https://clicktime.symantec.com/a/1/HFkDaIm7MZYydWwFqssly0lRa9BWoWEEbokgCi9n…> /G?tz ------------------------------ Message: 4 Date: Thu, 21 Jun 2018 12:31:56 -0400 From: "James B. Byrne" <byrnejb(a)harte-lyne.ca> To: "Gordon Messmer" <gordon.messmer(a)gmail.com> Cc: centos(a)centos.org Subject: Re: [CentOS] CentOS-6.9 Bind-9.8.2 error messages Message-ID: <2720c48e462a326dad3d716c31325f43.squirrel(a)webmail.harte-lyne.ca> Content-Type: text/plain;charset=iso-8859-1 On Wed, June 20, 2018 15:37, Gordon Messmer wrote: > On 06/20/2018 11:19 AM, James B. Byrne via CentOS wrote: >> I am encountering messages similar to this in the system logfile: >> >> Jun 20 13:38:18 inet03 named[3720]: malformed transaction: >> dynamic/efa1f375d76194fa51a3556a97e641e61685f914d446979da50a551a4333f >> fd7.mkeys.jnl last serial 103538 != transaction first serial 103361 >> >> I have no idea what this means, what caused it, nor how to fix it. >> Any suggestions relevant to any of the above are most welcome. >> > > I think I've seen this before.?? Are you auto-signing a zone for > DNSSEC, Yes > and does that zone appear in multiple views? No I stopped and restarted the BIND daemon and this appears to have corrected whatever issue was causing the errors to be generated. -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail Do NOT open attachments nor follow links sent by e-Mail James B. Byrne mailto:ByrneJB@Harte-Lyne.ca Harte & Lyne Limited https://clicktime.symantec.com/a/1/3qm1WpYWfhhR3CL-f_FUJqUD_XpMj733hnnofUT2… 9 Brockley Drive vox: +1 905 561 1241 Hamilton, Ontario fax: +1 905 561 0757 Canada L8E 3C3 ------------------------------ Message: 5 Date: Thu, 21 Jun 2018 13:28:38 -0400 (EDT) From: Robert Heller <heller(a)deepsoft.com> To: centos(a)centos.org <centos(a)centos.org> Subject: [CentOS] Imap daemons for CentOS 6 (other then cyrus-imapd) Message-ID: <20180621172838.D768226C2619(a)sharky3.deepsoft.com> Are there any imap daemons (besides cyrus-imapd). cyrus-imapd is appearently not compatible with postfix + procmail. I need an imap daemon that will work with a postfix + procmail system. -- Robert Heller -- 978-544-6933 Deepwoods Software -- Custom Software Services https://clicktime.symantec.com/a/1/eGcBdmqkFYbaGxldXqPflUsBamhj9GghI-bEbhZq… -- Linux Administration Services heller(a)deepsoft.com -- Webhosting Services ------------------------------ Message: 6 Date: Thu, 21 Jun 2018 13:32:16 -0400 From: "James (CentOS ML)" <centos(a)edwards.technology> To: CentOS mailing list <centos(a)centos.org> Cc: Robert Heller <heller(a)deepsoft.com> Subject: Re: [CentOS] Imap daemons for CentOS 6 (other then cyrus-imapd) Message-ID: <b979bb1c0e1247e3b3e0b2e0de223952(a)edwards.technology> Content-Type: text/plain; charset=US-ASCII; format=flowed On 2018-06-21 13:28, Robert Heller wrote: > Are there any imap daemons (besides cyrus-imapd). cyrus-imapd is > appearently not compatible with postfix + procmail. I need an imap > daemon that will work with a postfix + procmail system. Try dovecot, I use that personally. There also appears to be good documentation for dovecot+procmail as well - https://clicktime.symantec.com/a/1/2p8upgUG3dyM_D-qXYLbNH70qIQuJaYvhV0kviNB… ------------------------------ Message: 7 Date: Thu, 21 Jun 2018 11:34:18 -0600 From: Frank Cox <theatre(a)sasktel.net> To: centos(a)centos.org Subject: Re: [CentOS] Imap daemons for CentOS 6 (other then cyrus-imapd) Message-ID: <20180621113418.d7bd532565881109733f561e(a)sasktel.net> Content-Type: text/plain; charset=US-ASCII On Thu, 21 Jun 2018 13:28:38 -0400 (EDT) Robert Heller wrote: > Are there any imap daemons (besides cyrus-imapd). cyrus-imapd is appearently > not compatible with postfix + procmail. I need an imap daemon that will work > with a postfix + procmail system. I use dovecot with postfix and procmail; works fine. -- MELVILLE THEATRE ~ Real D 3D Digital Cinema ~ www.melvilletheatre.com ------------------------------ Message: 8 Date: Thu, 21 Jun 2018 20:42:50 +0200 From: "Walter H." <Walter.H(a)mathemainzel.info> To: centos(a)centos.org Subject: Re: [CentOS] Imap daemons for CentOS 6 (other then cyrus-imapd) Message-ID: <5B2BF1AA.5030007(a)mathemainzel.info> Content-Type: text/plain; charset=ISO-8859-1; format=flowed On 21.06.2018 19:28, Robert Heller wrote: > Are there any imap daemons (besides cyrus-imapd). cyrus-imapd is appearently > not compatible with postfix + procmail. I need an imap daemon that will work > with a postfix + procmail system. > the problem seems to be procmail, I use postfix and cyrus-imapd with no problems; ------------------------------ Message: 9 Date: Thu, 21 Jun 2018 14:49:09 -0400 From: Jonathan Billings <billings(a)negate.org> To: centos(a)centos.org Subject: Re: [CentOS] Imap daemons for CentOS 6 (other then cyrus-imapd) Message-ID: <20180621184909.GE1693(a)caen-tethys.engin.umich.edu> Content-Type: text/plain; charset=us-ascii On Thu, Jun 21, 2018 at 01:28:38PM -0400, Robert Heller wrote: > > Are there any imap daemons (besides cyrus-imapd). cyrus-imapd is > appearently not compatible with postfix + procmail. I need an imap > daemon that will work with a postfix + procmail system. I suggest dovecot if you don't want to deal with Cyrus IMAP, but I can tell you from first-hand experience that you used to be able to use procmail to deliver to Cyrus IMAP, using 'deliver'. However, if you get postfix to deliver directly via lmtp, you can take advantage of SIEVE to filter your mail, which is quite powerful. (I miss it, work migrated to Google Apps and its filters are subpar.) -- Jonathan Billings <billings(a)negate.org> ------------------------------ Message: 10 Date: Thu, 21 Jun 2018 13:03:03 -0700 From: Gordon Messmer <gordon.messmer(a)gmail.com> To: centos(a)centos.org Subject: Re: [CentOS] Specifying different options for different " smb" type gvfs mount Message-ID: <b038b2e3-4f15-6890-3264-f11ca1136b88(a)gmail.com> Content-Type: text/plain; charset=utf-8; format=flowed On 06/21/2018 05:09 AM, John Hodrien wrote: > On Thu, 21 Jun 2018, Toralf Lund wrote: > >> I known that I might use mount.cifs and related "fstab" entries as an >> alternative, but its password handling seems a lot less convenient. > > If you're in an AD environment, you can probably do nicely with > mount.cifs: > sec=krb5,multiuser > That way you don't have to deal with usernames/passwords at all. Interesting.? Seems like a lot of setup, but it's interesting.? I didn't know SMB supported this: https://clicktime.symantec.com/a/1/C-MtUYKskiDqrOo6AjZ3TiEoE538EEMOIEdNoqih… ------------------------------ Message: 11 Date: Thu, 21 Jun 2018 17:23:31 -0400 (EDT) From: Robert Heller <heller(a)deepsoft.com> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] Imap daemons for CentOS 6 (other then cyrus-imapd) Message-ID: <20180621212332.3ECAA26C288A(a)sharky3.deepsoft.com> At Thu, 21 Jun 2018 20:42:50 +0200 CentOS mailing list <centos(a)centos.org> wrote: > > On 21.06.2018 19:28, Robert Heller wrote: > > Are there any imap daemons (besides cyrus-imapd). cyrus-imapd is appearently > > not compatible with postfix + procmail. I need an imap daemon that will work > > with a postfix + procmail system. > > > the problem seems to be procmail, I use postfix and cyrus-imapd with no > problems; No actually the problem is cyrus-imapd: cyrus-imapd expects all users to use imap (or pop3) to access their E-Mail. It does not allow for other E-Mail methodologies, including using local UNIX utilies (eg mail or pine or mh or other tools like QWK). I have uninstalled cyrus-imapd and installed dovecot instead. This actually works. dovecot is even happy to use a Let's Encrypt cert for SSL. > > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://clicktime.symantec.com/a/1/GaRh-9mT7pT2BGk25Szya6j4lyfBTXokdCA6hocG… > > -- Robert Heller -- 978-544-6933 Deepwoods Software -- Custom Software Services https://clicktime.symantec.com/a/1/eGcBdmqkFYbaGxldXqPflUsBamhj9GghI-bEbhZq… -- Linux Administration Services heller(a)deepsoft.com -- Webhosting Services ------------------------------ Message: 12 Date: Thu, 21 Jun 2018 16:29:29 -0500 From: Valeri Galtsev <galtsev(a)kicp.uchicago.edu> To: centos(a)centos.org Subject: Re: [CentOS] Imap daemons for CentOS 6 (other then cyrus-imapd) Message-ID: <aa9ec9d3-e762-3c2b-91ba-ea50e7b9ded9(a)kicp.uchicago.edu> Content-Type: text/plain; charset=utf-8; format=flowed On 06/21/18 16:23, Robert Heller wrote: > At Thu, 21 Jun 2018 20:42:50 +0200 CentOS mailing list <centos(a)centos.org> wrote: > >> >> On 21.06.2018 19:28, Robert Heller wrote: >>> Are there any imap daemons (besides cyrus-imapd). cyrus-imapd is appearently >>> not compatible with postfix + procmail. I need an imap daemon that will work >>> with a postfix + procmail system. >>> >> the problem seems to be procmail, I use postfix and cyrus-imapd with no >> problems; > > No actually the problem is cyrus-imapd: cyrus-imapd expects all users to use > imap (or pop3) to access their E-Mail. It does not allow for other E-Mail > methodologies, including using local UNIX utilies (eg mail or pine or mh or > other tools like QWK). > > I have uninstalled cyrus-imapd and installed dovecot instead. This actually > works. dovecot is even happy to use a Let's Encrypt cert for SSL. I use postfix + dovecot since forever. I recently switched from amavisd-new to maia. It probably is same simple on Linux as it is on FreeBSD - I have servers under FreeBSD (or rather multiple jails on FreeBSD box). Good luck! Valeri > >> >> _______________________________________________ >> CentOS mailing list >> CentOS(a)centos.org >> https://clicktime.symantec.com/a/1/GaRh-9mT7pT2BGk25Szya6j4lyfBTXokdCA6hocG… >> >> > -- ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ ------------------------------ Message: 13 Date: Thu, 21 Jun 2018 18:46:01 -0300 From: Marcelo Ricardo Leitner <marcelo.leitner(a)gmail.com> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] Imap daemons for CentOS 6 (other then cyrus-imapd) Message-ID: <20180621214559.GA27219(a)localhost.localdomain> Content-Type: text/plain; charset=us-ascii On Thu, Jun 21, 2018 at 05:23:31PM -0400, Robert Heller wrote: > At Thu, 21 Jun 2018 20:42:50 +0200 CentOS mailing list <centos(a)centos.org> wrote: > > > > > On 21.06.2018 19:28, Robert Heller wrote: > > > Are there any imap daemons (besides cyrus-imapd). cyrus-imapd is appearently > > > not compatible with postfix + procmail. I need an imap daemon that will work > > > with a postfix + procmail system. > > > > > the problem seems to be procmail, I use postfix and cyrus-imapd with no > > problems; > > No actually the problem is cyrus-imapd: cyrus-imapd expects all users to use > imap (or pop3) to access their E-Mail. It does not allow for other E-Mail > methodologies, including using local UNIX utilies (eg mail or pine or mh or > other tools like QWK). So it's not that postfix + procmail + cyrus doesn't work, but that you have a requirement that cyrus can't fulfill. ------------------------------ Message: 14 Date: Thu, 21 Jun 2018 16:51:12 -0500 From: Valeri Galtsev <galtsev(a)kicp.uchicago.edu> To: centos(a)centos.org Subject: Re: [CentOS] Imap daemons for CentOS 6 (other then cyrus-imapd) Message-ID: <a82ade4c-4892-0840-970b-184061e686e1(a)kicp.uchicago.edu> Content-Type: text/plain; charset=utf-8; format=flowed On 06/21/18 16:46, Marcelo Ricardo Leitner wrote: > On Thu, Jun 21, 2018 at 05:23:31PM -0400, Robert Heller wrote: >> At Thu, 21 Jun 2018 20:42:50 +0200 CentOS mailing list <centos(a)centos.org> wrote: >> >>> >>> On 21.06.2018 19:28, Robert Heller wrote: >>>> Are there any imap daemons (besides cyrus-imapd). cyrus-imapd is appearently >>>> not compatible with postfix + procmail. I need an imap daemon that will work >>>> with a postfix + procmail system. >>>> >>> the problem seems to be procmail, I use postfix and cyrus-imapd with no >>> problems; >> >> No actually the problem is cyrus-imapd: cyrus-imapd expects all users to use >> imap (or pop3) to access their E-Mail. It does not allow for other E-Mail >> methodologies, including using local UNIX utilies (eg mail or pine or mh or >> other tools like QWK). Just a bit of correction. Pine (which is so old, alpine replaced it) or alpine you can configure to talk through IMAP protocol, then it will not matter what sort of IMAP server do you have. Just minor correction. Valeri > > So it's not that postfix + procmail + cyrus doesn't work, but that you > have a requirement that cyrus can't fulfill. > _______________________________________________ > CentOS mailing list > CentOS(a)centos.org > https://clicktime.symantec.com/a/1/GaRh-9mT7pT2BGk25Szya6j4lyfBTXokdCA6hocG… > -- ++++++++++++++++++++++++++++++++++++++++ Valeri Galtsev Sr System Administrator Department of Astronomy and Astrophysics Kavli Institute for Cosmological Physics University of Chicago Phone: 773-702-4247 ++++++++++++++++++++++++++++++++++++++++ ------------------------------ Message: 15 Date: Thu, 21 Jun 2018 17:51:39 -0400 From: Jonathan Billings <billings(a)negate.org> To: centos(a)centos.org Subject: Re: [CentOS] Imap daemons for CentOS 6 (other then cyrus-imapd) Message-ID: <20180621215139.dzzq57snoncik746@raspi3> Content-Type: text/plain; charset=us-ascii On Thu, Jun 21, 2018 at 05:23:31PM -0400, Robert Heller wrote: > No actually the problem is cyrus-imapd: cyrus-imapd expects all users to use > imap (or pop3) to access their E-Mail. It does not allow for other E-Mail > methodologies, including using local UNIX utilies (eg mail or pine or mh or > other tools like QWK). I suppose it shouldn't be a huge surprise that an IMAP server expects you to use IMAP. The backend uses its own files in a manner that is optimised for running IMAP, which improves performance and load on the server. If you're using dovecot, at least try to avoid using mbox format, due to how terrible it is for performance. -- Jonathan Billings <billings(a)negate.org> ------------------------------ Message: 16 Date: Fri, 22 Jun 2018 09:24:53 +0100 (BST) From: John Hodrien <J.H.Hodrien(a)leeds.ac.uk> To: CentOS mailing list <centos(a)centos.org> Subject: Re: [CentOS] Specifying different options for different " smb" type gvfs mount Message-ID: <nycvar.YEU.7.76.1806220912370.31795(a)pbzc-cp3201.yrrqf.np.hx> Content-Type: text/plain; charset=utf-8; format=flowed On Thu, 21 Jun 2018, Gordon Messmer wrote: > On 06/21/2018 05:09 AM, John Hodrien wrote: >> On Thu, 21 Jun 2018, Toralf Lund wrote: >> >>> I known that I might use mount.cifs and related "fstab" entries as an >>> alternative, but its password handling seems a lot less convenient. >> >> If you're in an AD environment, you can probably do nicely with >> mount.cifs: >> sec=krb5,multiuser >> That way you don't have to deal with usernames/passwords at all. > > Interesting.? Seems like a lot of setup, but it's interesting.? I didn't know > SMB supported this: > > https://clicktime.symantec.com/a/1/C-MtUYKskiDqrOo6AjZ3TiEoE538EEMOIEdNoqih… That article makes it sound a whole lot harder than it is, as almost all of that is pre done in later versions of CentOS. You don't have to configure the upcall stuff as it's already done, you don't need to generate a credential cache for root as it can just use the keytab, and if you've already setup a machine to talk to AD with SSSD you've probably done everything else. Paired with wildcard automount entries, and you end up in a very usable setup with minimal config. jh ------------------------------ Message: 17 Date: Fri, 22 Jun 2018 10:31:45 +0200 From: "Walter H." <walter.h(a)mathemainzel.info> To: "CentOS mailing list" <centos(a)centos.org> Subject: Re: [CentOS] Imap daemons for CentOS 6 (other then cyrus-imapd) Message-ID: <bac82dd69b099fc5dc37c0766f5b4a95.1529656305(a)squirrel.mail> Content-Type: text/plain;charset=utf-8 On Thu, June 21, 2018 23:23, Robert Heller wrote: > At Thu, 21 Jun 2018 20:42:50 +0200 CentOS mailing list <centos(a)centos.org> > wrote: > >> >> On 21.06.2018 19:28, Robert Heller wrote: >> > Are there any imap daemons (besides cyrus-imapd). cyrus-imapd is >> appearently >> > not compatible with postfix + procmail. I need an imap daemon that >> will work >> > with a postfix + procmail system. >> > >> the problem seems to be procmail, I use postfix and cyrus-imapd with no >> problems; > > No actually the problem is cyrus-imapd: cyrus-imapd expects all users to > use > imap (or pop3) to access their E-Mail. of course, what else do you expect? (SSL is not the problem, as I'm using cyrus-imapd with SSL) Walter ------------------------------ Message: 18 Date: Fri, 22 Jun 2018 10:43:20 +0200 From: "Walter H." <walter.h(a)mathemainzel.info> To: "CentOS mailing list" <centos(a)centos.org> Subject: Re: [CentOS] Imap daemons for CentOS 6 (other then cyrus-imapd) Message-ID: <841a958996ff749537ac6f066a6b1283.1529657000(a)squirrel.mail> Content-Type: text/plain;charset=utf-8 On Thu, June 21, 2018 23:23, Robert Heller wrote: > At Thu, 21 Jun 2018 20:42:50 +0200 CentOS mailing list <centos(a)centos.org> wrote: > >> >> On 21.06.2018 19:28, Robert Heller wrote: >> > Are there any imap daemons (besides cyrus-imapd). cyrus-imapd is >> appearently >> > not compatible with postfix + procmail. I need an imap daemon that >> will work >> > with a postfix + procmail system. >> > >> the problem seems to be procmail, I use postfix and cyrus-imapd with no problems; > > No actually the problem is cyrus-imapd: cyrus-imapd expects all users to use > imap (or pop3) to access their E-Mail. of course, what else do you expect? (SSL is not the problem, as I'm using cyrus-imapd with SSL) here my settings in /etc/imapd.conf tls_cert_file: /etc/pki/cyrus-imapd/tls.crt/mail-host.crt tls_key_file: /etc/pki/cyrus-imapd/tls.key/mail-host.key tls_ca_file: /etc/pki/cyrus-imapd/tls.crt/server-chain-sslca.crt tls_cipher_list: EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA:EECDH:EDH+AESGCM:EDH:ECDH+AESGCM:ECDH+AES:ECDH:AES:HIGH:MEDIUM:3DES:!SSLv2:+SSLv3:!RC4:!MD5:!IDEA:!SEED:!aNULL:!eNULL:!LOW:!EXP:!DSS:!PSK:!SRP tls_prefer_server_ciphers: 1 tls_versions: tls1_0 tls1_1 tls1_2 Walter ------------------------------ Subject: Digest Footer _______________________________________________ CentOS mailing list CentOS(a)centos.org https://clicktime.symantec.com/a/1/GaRh-9mT7pT2BGk25Szya6j4lyfBTXokdCA6hocG… ------------------------------ End of CentOS Digest, Vol 161, Issue 22 ***************************************

1 0

failed to start guest with "<interface type='hostdev'>" type vf
by Maheshwari, Shagun 25 Jun '18

25 Jun '18

Hi, Issue mentioned in https://bugzilla.redhat.com/show_bug.cgi?id=1066825 is marked as fixed in CentOS 7. However I still see issue in CentOS 7 Domain vWAAS-12KK defined from vWAAS-12KK/vWAAS-12KK.xml error: Failed to start domain vWAAS-12KK error: internal error: couldn't find IFLA_VF_INFO for VF 2 in netlink response Domain vWAAS-12KK marked as autostarted Done launching [root@localhost home]# virsh list Id Name State ---------------------------------------------------- [root@localhost home]# [root@localhost home]# [root@localhost home]# virsh list --all Id Name State ---------------------------------------------------- - vWAAS-12KK shut off I can share more info if needed. Regards, Shagun

1 0

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