Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.mandriva    |    Somewhat decent but also getting bloated    |    29,919 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 29,472 of 29,919    |
|    Karl Dalen to unruh    |
|    Re: Where to go from Mandriva 2010    |
|    21 Nov 13 19:37:56    |
      From: karl.dalen21@gmail.com              On Thursday, November 21, 2013 4:22:19 PM UTC-8, unruh wrote:       > On 2013-11-21, Bit Twister wrote:       >       >> ...       > >> This exact same set-up and config files worked to connect to MD 2010       > >> earlier.       > > OH, NO. I hope you are not installing other distribution/release       > > configuration files. DO NOT do that unless the application release is       > > the same on both installations.       >       > If he means the /etc/ssh/* files, it should be fine. AFAIK those files       > have not changed in quite a while and files from Mandriva 2010 should       > work fine. If you mean the firewall files, then all bets are off.       >              Sorry for not being clear, I meant I did the exact same changes in the new       sshd_config in Mageia 3.0 as I have done in many older releases including       MD 2010 and not copying any config files from old release to new.       I usually run into initial problems with firewalls which tend to       always be enabled per default in many distributions, which prevents       smooth bring-ups of sshd, nfsd and sendmail. There were similar problems       even in the older MD distributions I have used.       I also always manually add a line "ALL: ALL" in /etc/hosts.allow,       which is normally empty after a fresh install.       >>       > >> I exit mcc and restart it       > >> looks like it does not retain that setting and it shows this option       > >> unchecked.       > >       > > Yup, I have not decided if that is a feature or a bug, but regardless       > > of current state of the firewall, what you see is normal. You need to       > > use systemctl to discern the status of a service. A service can be       > > disabled and be running.       >              This looks like a bug to me. I'm going to try disabling shorewall:       systemctl status shorewall.service       systemctl stop shorewall.service       systemctl disable shorewall.service       systemctl status shorewall.service              Thanks              >       > > systemctl status shorewall should show Active even though mcc       > > shorwall configuration does not show your last setting.       >              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca