I'm administrating a networked environment and I had an interesting situation arise yesterday. When a host is required to shutdown by a regular user, it refuses to do so if other users are logged in locally. This, however, is not the case when other users are logged in via SSH. If one user is logged in locally and one user is logged in via SSH and the locally logged in user attempts shutdown it succeeds without even a warning and the other user's SSH connection is abruptly terminated. My question is, is there a way to prevent this like the policy does for local users? I have already looked at the man page for sshd_config and couldn't find anything that seems related. --- **EDIT (Additional info.):** There are 4 OS's on the network: Mandriva 2009, Mandriva 2010.2, Mandriva 2011 and Ubuntu 11.04. The specific case I'm referring to had the SSH user on a Mandriva 2009 host and the local user on a Mandriva 2011 host. Mandriva 2009 hosts use the GNOME 2.28 environment, 2010.2 hosts use GNOME 2.32, 2011 hosts use KDE Plasma and the Ubuntu 11.04 hosts use Unity. --- **Update** As I noted in this question , I have looked into polkit actions under /usr/share/polkit-1/actions/ and found (in the file org.freedesktop.consolekit.policy) an action called org.freedesktop.consolekit.system.stop-multiple-users that throws the message System policy prevents stopping the system when other users are logged in I'm thinking (due to the org.freedesktop.* naming convention) that this is some kind of signal sent to the DM via D-BUS. I think that if I can find out what signal triggers this polkit action, I should be able to modify its behavior. Any ideas? --- **Update 2** I tried a little experiment today and it gave me very strange results. I tried logging in via SSH to one box and made sure no other users were logged in on any VTs. If I choose to Shutdown from the "Actions" menu of GDM, I get the long-awaited policy message informing me that it's impossible to do so without authentication as other users are logged in. **However**, if I use GDM to locally log in and choose to shut down the box from GNOME's menu, the SSH session is clobbered as before. How is this possible? Is the behavior different when I initiate a shutdown request from GDM than when I initiate it from within a gnome-session? Does that tell anybody anything that can help me solve the problem?

I'm trying to use bmake to build OS161 on Mandriva. When I try to run bmake, I get the following error: bmake: no system rules (sys.mk) I get the same error, even when I run bmake -m /usr/local/share/mk/sys.mk I've checked, and the path I listed above exists, but regardless of what path I give it, even if I give it a garbage path, I get the same error. This happens no matter what directory I run bmake in, so it's definitely not an OS161 problem. Does anybody know how to fix this?

