similar to: CentOS6 box fails

Dear Srs, I'm trying to automount an iSCSI device at system startup, this is the configuration: - CentOS 5.1, with kernel 2.6.18-53.1.14.el5PAE, i686 arch - iscsi-initiator-utils 6.2.0.865-0.8.el5 - iSCSI target is a Infortrend A16E-G2130-4 I have solved the "initial_login_retry_max" problem [1] and Open- iSCSI logs into Infortrend target without problems, with 10 retries in

Peter Farrow wrote: >Rc.local is used explicitly for the running of scripts after the system >has booted. >Putting your own firewall scripts in here is a good place to put them >rather than relying on "service iptables save", this is because the >visibility of changes is poor when using the "service iptables save" >some one either inadvertantly or otherwise

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

All, my IMAP client [1] marks messages as deleted, but doesn't expunge. Dovecot (2.2.27-3+deb9u2) expunges them. Is this because the mailbox is part of public namespace? .... ::1.38247-::1.00143: MALP6 STORE 48,49,50,51,52,53,54,55,56,57,58,59,60,61 +FLAGS (\Deleted) ::1.00143-::1.38247: * 48 FETCH (FLAGS (\Deleted \Seen)) * 49 FETCH (FLAGS (\Deleted \Seen)) * 50 FETCH (FLAGS (\Deleted

Hello there, I think I've shutdown my box right in the middle of a yum update.. The latest kernel installed won't simple boot, and the old one can, but only in init 3 mode (tty). From a console, I wanted to complete the yum update and it suggested me to do a `yum-complete-transaction`. yum-complete-transaction tells me that 447 elements are left to run in 1 transaction, runs and show

Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When

I just read the rhel6 filesystem size limit. http://www.redhat.com/rhel/compare/ It says 16TB limit for ext4 (same as ext3)?!?! I thought ext4 was supposed to support 1EB ( ~ 1 million TB) limit. That was one of the main advantages of rhel6. After a little more digging all I found was that the user space formatting tools (mkfs.ext4) only support 32bit filesystems (not 48bits). I'm surprised

Any guidance appreciated. Been running CentoS 6.1 on my stuff in my 1-man office trying to buy time to have some liesure to learn the non inittab/telinit/runlevel stuff as I put up CentOS 8. So, yes I know EOL is upon me but since I've tried to become a user after exiting comp. biz decades ago I no longer stay with the "latest and greatest". Anyway, Have 6.10 up-to-date on a Ryzen

CentOS Errata and Bugfix Advisory 2011:1002 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-1002.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 9e93419532066daf9ed7decffa888102 certmonger-0.42-1.el5.i386.rpm Source: ff80760457265afe0e000c14196e695f certmonger-0.42-1.el5.src.rpm -- Karanbir Singh

CentOS Errata and Bugfix Advisory 2011:1002 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-1002.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: d20b85ae9ba720508ddf3c7fa387317f certmonger-0.42-1.el5.x86_64.rpm Source: ff80760457265afe0e000c14196e695f certmonger-0.42-1.el5.src.rpm -- Karanbir Singh

CentOS Errata and Bugfix Advisory 2011:1238 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-1238.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 94c7ee91e199e5454050a6728ec93a8b certmonger-0.42-1.el5_7.1.i386.rpm Source: 8ecf75c77186b098490435f4ac0fc600 certmonger-0.42-1.el5_7.1.src.rpm -- Johnny

CentOS Errata and Bugfix Advisory 2011:1238 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-1238.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: efaadf3eb6faa4b08d81f91a4d73b331 certmonger-0.42-1.el5_7.1.x86_64.rpm Source: 8ecf75c77186b098490435f4ac0fc600 certmonger-0.42-1.el5_7.1.src.rpm -- Johnny

CentOS Errata and Bugfix Advisory 2011:1842 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-1842.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 166db831e9f70be76dd9beaf683c511a33fae32f11c0941855b4e562aafa8716 certmonger-0.42-1.el5_7.2.i386.rpm Source:

CentOS Errata and Bugfix Advisory 2011:1842 Upstream details at : https://rhn.redhat.com/errata/RHBA-2011-1842.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: fbe31248b85debd6c44503a4f902f5ee0172d645ccd59fa3c9f1dfd44a4a191a certmonger-0.42-1.el5_7.2.x86_64.rpm Source:

CentOS Errata and Bugfix Advisory 2018:1381 Upstream details at : https://access.redhat.com/errata/RHBA-2018:1381 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) x86_64: 238c4c382d82807d2b68e5ae89ef52b1a087328867337fcf77b82af0e1b9dbcb certmonger-0.78.4-3.el7_5.1.x86_64.rpm Source:

One thing I have noticed on CentOS6 is that rsync via xinetd never works after a reboot. It always takes an additional, post-reboot service xinetd restart to get it going. That has been the same for all revisions up to and including 6.5, and I've seen it on more than just machine. While I don't see such a message on other problem machines, the latest reboot gave me a clue: Dec 9

On Mon, 13 Jan 2020 at 12:23, Patrick B?gou <Patrick.Begou at legi.grenoble-inp.fr> wrote: > > Hi, > > I have a strange problem with a freshly installed Centos7 desktop > (most8pc25). I can't ssh to 2 CentOS6 servers, even with firewall > disabled on the client and on the server. But I can connect from the > server to the client, all in the same VLAN. I can also ssh

On Mon, Jan 13, 2020 at 01:00:05PM -0500, Stephen John Smoogen wrote: > On Mon, 13 Jan 2020 at 12:23, Patrick B?gou > <Patrick.Begou at legi.grenoble-inp.fr> wrote: > > > > Hi, > > > > I have a strange problem with a freshly installed Centos7 desktop > > (most8pc25). I can't ssh to 2 CentOS6 servers, even with firewall > > disabled on the client

Hi, I have a server with Supermicro X7DVL-3 (P9) motherboard, 16G ECC RAM and LSI SAS 1068e RAID controller. I installed CentOS 6.5 64bit on the machine without any problems, but after following the Xen setup steps at http://wiki.centos.org/HowTos/Xen/Xen4QuickStart which installed me the kernel 3.10.32-11.el6.centos.alt.x86_64, I encountered a problem: After "Starting certmonger

Hi, What's the correct way to change configuration parameters for an iSCSI device? For example I/O scheduler, max_sectors_kb, etc... I could add commands to the S99local script: echo noop > /sys/block/sdb/queue/scheduler echo 64 > /sys/block/sdb/queue/max_hw_sectors_kb Unfortunately, iSCSI device names might change from sdb to, say, sdc (server reboot, iSCSI target reconnection).