ianw1974

I expect that to be a KDE setting somewhere if it's possible to decrease it.

I've made a virtual machine. Now my question is. When I click an option to shutdown the machine, I'm given a dialog box if I want to then click the reboot or shutdown option. The dialog box has a timer of 30 seconds. Is this what you are referring to? That in case you don't click anything, it will wait 30 seconds, and then restart? Or do you mean that you click restart, the process takes too long to complete? (IE: not related to the timer/dialog box).

Please let me know.

John,

Not found anything right yet, just some bugs, but nothing hinting at a solution. So am downloading Mageia 5 and I'll make an install tomorrow. Please let me know what desktop did you install? KDE4? As per your signature?

For now, some additional info as I investigate:

https://forums.mageia.org/en/viewtopic.php?f=7&t=7923#p50327

That is just some arbitrary definition. If you have a slow harddisk, and some services running that need to be stopped beforehand, shutdown might take half a minute.

If I find anymore in the meantime, I'll try and help, otherwise, I'll be installing it to check it out and find a solution.

Yep, I think I know what you mean, although have no idea where to look. Let me make a default install of Mageia, and I'll see if I can then try and find the setting that you're talking about.

Hi John,

A lot of this could be due to services on your system, as it's shutting them all down when you turn it off. We can alleviate the problem by disabling unnecessary services. However, I would need to know what services are enabled. Easier will be a console, because I can filter them.

So if you open a console and then do this:

su (enter root password when prompted)
chkconfig --list | grep :on

that will filter all services with the "on" parameter, that shows they are enabled. You can then copy and paste it into your reply. We could do it by screenshots, but it would be too many screenshots to get all the info, and it would show all services enabled and disabled.

I'm not using Mageia 5, so am assuming they are still using chkconfig to list services. If not, I'll create myself a Virtual Machine and then take a look for an alternative command to provide you.

In your ppp config files. Since you have a config already setup, add the option in here.

As a guess somewhere under /etc/ppp, although since you configured it, you should know where the files are. I do not know what you configured or where.

you mean to say that if ppp0 is time out after 3 min then i have to run my script right but one thing i like to share when i disconnect phone line from modem then if i checked link status by /sbin/adsl-status it shows ppp0 is connected and after 2 min if i checked status then it shows error as "link is attached to ppp0 but ppp0 is down " in that case if i set gateway as 10.10.1.169 then it set but it automatically removed again

No, you set the config option in my previous post to set the idle time, then ppp0 will be dropped, and your route should be active. I don't know what else you are doing or what your script is for.

idle n

 

If this option is configured, pppd will disconnect the link whenever this timer expires. Idle times are specified in seconds. Each new active data packet will reset the timer.

From here:

http://www.tldp.org/LDP/nag2/x7297.html

obviously n you set a number for in seconds to specify an idle timeout. As I said earlier, I don't have a set up like yours, so it helps if you use google and search for the info I provided you with.

If you don't have an idle timeout, then your ppp0 connection will stay active. Which is what you have now. If you have an idle timeout set for 3 minutes, then if nothing happens for 3 minutes, the connection will then drop and your system will work how you want it.

So you need to do this.

I expect it won't do it automatically, because it seems you do not have a ppp0 idle timeout. Your simulation with pulling the telephone cable shows that this is the case. So you need to set some kind of idle timeout for ppp0, and then perhaps that will fix your problem.

As I said, just removing the telephone line, CentOS still thinks the ppp0 connection is active, and it's not responding, and so this is your problem. Ideally ppp0 should disconnect when there is no longer an internet connection. I don't have such a setup to be able to tell you what to do. You need some kind of timeout for ppp0 when it's not in use, or when no traffic is able to go across the link. This would then initiate an ifdown and you would have the default route via your Windows machine.

Maybe this google search for an idle timeout will help give you the info you need:

https://www.google.co.uk/?gws_rd=ssl#q=linux+ppp0+idle+timeout

Just taking the phone line out, your system still thinks that the ppp0 connection is active, and so you have two default routes. Which is probably why it works when you do ifdown ppp0. You said eth1 is your isp, so why are you using ppp0 unless of course that is also connected with eth1 for user authentication to bring the link up (PPPoE)?

I expect we need more information on your computer setup before we can help you further. But I expect it is related to the scenario I listed above that you have two default routes and everything is attempting to go via the one created by the ppp0 link until you drop the link.

In fact you don't need two default routes as such. You don't need this for your internal network if you are not accessing the internet from it. Perhaps explain more on what you are trying to achieve.

I don't use shorewall, so can't tell you specifically. I am using iptables however, so you should be blocking all inbound traffic unless you need access on those ports. You don't list your inbound requirements. You have squid and postfix, so do these need to be accessible to the internet? If yes, then secure squid so that nobody can use it unless you authorise them to, and the same with postfix:

http://www.mailradar.com/openrelay/

that page will help you test and tell you what you need to do and fix postfix. As for the rest, you need to generate iptables or shorewall rules to block what you don't want access to. If you want to block on that particular IP:

iptables -A INPUT -d 216.66.15.109 -j DROP

