similar to: Fix for ''firewall'' script on shorewall delete

Hi, On Tue, Apr 28, 2015 at 10:37 AM, <carlh04426 at gmail.com> wrote: > Hi All, > > I had some health issues for a few months and I barely recall dealing > with Heartbleed ... it's all just a blur. Now I'm getting back up to > speed, but I have a pair of CentOS 6.6 x86_64 + Virtualmin 4.13 GPL > servers which no longer seem to be picking up available updates.

Hi All, I had some health issues for a few months and I barely recall dealing with Heartbleed ... it's all just a blur. Now I'm getting back up to speed, but I have a pair of CentOS 6.6 x86_64 + Virtualmin 4.13 GPL servers which no longer seem to be picking up available updates. 'yum check' ran for about 25 minutes this evening on one of them and returned nothing useful. rpm -qa

Hi, it seems not to be possible to add more than one host at once to a zone. So shorewall add br0:eth0:192.168.2.10,eth0:192.168.2.11 work fails, since "br0:eth0:192.168.2.10,eth0" is interpreted as one interface. --snip -- iptables v1.2.9: interface name `eth0:192.168.2.10,eth0'' must be shorter than IFNAMSIZ (15) Try `iptables -h'' or ''iptables

Using the instructions on: http://wiki.centos.org/AdditionalResources/Repositories/RPMForge#head-f0 c3ecee3dbb407e4eed79a56ec0ae92d1398e01 I enter the command: rpm --import http://apt.sw.be/RPM-GPG-KEY.dag.txt and it comes back to the prompt, like it worked, but attempting to confirm the download: rpm -K rpmforge-release-0.5.2-2.el6.rf.*.rpm results in: error:

