similar to: escd daemon

Helmut Drodofsky wrote: > Hello, > > there is one route missing: > > 128.0.0.0/1. > Did you mean 127.0.0.0? mark > config client: > route-nopull > redirect-gateway def1 bypass-dhcp > > best regards > Helmut > > Viele Gr??e > Helmut Drodofsky > > Internet XS Service GmbH > He?br?hlstra?e 15 > 70565 Stuttgart > > Gesch?ftsf?hrung

Helo, update is in EPEL repository. on startup, clamd does not further create clamd.sock and clamd.pid clamd service stops without any message - even in debug mode. It's a nightmare. Helmut -- Viele Gr??e Helmut Drodofsky Internet XS Service GmbH He?br?hlstra?e 15 70565 Stuttgart Gesch?ftsf?hrung Dr.-Ing. Roswitha Hahn-Drodofsky HRB 21091 Stuttgart USt.ID: DE190582774 Tel. 0711

2016-07-08 4:19 GMT+08:00 Helmut Drodofsky <drodofsky at internet-xs.de>: > Helo, > > update is in EPEL repository. > > on startup, clamd does not further create clamd.sock and clamd.pid > > clamd service stops without any message - even in debug mode. > > Comment out "AllowSupplementaryGroups" in config clamd.conf and try restart again > It's a

Helo, we use recent to control ip traffic. kernel 2.6.18-308.13.1.el5 : all is OK kernel 2.6.18-308.16.1.el5 : the first recent statement causes an error. E.g.: iptables -A INPUT -m state --state NEW -m recent --set -p tcp --dport 80 iptables: Unknown error 18446744073709551615 The man pages say: recent is supported. CentOS 6: is OK Knows anyone more? Best regards Helmut Drodofsky -- Viele

Hello, njab.org will discontinue blacklist services. On 1. March 2013 Apache published: Bug 6913; Disabled rules/scores for njabl.org See: http://svn.apache.org/viewvc?view=revision&revision=1451776 Will there be an update from CentOS? Best regards Helmut Drodofsky -- Viele Gr??e Helmut Drodofsky Internet XS Service GmbH He?br?hlstra?e 15 70565 Stuttgart Gesch?ftsf?hrung

Hello, because of high disk load we plan to move from disk (raid1) to ssd. Are there recommendations for - manufacturer - file sytem - raid1 The Red Hat Storage Administration Guide says: - no raid 1 - ext4 only is this state of the art? I have searched list,centos.org 2015 - nothing found. I found in the year 2012 / 2013: https://www.centos.org/forums/viewtopic.php?t=7580

Hello, I have found a lot of discussions concerning the LSI Logic scsi driver. E.g.: https://lkml.org/lkml/2010/4/26/335 https://bugzilla.kernel.org/show_bug.cgi?id=16547 http://www.redhat.com/archives/rhl-list/2007-April/msg02661.html VMware ESXI was updated on 28. April 2011. Is this bug fixed in CentOS 6? RHEL 6 beta: the bug was included so far as I have read. -- Viele Gr??e Helmut

Hello, my CentOS 6.2 server sends the daily messages correct e.g. today at Feb 1 03:31:14 At the beginning of work hours (9:00 am local time): Feb 1 10:06:17 server postfix/sendmail[27125]: fatal: chdir /var/spool/postfix: Permission denied Solution: restorecon -R /var/spool/postfix/ Afterwards, postfix is OK again. My own cron jobs will be run latest 1 am What daily cron job destroys

Helo, up to 04:02 the root file system was OK. With the logrotate activities there are messages: read only. Last entry in /var/log/messages is the sendmail entry from logrotate. less /etc/mtab gives: /dev/sda1 / ext3 rw 0 0 proc /proc proc rw 0 0 sysfs /sys sysfs rw 0 0 devpts /dev/pts devpts rw,gid=5,mode=620 0 0 tmpfs /dev/shm tmpfs rw 0 0 none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0

Helo, the solution was now found in dmesg. I/O error for the journal. dmesg was updated, /var/log/messages not. I think because of read only file system. Best regards Helmut Helo, up to 04:02 the root file system was OK. With the logrotate activities there are messages: read only. Last entry in /var/log/messages is the sendmail entry from logrotate. less /etc/mtab gives: /dev/sda1 /