I'm using OpenMandriva Lx 4.0 for a few weeks now and all in all it works very well on my small Netbook. Recently I've noticed that for some commands e.g. cp or mv there is no manual entry found on my system or it can't be found, but for other commands like netstat it will be displayed. I've checked that the packages man-db and man-pages are installed and also tried to reinstall them. In another post there was suggested to try mandb -c which yields to the following output updating index cache for path `/usr/share/man/man7'. Wait... Processing manual pages under /usr/share/man... Updating index cache for path `/usr/share/man/man5'. Wait... mandb: can't open /usr/share/man/man5/regulatory.bin.5.gz: No such file or directory mandb: warning: /usr/share/man/man5/regulatory.db.5.xz: bad symlink or ROFF `.so' request Updating index cache for path `/usr/share/man/man9'. Wait... mandb: can't open /usr/share/man/:man9/skb_queue_head.9: No such file or directory mandb: warning: /usr/share/man/man9/__skb_queue_head.9.xz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/:man9/skb_queue_tail.9: No such file or directory mandb: warning: /usr/share/man/man9/__skb_queue_tail.9.xz: bad symlink or ROFF `.so' request Updating index cache for path `/usr/share/man/man1'. Wait... mandb: warning: /usr/share/man/man1/openssl-rand.1ssl.xz is a dangling symlink mandb: warning: /usr/share/man/man1/openssl-passwd.1ssl.xz is a dangling symlink Updating index cache for path `/usr/share/man/man4'. Wait... Updating index cache for path `/usr/share/man/man6'. Wait... Updating index cache for path `/usr/share/man/man2'. Wait... mandb: can't open /usr/share/man/man2/init_module.2: No such file or directory mandb: warning: /usr/share/man/man2/finit_module.2.xz: bad symlink or ROFF `.so' request Updating index cache for path `/usr/share/man/mann'. Wait... Updating index cache for path `/usr/share/man/man2x'. Wait... Updating index cache for path `/usr/share/man/man8x'. Wait... Updating index cache for path `/usr/share/man/man3'. Wait... mandb: warning: /usr/share/man/man3/Class::Prototyped::why.3pm.xz: whatis parse for Class::Prototyped::why(3pm) failed mandb: warning: /usr/share/man/man3/MIME::changes.3pm.xz: whatis parse for MIME::changes(3pm) failed mandb: warning: /usr/share/man/man3/XML::Validator::Schema::SimpleType.3pm.xz: whatis parse for XML::Validator::Schema::SimpleType(3pm) failed Updating index cache for path `/usr/share/man/man5x'. Wait... Updating index cache for path `/usr/share/man/man3p'. Wait... Updating index cache for path `/usr/share/man/man8'. Wait... mandb: can't open /usr/share/man/man8/setarch.8: No such file or directory mandb: warning: /usr/share/man/man8/uname26.8.xz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man8/setarch.8: No such file or directory mandb: warning: /usr/share/man/man8/x86_64.8.xz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man8/setarch.8: No such file or directory mandb: warning: /usr/share/man/man8/i386.8.xz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man8/setarch.8: No such file or directory mandb: warning: /usr/share/man/man8/linux32.8.xz: bad symlink or ROFF `.so' request mandb: can't open /usr/share/man/man8/setarch.8: No such file or directory mandb: warning: /usr/share/man/man8/linux64.8.xz: bad symlink or ROFF `.so' request mandb: warning: /usr/share/man/man8/pcimodules.man.xz: ignoring bogus filename mandb: warning: /usr/share/man/man8/saslauthd.8.xz: whatis parse for saslauthd(8) failed Updating index cache for path `/usr/share/man/man4x'. Wait... Updating index cache for path `/usr/share/man/man1x'. Wait... Updating index cache for path `/usr/share/man/man3x'. Wait... Updating index cache for path `/usr/share/man/man1p'. Wait... Updating index cache for path `/usr/share/man/man6x'. Wait... Updating index cache for path `/usr/share/man/man0p'. Wait... Updating index cache for path `/usr/share/man/man7x'. Wait... Updating index cache for path `/usr/share/man/man9x'. Wait... done. Checking for stray cats under /usr/share/man... Checking for stray cats under /var/cache/man... ... However I'm not shure how to proceed in order to get the man pages configured properly. Does anyone has an idea how to fix it?

I'm trying to install OpenMandriva LX 3.02 alongside Windows 10 on a HP Pavilion 15-aw009na with EFI boot system. I only get to the screen where I can choose between the options "Start OpenMandriva LX in live mode", "Install OpenMandriva Lx", etc. When I choose any of these options, the installer then throws the following error message, that is repeated all the time: [number] Mandriva Linux installation AMD-Vi: completion-wait loop time out I have double checked that the md5sum is correct, the iso is not corrupted, and had to disable the secure boot option in the bootloader (bios), but it is still not working.

In the registry of Windows XP can find the following options to enable optimizations for TCP/ IP: - MSS; - TCP Rx Window Size; - SACK (Selective Acknowledgment); - ECN (Explicit Congestion Notification); - TCP Window Scaling; - TCP Timestamping; - PMTU Discovery; - TCP Fast Retransmit; - TCP Fast Recovery; - Delayed ACK. For example, under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\interfaceGUID on parameter IPAddress [REG_MULTI_SZ] can find the interface and configure a specific network card. I can manipulate the values ​​of the parameters **programmatically** and see the results. I am interested in a list of similar parameters in Linux Mandriva. And yet - can I change it from Java code?

Where do I find Mandriva Linux netinstall for i386? Do they even have a Mandriva netinstall?

I tried to use a printer that is shared by a Windows PC. When I try to Mandrive Control Center > Hardware > Set up printer, the window opens but there is no content. Only a window. Seems that **system-config-printer** package is not installed. I try to open Software Management > Look at instalable ... and select All search by name *system-config-printer* but the search returns nothing. What should I do next to be able to use the printer?

I'm currently migrating a production environment from Mandriva 2010.1 to Debian 7.0 Wheezy. The old environment used the drakbackup tool provided with Mandriva for hourly backups. I'm planning on using bacula as a more permanent and distro-agnostic solution for the Debian environment. The problem is, I need to provide continuity in terms of being able to restore the previous Mandriva backups. Usually, I could restore them easily from within mcc (Mandriva Control Center); however, I'm not sure how to accomplish this manually. **What I know so far** - Mandriva keeps lists of every archive's contents in gzipped text files. - Mandriva has gzip archives for base and incremental backups named after their creation time. - I can thus easily locate a certain file from the list files and extract the version I need from the base and incremental archives **What I need to know** - How do I merge the base and incremental backups to form the "complete" file?

Last night I tried to install Mandriva Linux on PC, where I have already Windows 7. In PC I've got 2 128GB SSD and 1 2TB HDD. On one SSD I installed Win7, and when I select the other empty SSD for installation, I couldn't format it. I get this message: ext4 formatting of sdb1 failed I don't remember what version on linux I tried to install. Is where a problem to have 2 operating systems on 2 different hard drives, and have option to choose which OS I want to run? How should I format empty SSD to install Linux on it?

I want to install Mandriva 2010.2 in my external USB HDD using the image file. The laptop's cd/dvd drive doesn't work, so I don't have the option of making a Live CD and starting the installation from there (which works well enough). My external HDD has some an NTFS partition and a free partition in which I want to install Mandriva.

I'm trying to figure out how the init system works for these distributions, but they seem to use different layouts... How do each of them work?

I can't seem to shutdown my machine from mandriva,I have to restart to shut it down from GRUB it says "System Halted" and just freezes there I'm using the x86_64 GNOME version I've already asked on mandriva forums and they couldn't determine the cause of this problem P.S. I'm using the 2.6.36.2-desktop-2mnb kernel