Trying to apply the latest updates to an Athalon base fully updated CentOS 4.2. In the past used the update process kicked off by clicking the hand-dandy red icon. This failed, so I tried yum. Somewhere in the process, it complained that there was no GPG key for the lame libraries (IIRC, everything's a little hazy after all the Googling trying to fix this). Anyway, tried "yum

Alle, I'm running CentOS 4.8. I just started seeing these errors during RPM operations: error: rpmdbAdd: skipping h# 990 Header V3 DSA signature: BAD, key ID 443e1821 error: rpmdbNextIterator: skipping h# 969 Header V3 DSA signature: BAD, key ID 443e1821 I've cleared out the __db.* files and tried to rebuild the DB with no luck. I've also tried this:

Got a problem with one workstation. What I'm seeing, from a yum update (saw it with make whatis first): <snip> Running rpm_check_debug error: rpmdbNextIterator: skipping h# 1211 hdr SHA1: BAD, not hex <repeated many times> <snip> ERROR with rpm_check_debug vs depsolve: libicui18n.so.36 is needed by boost-1.33.1-10.el5_7.3.i386 libicuuc.so.36 is needed by

On 1/4/19 8:22 AM, Daniel Walsh wrote: > On 1/3/19 10:19 PM, H wrote: >> I recently updated docker to version 18.09 and I seem to have lost the container id in the command prompt when I exec into a running container, a very useful feature in the previous version I was running. I have not found any information in the Docker General Forum. >> >> Has anyone else seen this?

I have a system (Centos 4.4 all packages uptodate) where almost every rpm or yum operation fails with a message like e.g.: error: %preun(a2ps-4.13b-41.i386) scriptlet failed, exit status 255 some times the error is on %post() the last few lines of output from rpm -e -vv a2ps are D: ========== --- a2ps-4.13b-41 i386-linux 0x1 D: erase: a2ps-4.13b-41 has 316 files, test = 0 D: opening db

On 01/04/2019 09:16 PM, H wrote: > On 01/04/2019 08:27 AM, Daniel Walsh wrote: >> On 1/4/19 8:22 AM, Daniel Walsh wrote: >>> On 1/3/19 10:19 PM, H wrote: >>>> I recently updated docker to version 18.09 and I seem to have lost the container id in the command prompt when I exec into a running container, a very useful feature in the previous version I was running. I have

Hi, I've encountered the following problem at a client. The problem results in one or more of the smbd processing continuously grabbing more and more memory until the system runs out of memory or just becomes unusable due to a low memory condition. This error is extremely serious as the entire server is eventually brought down by one error. After debugging this error at the

Hi, I''ve set up a bridge which connects two parts of the same subnet with each other. I''ve set up everything as described in the Documentation and it works very nicely. However: I have a problem with adding hosts to zones dynamically. The zone I want to add hosts to is called ''work''. Since only the bridge br0 is defined in /etc/shorewall/interfaces

On 1/3/19 10:19 PM, H wrote: > I recently updated docker to version 18.09 and I seem to have lost the container id in the command prompt when I exec into a running container, a very useful feature in the previous version I was running. I have not found any information in the Docker General Forum. > > Has anyone else seen this? > > _______________________________________________ >

On 01/04/2019 08:27 AM, Daniel Walsh wrote: > On 1/4/19 8:22 AM, Daniel Walsh wrote: >> On 1/3/19 10:19 PM, H wrote: >>> I recently updated docker to version 18.09 and I seem to have lost the container id in the command prompt when I exec into a running container, a very useful feature in the previous version I was running. I have not found any information in the Docker General

On 1/4/19 9:50 PM, H wrote: > On 01/04/2019 09:16 PM, H wrote: >> On 01/04/2019 08:27 AM, Daniel Walsh wrote: >>> On 1/4/19 8:22 AM, Daniel Walsh wrote: >>>> On 1/3/19 10:19 PM, H wrote: >>>>> I recently updated docker to version 18.09 and I seem to have lost the container id in the command prompt when I exec into a running container, a very useful

Hi folks, I am experiencing a strange problem with 1.9.18p7 on FreeBSD 2.2.2. When I access files from the [homes] share, my Win95 client seems to be caching the files, and not realising that the files may have changed. For example, I can load a simple text file (from the [homes] share) into Codewright on the Win95 client. Then I edit the same file using vi on the samba server, and write out

Hi there, I have Samba 2.2.3a configured to access openLDAP 2.0.18 for authentication. The autentication via ldap protocol works fine. Then I tried to enable SSL to connect samba with the LDAP server. Calling smbasswd generates this: #/usr/local/samba/bin/smbpasswd atuttle -D9 New SMB password: Retype new SMB password: ldap_open_connection: connection opened Bind failed: Can't contact LDAP

In ocfs2_remove_btree_range, when calling ocfs2_lock_refcount_tree and ocfs2_prepare_refcount_change_for_del failed, it goes to out and then tries to call mutex_unlock without mutex_lock before. And when calling ocfs2_reserve_blocks_for_rec_trunc failed, it should free ref_tree before return. Signed-off-by: Joseph Qi <joseph.qi at huawei.com> --- fs/ocfs2/alloc.c | 8 ++++---- 1 file

Hi, I have a few corrections for OPENssh-2.9p1 solaris packaging. I use to configure: setenv CFLAGS -I/opt/local/include setenv LDFLAGS "-R/opt/JGMAzlib/lib -L/opt/JGMAzlib/lib" ./configure --prefix=/opt/OPENssh --with-tcp-wrappers --sysconfdir=/etc/opt/OPENssh --localstatedir=/var/opt/OPENssh --with-pid-dir=/var/opt/OPENssh/run --with-ssl-dir=/opt/OPENssl --with-ipv4-default

[mod: Forwarded by Jeff Uphoff. I tried to mangle the headers that it appears as the original post: with an invalid return address. -- REW] A few months back, a very alpha version of bliss got posted. That shouldn''t have happened, but, it was pretty much ignored so I didn''t worry about it. But now it seems there''s a bit of a fuss about this. I''ll post the