Helo, on http://wiki.centos.org/FAQ/CentOS7 in 3. And what if I want the old naming back? is written: /etc/udev/rules.d/60-net.rules seems necessary to override /usr/lib/udev/rules.d/60-net.rules According to my experience, the text should be changed to: /etc/udev/rules.d/70-persistent-net.rules has to describe the naming rule according to this example: SUBSYSTEM=="net",

Hello, there is one route missing: 128.0.0.0/1. config client: route-nopull redirect-gateway def1 bypass-dhcp best regards Helmut Viele Gr??e Helmut Drodofsky Internet XS Service GmbH He?br?hlstra?e 15 70565 Stuttgart Gesch?ftsf?hrung Dr.-Ing. Roswitha Hahn-Drodofsky HRB 21091 Stuttgart USt.ID: DE190582774 Tel. 0711 781941 0 Fax: 0711 781941 79 Mail: info at internet-xs.de

Hello, our server uses 1 GBit Nic and 10 GBit SPF+ NIC. When both nics are configured ONBOOT=yes, then both nics are OK. Wen 1GBit nic is ONBOOT=no, netwerk does not come up. Missing driver? What else? -- Viele Gr??e Helmut Drodofsky Internet XS Service GmbH He?br?hlstra?e 15 70565 Stuttgart Gesch?ftsf?hrung Dr.-Ing. Roswitha Hahn-Drodofsky HRB 21091 Stuttgart USt.ID: DE190582774 Tel.

Hello, up to CentOS 5.3 it was possible, to control new ip connections by "recent", "seconds" and "hitcount" -A INPUT -m state --state NEW -m recent --set -p tcp --dport 80 -A INPUT -m state --state NEW -m recent --update --seconds 60 --hitcount 1000 -p tcp --dport 80 -j LOG --log-prefix "FW DROP IP Flood: " -A INPUT -p tcp -m tcp --dport 80 -m state

Hello, now I have spent many hours to configure openswan for VPN connections without any success. My goal: VPN Server CentOS 6 with public IPv4 VPN Client (= road warrier) from private site with NAT router or from mobile cell with Linux, Windows 7, Mac, iPhone or Android Is there any how to in the net? When I read file:///usr/share/doc/openswan-doc-2.6.32/config.html then I belive, there is

Hello, booting starts /etc/init.d/nfslock. today, rpc.statd used port 873. later starting xinetd finds port used and disabled rsync daemon. So its more or less a lucky break, to boot CentOS and have rsync running? In /etc/rc3.d is S14nfslock S56xinetd so by design xinetd starts always after nfslock!!!! Best regards -- Viele Gr??e i.V. Helmut Drodofsky ________________________________

Hello, I use procedures for backup with rsync. The data where "pulled" by the backup server. Sender: Now CentOS 5.9, receiver CentOS 6 updated on July 3. Up to yesterday it run OK. Today morning I made yum update to sender CentOS 5 Now I get rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at

Hello, I use procedures for backup with rsync. The data where "pulled" by the backup server. Sender: Now CentOS 5.9, receiver CentOS 6 updated on July 3. Up to yesterday it run OK. Today morning I made yum update to sender CentOS 5 Now I get rsync: connection unexpectedly closed (0 bytes received so far) [receiver] rsync error: error in rsync protocol data stream (code 12) at

yum update was run 23.10.19 and then 05.11.19 to the beginning of the update 5.11.2019 kernel logging to /var/log/messages was ok. During the update at 5.11.2019 logging to /var/log/messages finished. I persume, this bug began during processing updates. yum-log shows: ........... Nov 05 14:56:54 Installed: virt-viewer-5.0-15.el7.x86_64 Nov 05 15:59:28 Installed: nbdkit-1.8.0-1.el7.x86_64

I've taken you as far as I can go. ?Now you will have to experiment a bit for your use case. ?I should point out that at least in my system, the link with the serial number in it shows up even with the line commented in the rules file. As always, YMMV. On Thu, 2019-02-07 at 22:29 +0100, Helmut Drodofsky wrote: > Hello Ron, > > sounds good. I have 2 tape changer. I persume, udev