assuming that 216.66.15.109 is your public IP address assigned to this server. If not, replace it with your public IP address. Because the one above that you mentioned is Fremont, California, and your IP posting here is South Africa. So change that destination IP appropriately.

will be suffice, and allow you to continue using your server locally. However it won't be accessible now from the internet for any of your resources. If you need access, then generate appropriate iptables rules prior to this to grant access for particular source IP's, or secure squid so that only authorised users can use it.

Based on the text from the cbl, someone is using your proxy to hide their conficker requirements, and so you were correctly blocked.

When I used Mint, it updates automatically, same as on Ubuntu, as they are the linux-image-x.xx.x-xx-generic (where x.xx.x-xx is the kernel version). Most distros update the kernel automatically when one becomes available. Same happened for me with RHEL/CentOS/Mandriva. With Gentoo it installs with the emerge, but then you have to manually build and compile it.

Ran it in VirtualBox. The only thing when doing updates to iPhone, etc, you have to keep monitoring if the USB device is connected and not and click every now and then when required, to get the update of the phone to continue.

Other than that, no real major problems.

Glad you got it working :)

Lightdm is good, but does require a bit of configuration. I found this out not so long ago on my Gentoo installation, when I was trying to sort out something because of issues trying to emerge gdm, and didn't want Gnome3.

Here's a good link with some info:

https://wiki.mageia.org/en/Display_Managers

note there says about lightdm being usable in Mageia 3 and higher. Maybe it will help. I've tried lightdm and lxdm because I was attempting to build a system with LXDE but also have at least a pretty display manager. If I remember to get on my Gentoo system later tonight, I'll take a look at my config and see what special stuff there I configured. Was a while ago, so can't remember exactly what I did with it, or even what DM I'm using now.

Incidently, lightdm is in use with the latest Ubuntu's, and works straight out of the box - as does pretty much all stuff with Ubuntu. Just in case you want an alternative to check out.

You tried from repos which probably no longer exist, because 2011 is extremely old now. It probably did not find files on there, and so of course failed to download.

You can try:

https://openmandriva.org/

try downloading DVD iso image here for Mandriva 2011 maybe:

http://mandriva.mirror.dkm.cz/pub/mandriva/official/iso/2011/

maybe it will be possible to fix failed upgrade booting from DVD once you burnt ISO image.

It is possible that the motherboard is not supported by Mandriva 2010, or in particular the IDE/ATA side - this can be quite common if the motherboard was not available when Mandriva 2011 was released. The fact it reads grub/lilo does not necessarily mean that everything is OK.

It says it is waiting for /dev/sda5 and /dev/sda7. The best way, would be to start the system from the Mandriva 2011 CD/DVD in recovery/rescue mode. Then look at your disk partitions to see how it is recognised. Maybe it is not /dev/sda5 and /dev/sda7 now, and that is why the problem exists.

When you boot to rescue mode, from the console:

fdisk -l

to list partitions, and then you can see how Mandriva 2011 recognises the disk.

Gnome and KDE will be memory hungry. Alternatives are LXDE or XFCE for a lighter desktop experience. That would help speed things up a bit more.

There could be a couple of things here. You say it's an old machine? So it's possible it only has a CD-ROM drive, rather than a DVD-ROM drive. Could it be that the later versions that you have burned are DVD's and not CD's?

Alternatively, it could always be a bad burn, or corrupted ISO download, and hence the problem with not being able to read the disks that you install.

EDIT:

http://h10025.www1.hp.com/ewfrf/wc/document?docname=c00282472&tmp_task=prodinfoCategory&cc=us&dlc=en&lc=en&product=446896

from here it looks like it just has a CD-RW drive, so if you're attempting to start from DVD's, that will not work and might be the source of your problem. If using CD's for later versions, then I guess a bad burn or corrupted ISO download. Verify the ISO with the md5sum, and if incorrect download and burn again.

The other alternative, if there are no CD ISO images for the distro that you want to install (which can be the case), just replace the CD-RW with a DVD-RW, and then you're done. Best bet will be to take out the one you have in there, verify the type of connection (I expect IDE), and make sure you get a DVD drive with IDE. A lot of them now are SATA, which because this is an old machine, isn't going to work.

ianw1974: It's not trivial to make a one-shot perfect install that will result in a perfect boot on all hardware and configurations. I haven't actually used the newer installer, so I can't comment on it specifically, but it was a long needed rewrite - for a long time the installer needed developer attention. Eventually someone stepped up and gave it the rewrite it needed, but installers take a lot of testing on a very diverse range of configurations before they can be considered stable. Unlike some of the larger distros, Arch has no corporate backing, so this testing falls on the community. Testing an installer properly is time consuming and few users actually spend the time.

Maybe not trivial, but on my particular system it didn't work with the new installer. The old installer however did. Had I had the time, I would have probably posted about it to get it fixed and get my system working. However, I didn't have time, I needed my system working as I didn't have another, so dropped it for something else that just installed and worked immediately.

Yep, you'll be fine :)

If you aren't natting on the router (port-forwarding) to gain access to it externally, then no, you won't need to. Then you are just using it for internal use on your private network.