[gentoo-user] glibc+ipv6 loopback resolving issues
Hi, I'm having some issues wih resolving of the loopback ip address with glibc's gethostbyaddr() / getnameinfo(). I have a setup with the following (abbreviated) /etc/hosts file: ==8 ::1 ip6-localhost 127.0.0.1 localhost ==8 When using gethostbyaddr() or getnameinfo() to resolve ip address 127.0.0.1, the hostname ip6-localhost is returned, but I expected to see localhost. When editing /etc/hosts and putting the 127.0.0.1 above the ::1 line, things work normally. It seems that glibc treats the loopback ip addresses (127.0.0.1 and ::1) as a special case, and returns the first entry from the hosts file for any loopback address, making no difference between ipv4 and ipv6. I would expect libc to differ between the 2 addresses, but it seems it doesn't. However: I find no documentation in man pages or google saying that the loopback addresses receive a special treatment, or that the entries in the hosts file should be in some special order to make things work as expected. I can easily reproduce this on several gentoo hosts, running glibc-2.10.1-r1 or glibc-2.9_p20081201-r2, and also on ubuntu 9.04 (libc6 version 2.9-4ubuntu6) and 9.10 (2.10.1-0ubuntu15). Could someone explain to me if this is intended behaviour, and why, as I tend to see this more as a bug? -- Regards, Tom PS: I tested this by using the name-addr-test utils provided by postfix (2.6.5 tarball, auxiliary/name-addr-test/ dir), because postfix was the application that showed me this strange behaviour and the test utils were readily available. PS2: When you want to reproduce this, no actual ipv6 connectivity is needed. Since glibc supports ipv6 out of the box, this should 'work' with any setup.
Re: [gentoo-user] Re: configuring x2go on gentoo
On Monday 01 February 2010 19:57:52 Nikos Chantziaras wrote: On 02/01/2010 08:06 PM, Valmor de Almeida wrote: Nikos Chantziaras wrote: On 01/22/2010 12:10 AM, Valmor de Almeida wrote: Hello, I would like to try a remote desktop server/client app (linux to linux). Would anyone have suggestions? freenx x ltsp x vnc x others? I use x2go, which is based on NX. FreeNX, which I used before, was semi-abandoned at some point. You can find it in the nx overlay. I am experimenting with it. I could not find config instructions for gentoo therefore I am following http://wiki.archlinux.org/index.php/X2go Is this sufficient? Does fuse need to be a module or can it be built into the kernel? I am follwing the latter. Thanks for inputs. Don't know about the server configuration on Gentoo. I only run the client on my Gentoo box. The server runs on a Debian machine and IIRC the configuration was pretty much automatic there. Nikos, is your debian server logging something like this every 5 seconds? Feb 2 14:20:24 revolver sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/x2gopgwrapper listsessionsroot revolver Feb 2 14:20:24 revolver sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 2 14:20:24 revolver sudo: pam_unix(sudo:session): session closed for user root Feb 2 14:20:24 revolver su[25114]: Successful su for postgres by root Feb 2 14:20:24 revolver su[25114]: + ??? root:postgres Feb 2 14:20:24 revolver su[25114]: pam_unix(su:session): session opened for user postgres by (uid=0) Feb 2 14:20:24 revolver su[25114]: pam_unix(su:session): session closed for user postgres Feb 2 14:20:29 revolver sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/x2gopgwrapper listsessionsroot revolver Feb 2 14:20:29 revolver sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 2 14:20:29 revolver sudo: pam_unix(sudo:session): session closed for user root Feb 2 14:20:29 revolver su[25126]: Successful su for postgres by root Feb 2 14:20:29 revolver su[25126]: + ??? root:postgres Feb 2 14:20:29 revolver su[25126]: pam_unix(su:session): session opened for user postgres by (uid=0) Feb 2 14:20:29 revolver su[25126]: pam_unix(su:session): session closed for user postgres Feb 2 14:20:34 revolver sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/x2gopgwrapper listsessionsroot revolver Feb 2 14:20:34 revolver sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 2 14:20:34 revolver sudo: pam_unix(sudo:session): session closed for user root Feb 2 14:20:34 revolver su[25138]: Successful su for postgres by root Feb 2 14:20:34 revolver su[25138]: + ??? root:postgres Feb 2 14:20:34 revolver su[25138]: pam_unix(su:session): session opened for user postgres by (uid=0) Feb 2 14:20:34 revolver su[25138]: pam_unix(su:session): session closed for user postgres My gentoo x2go server works fine, but I have those messages fullfilling my log, and I don't know how to solve. --- TopperH http://topperh.blackmamba.kicks-ass.org
Re: [gentoo-user] baselayout2/openrc question
On Tue, 2 Feb 2010 08:08:25 +0200 Alan McKinnon wrote: On Tuesday 02 February 2010 06:03:10 David Relson wrote: G'day, I've been running baselayout-2 for several months and it's been working fine AFAICT. Over the weekend I noticed that my USB thumb drive is no longer automounting. This evening I ran /etc/init.d/udev status which reported: * status: stopped. Running /etc/init.d/udev start reported: * The udev init-script is written for baselayout-2! * Please do not use it with baselayout-1!. * ERROR: udev failed to start The message occurs because /etc/init.d/udev checks for /etc/init.d/sysfs, which is not present. Googling indicates that /etc/init.d/sysf comes from sys-apps/openrc. I have openrc-0.3.0-r1 installed (from long ago). openrc-0.6.0-r1 is available, though keyworded ~amd64. Unmasking it and running emerge -p ... shows that sysvinit is a blocker. Is it safe to delete sysvinit and emerge openrc-0.6.0-r1? Am I likely to get myself into troubleif I do this? If so, how much and how deep? very very very very deep trouble if you restart the machine and everything is not complete yet. Do not do that. all version of baselayout-2 are marked unstable and you likely have an old version of sysvinit that is not compatible with the ancient openrc you do have. That openrc is not in portage anymore. You should upgrade to the latest unstable portage (which supports automatically resolving blockers). You need baselayout, openrc and sysvinit as well as /etc/init.d/sysfs. I have none of these in world yet all are present. With the latest portage, try again and let portage figure out for itself what it wants to do. Hi Alan, Reply appreciated! I've been running unstable versions of portage for many months and currently have 2.1.7.17, which _is_ the newest non-masked version. With it, sysvinit is blocking (capital B) openrc-0.6.0-r1 and /etc/init.d/sysfs is not present (which makes /etc/init.d/udev unhappy). Since /etc/init.d/udev only _checks_ for the presence of /etc/init.d/sysfs but doesn't run it (or anything), would creating a dummy (zero length) sysfs file be workable? Regards, David
Re: [gentoo-user] waiting for uevents...
On Mon, Feb 1, 2010 at 4:20 PM, Philip Webb purs...@ca.inter.net wrote: 100201 Valmor de Almeida wrote: Recently I bumped up the number of HDD on a relatively old system [snip] I had this on my stand-by machine discovered it was waiting for a broken CD drive; when I unplugged the drive, all was well. I had a drive that had not been used yet and had no partitions or file system on it. I booted the machine from a gentoo LiveCD (with no problem; weird), made a partition and created a fs then rebooted and all worked. Don't know why I was able to boot from a LiveCD in the first place; maybe my kernel still need some fine tuning. Thanks. -- Valmor
Re: [gentoo-user] Re: configuring x2go on gentoo
On Mon, Feb 1, 2010 at 1:57 PM, Nikos Chantziaras rea...@arcor.de wrote: On 02/01/2010 08:06 PM, Valmor de Almeida wrote: [snip] Don't know about the server configuration on Gentoo. I only run the client on my Gentoo box. The server runs on a Debian machine and IIRC the Here are the steps I followed to configure and test the server. 1) emerge x2goserver (needed to rebuild the kernel with FUSE) 2) following message from emerge of postgresql-8.1.11 did: emerge --config =postgresql-8.1.11 3) /etc/init.d/postgresql start 4) visudo and added users ALL=(ALL) NOPASSWD: /usr/bin/x2gopgwrapper 5) run script to create database cd /usr/share/x2go/script ./x2gocreatebase.sh 6) /etc/init.d/postgresql restart 7) /etc/init.d/x2goserver start The /var/log/messages file is filled with Feb 1 17:45:56 xeon0 sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/x2gopgwrapper listsessionsroot xeon0 Feb 1 17:45:56 xeon0 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 1 17:45:56 xeon0 sudo: pam_unix(sudo:session): session closed for user root Feb 1 17:45:56 xeon0 su[3869]: Successful su for postgres by root Feb 1 17:45:56 xeon0 su[3869]: + ??? root:postgres Feb 1 17:45:56 xeon0 su[3869]: pam_unix(su:session): session opened for user postgres by (uid=0) Feb 1 17:45:57 xeon0 su[3869]: pam_unix(su:session): session closed for user postgres Feb 1 17:46:02 xeon0 sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/x2gopgwrapper listsessionsroot xeon0 Feb 1 17:46:02 xeon0 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 1 17:46:02 xeon0 sudo: pam_unix(sudo:session): session closed for user root Feb 1 17:46:02 xeon0 su[3880]: Successful su for postgres by root Feb 1 17:46:02 xeon0 su[3880]: + ??? root:postgres Feb 1 17:46:02 xeon0 su[3880]: pam_unix(su:session): session opened for user postgres by (uid=0) Feb 1 17:46:02 xeon0 su[3880]: pam_unix(su:session): session closed for user postgres Any ideas on how to stop this? Thanks, -- Valmor
Re: [gentoo-user] baselayout2/openrc question
On Tuesday 02 February 2010 12:47:46 David Relson wrote: I've been running unstable versions of portage for many months and currently have 2.1.7.17, which _is_ the newest non-masked version. Nevertheless, it isn't the latest version. To get that you need an entry in package.unmask; then portage will be able to sort out far more complex problems than the unmasked version can. Don't worry - many people here have been doing this for many months, with no problems attributable to portage. -- Rgds Peter.
Re: [gentoo-user] baselayout2/openrc question
Peter Humphrey wrote: On Tuesday 02 February 2010 12:47:46 David Relson wrote: I've been running unstable versions of portage for many months and currently have 2.1.7.17, which _is_ the newest non-masked version. Nevertheless, it isn't the latest version. To get that you need an entry in package.unmask; then portage will be able to sort out far more complex problems than the unmasked version can. Don't worry - many people here have been doing this for many months, with no problems attributable to portage. I'm not sure if upgrading portage to a masked version is a sane solution for the OP's issue (i.e. resolving a single dependency issue). Reading the error output from portage (and sometimes the ebuild) to solve the blocker (as people do who run a stable portage) would suffice, imho. As for the issue with openrc: =sys-apps/openrc-0.6.0-r1 depends on =sys-apps/sysvinit-2.87-r3, and both are in ~arch. Unmask both, emerge them, run etc-update and be fine. -- Regards, Tom
[gentoo-user] Re: configuring x2go on gentoo
On 02/02/2010 02:29 PM, Momesso Andrea wrote: On Monday 01 February 2010 19:57:52 Nikos Chantziaras wrote: On 02/01/2010 08:06 PM, Valmor de Almeida wrote: Nikos Chantziaras wrote: On 01/22/2010 12:10 AM, Valmor de Almeida wrote: Hello, I would like to try a remote desktop server/client app (linux to linux). Would anyone have suggestions? freenx x ltsp x vnc x others? I use x2go, which is based on NX. FreeNX, which I used before, was semi-abandoned at some point. You can find it in the nx overlay. I am experimenting with it. I could not find config instructions for gentoo therefore I am following http://wiki.archlinux.org/index.php/X2go Is this sufficient? Does fuse need to be a module or can it be built into the kernel? I am follwing the latter. Thanks for inputs. Don't know about the server configuration on Gentoo. I only run the client on my Gentoo box. The server runs on a Debian machine and IIRC the configuration was pretty much automatic there. Nikos, is your debian server logging something like this every 5 seconds? Feb 2 14:20:24 revolver sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/x2gopgwrapper listsessionsroot revolver Feb 2 14:20:24 revolver sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 2 14:20:24 revolver sudo: pam_unix(sudo:session): session closed for user root Yup.
[gentoo-user] Re: configuring x2go on gentoo
On 02/02/2010 04:37 PM, Valmor de Almeida wrote: On Mon, Feb 1, 2010 at 1:57 PM, Nikos Chantziarasrea...@arcor.de wrote: On 02/01/2010 08:06 PM, Valmor de Almeida wrote: [snip] Don't know about the server configuration on Gentoo. I only run the client on my Gentoo box. The server runs on a Debian machine and IIRC the Here are the steps I followed to configure and test the server. 1) emerge x2goserver (needed to rebuild the kernel with FUSE) 2) following message from emerge of postgresql-8.1.11 did: emerge --config =postgresql-8.1.11 3) /etc/init.d/postgresql start 4) visudo and added users ALL=(ALL) NOPASSWD: /usr/bin/x2gopgwrapper 5) run script to create database cd /usr/share/x2go/script ./x2gocreatebase.sh 6) /etc/init.d/postgresql restart 7) /etc/init.d/x2goserver start The /var/log/messages file is filled with Feb 1 17:45:56 xeon0 sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/x2gopgwrapper listsessionsroot xeon0 Feb 1 17:45:56 xeon0 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 1 17:45:56 xeon0 sudo: pam_unix(sudo:session): session closed for user root Feb 1 17:45:56 xeon0 su[3869]: Successful su for postgres by root Feb 1 17:45:56 xeon0 su[3869]: + ??? root:postgres Feb 1 17:45:56 xeon0 su[3869]: pam_unix(su:session): session opened for user postgres by (uid=0) Feb 1 17:45:57 xeon0 su[3869]: pam_unix(su:session): session closed for user postgres Feb 1 17:46:02 xeon0 sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/bin/x2gopgwrapper listsessionsroot xeon0 Feb 1 17:46:02 xeon0 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 1 17:46:02 xeon0 sudo: pam_unix(sudo:session): session closed for user root Feb 1 17:46:02 xeon0 su[3880]: Successful su for postgres by root Feb 1 17:46:02 xeon0 su[3880]: + ??? root:postgres Feb 1 17:46:02 xeon0 su[3880]: pam_unix(su:session): session opened for user postgres by (uid=0) Feb 1 17:46:02 xeon0 su[3880]: pam_unix(su:session): session closed for user postgres Any ideas on how to stop this? I get that too. I just ignore it though. If the messages bother you, I guess you can have syslog-ng filter them out. It would probably be cleaner to suppress them at their origin - that would be sudo and su - but I don't know how.
[gentoo-user] GNOME: Selecting shut down in the menu sometimes lands me back a gdm login screen.
Selecting shut down in the menu sometimes lands me back a gdm login screen. At other times, the computer shuts down normally.
Re: [gentoo-user] baselayout2/openrc question
On Mon, Feb 01, 2010 at 11:03:10PM -0500, David Relson wrote: Is it safe to delete sysvinit and emerge openrc-0.6.0-r1? Am I likely to get myself into troubleif I do this? If so, how much and how deep? The latest version of sysvinit, 2.87-r3, is the one you should be running with openrc. This version is scheduled to go stable around 2/8, so to get it onto your system early, do this: echo =sys-apps/sysvinit-2.87-r3 /etc/portage/package.keywords William pgpUYn0oC1pIv.pgp Description: PGP signature
Re: [gentoo-user] Re: configuring x2go on gentoo
On Tue, Feb 2, 2010 at 9:37 AM, Valmor de Almeida val.gen...@gmail.com wrote: [snip] users ALL=(ALL) NOPASSWD: /usr/bin/x2gopgwrapper There is a % missing at the beginning of the line above. My x2go client/server is not working. It starts a session but immediately kicks me out. This is what I see on the client side after firing x2goclient (at this point I am only trying to open an xterm on the server): Can't load translator (:/x2goclient_en_us) ! Can't load translator (:/qt_en_US) ! Selected from list normal export HOSTNAME x2golistsessions host: 192.168.0.4 exitCode: 0 status: 0 normal x2gostartagent 1280x1024 lan 16m-jpeg-9 unix-kde-depth_24 us pc105/us 0 R xterm host: 192.168.0.4 50 f3bb191128995c903396a065e1b1d1da 5941 dealmeida-50-1265133894_stRxterm_dp24 30001 30002 30003 exitCode: 0 status: 0 tunnel normal mkdir ~/.pulse;echo default-server=localhost:30002 ~/.pulse/client.conf host: 192.168.0.4 tunnel exitCode: 0 status: 0 normal setsid x2goruncommand 50 5941 dealmeida-50-1265133894_stRxterm_dp24 30002 /usr/bin/xterm nosnd R /dev/null exit host: 192.168.0.4 exitCode: 0 status: 0 QProcess: Destroyed while process is still running. QProcess: Destroyed while process is still running. check command message normal x2gocmdexitmessage dealmeida-50-1265133894_stRxterm_dp24 host: 192.168.0.4 exec /usr/bin/xterm exitCode: 0 status: 0 On the server side, in the messages file I can't see what is wrong (here is the beginning): Feb 2 13:17:23 xeon0 sshd[7559]: Accepted keyboard-interactive/pam for dealmeida from 192.168.0.200 port 37244 ssh2 Feb 2 13:17:23 xeon0 sshd[7559]: pam_unix(sshd:session): session opened for user dealmeida by (uid=0) Feb 2 13:17:23 xeon0 sudo: dealmeida : TTY=unknown ; PWD=/home/dealmeida ; USER=root ; COMMAND=/usr/bin/x2gopgwrapper listsessions xeon0 Feb 2 13:17:23 xeon0 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 2 13:17:23 xeon0 sudo: pam_unix(sudo:session): session closed for user root Feb 2 13:17:23 xeon0 su[7567]: Successful su for postgres by root Feb 2 13:17:23 xeon0 su[7567]: + ??? root:postgres Feb 2 13:17:23 xeon0 su[7567]: pam_unix(su:session): session opened for user postgres by (uid=0) Feb 2 13:17:23 xeon0 su[7567]: pam_unix(su:session): session closed for user postgres Feb 2 13:17:23 xeon0 sshd[7559]: pam_unix(sshd:session): session closed for user dealmeida Feb 2 13:17:23 xeon0 sshd[7572]: Accepted keyboard-interactive/pam for dealmeida from 192.168.0.200 port 37245 ssh2 Feb 2 13:17:23 xeon0 sshd[7572]: pam_unix(sshd:session): session opened for user dealmeida by (uid=0) Feb 2 13:17:23 xeon0 sudo: dealmeida : TTY=unknown ; PWD=/home/dealmeida ; USER=root ; COMMAND=/usr/bin/x2gopgwrapper getdisplays xeon0 Feb 2 13:17:23 xeon0 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 2 13:17:23 xeon0 sudo: pam_unix(sudo:session): session closed for user root Feb 2 13:17:23 xeon0 su[7585]: Successful su for postgres by root Feb 2 13:17:23 xeon0 su[7585]: + ??? root:postgres Feb 2 13:17:23 xeon0 su[7585]: pam_unix(su:session): session opened for user postgres by (uid=0) Feb 2 13:17:23 xeon0 su[7585]: pam_unix(su:session): session closed for user postgres Feb 2 13:17:23 xeon0 sudo: dealmeida : TTY=unknown ; PWD=/home/dealmeida ; USER=root ; COMMAND=/usr/bin/x2gopgwrapper insertsession 50 xeon0 dealmeida-50-1265134643_stRxterm_dp24 Feb 2 13:17:23 xeon0 sudo: pam_unix(sudo:session): session opened for user root by (uid=0) Feb 2 13:17:23 xeon0 sudo: pam_unix(sudo:session): session closed for user root Feb 2 13:17:23 xeon0 su[7599]: Successful su for postgres by root Feb 2 13:17:23 xeon0 su[7599]: + ??? root:postgres Feb 2 13:17:23 xeon0 su[7599]: pam_unix(su:session): session opened for user postgres by (uid=0) Any help appreciated. Thanks. -- Valmor
Re: [gentoo-user] waiting for uevents...
On Tuesday 02 February 2010 16:23:46 Valmor de Almeida wrote: On Mon, Feb 1, 2010 at 4:20 PM, Philip Webb purs...@ca.inter.net wrote: 100201 Valmor de Almeida wrote: Recently I bumped up the number of HDD on a relatively old system [snip] I had this on my stand-by machine discovered it was waiting for a broken CD drive; when I unplugged the drive, all was well. I had a drive that had not been used yet and had no partitions or file system on it. I booted the machine from a gentoo LiveCD (with no problem; weird), made a partition and created a fs then rebooted and all worked. Don't know why I was able to boot from a LiveCD in the first place; maybe my kernel still need some fine tuning. You keep saying weird. It is not weird. What you describe is exactly the way it should work. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] baselayout2/openrc question
On Tuesday 02 February 2010 14:47:46 David Relson wrote: On Tue, 2 Feb 2010 08:08:25 +0200 Alan McKinnon wrote: On Tuesday 02 February 2010 06:03:10 David Relson wrote: G'day, I've been running baselayout-2 for several months and it's been working fine AFAICT. Over the weekend I noticed that my USB thumb drive is no longer automounting. This evening I ran /etc/init.d/udev status which reported: * status: stopped. Running /etc/init.d/udev start reported: * The udev init-script is written for baselayout-2! * Please do not use it with baselayout-1!. * ERROR: udev failed to start The message occurs because /etc/init.d/udev checks for /etc/init.d/sysfs, which is not present. Googling indicates that /etc/init.d/sysf comes from sys-apps/openrc. I have openrc-0.3.0-r1 installed (from long ago). openrc-0.6.0-r1 is available, though keyworded ~amd64. Unmasking it and running emerge -p ... shows that sysvinit is a blocker. Is it safe to delete sysvinit and emerge openrc-0.6.0-r1? Am I likely to get myself into troubleif I do this? If so, how much and how deep? very very very very deep trouble if you restart the machine and everything is not complete yet. Do not do that. all version of baselayout-2 are marked unstable and you likely have an old version of sysvinit that is not compatible with the ancient openrc you do have. That openrc is not in portage anymore. You should upgrade to the latest unstable portage (which supports automatically resolving blockers). You need baselayout, openrc and sysvinit as well as /etc/init.d/sysfs. I have none of these in world yet all are present. With the latest portage, try again and let portage figure out for itself what it wants to do. Hi Alan, Reply appreciated! I've been running unstable versions of portage for many months and currently have 2.1.7.17, which _is_ the newest non-masked version. No, you completely misunderstand what stable, unstable and masked mean. You are using stable (and call it unstable which is wrong). What you call masked is actually called unstable. Masked is something else entirely. Do not confuse these terms. They have *exact* meaning. You need to keyword portage as ~ in packages.keywords to release portage-2.2, which is the version that supports automagic blocker resolution. With it, sysvinit is blocking (capital B) openrc-0.6.0-r1 and /etc/init.d/sysfs is not present (which makes /etc/init.d/udev unhappy). Thsi is correct. You have temporary blockers and the version of portage I said you should use just magically knows what to do. It knows this better than you do. Since /etc/init.d/udev only _checks_ for the presence of /etc/init.d/sysfs but doesn't run it (or anything), would creating a dummy (zero length) sysfs file be workable? Latest unstable openrc will likely fix this. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] baselayout2/openrc question
On Tuesday 02 February 2010 17:34:42 Tom Hendrikx wrote: Peter Humphrey wrote: On Tuesday 02 February 2010 12:47:46 David Relson wrote: I've been running unstable versions of portage for many months and currently have 2.1.7.17, which _is_ the newest non-masked version. Nevertheless, it isn't the latest version. To get that you need an entry in package.unmask; then portage will be able to sort out far more complex problems than the unmasked version can. Don't worry - many people here have been doing this for many months, with no problems attributable to portage. I'm not sure if upgrading portage to a masked version is a sane solution for the OP's issue (i.e. resolving a single dependency issue). Reading the error output from portage (and sometimes the ebuild) to solve the blocker (as people do who run a stable portage) would suffice, imho. The list of benefits from using latest unstable portage is very long. The list of persons running stable systems who have reported problems here with latest unstable portage is very short, tending to zero in fact. Whereas willy-nilly mixing stable and unstable is normally condemned as a bad idea (with good reason), it generally considered OK with portage for the above reason. Portage is self-contained, unmasking it doesn't contaminate the system with legions of other unstable $STUFF As for the issue with openrc: =sys-apps/openrc-0.6.0-r1 depends on =sys-apps/sysvinit-2.87-r3, and both are in ~arch. Unmask both, emerge them, run etc-update and be fine. Portage's blocker list has historically been confusing and difficult for users to parse. They often don't know what to do - how many posts like that have you answered where the answer is simply unmerge this, merge that, merge world? It makes sense to me, probably to you too, and not much sense to a large chunk of gentoo userland. Latest portage fixes all that and makes it a non-issue. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] waiting for uevents...
100202 Alan McKinnon wrote: 100201 Valmor de Almeida wrote: On Mon, Feb 1, 2010 at 4:20 PM, Philip Webb purs...@ca.inter.net wrote: I had this on my stand-by machine discovered it was waiting for a broken CD drive; when I unplugged the drive, all was well. I had a drive that had not been used w no partitions or file system. I booted the machine from a Gentoo LiveCD with no problem (weird), made a partition and created a fs then rebooted and all worked. Don't know why I was able to boot from a LiveCD in the first place; maybe my kernel still need some fine tuning. You keep saying weird. It is not weird. What you describe is exactly the way it should work. Without further explanation from you, I don't agree: the machine shouldn't wait 5 min (mine) to decide the drive is broken there is a puzzle why the Gentoo CD wouldn't encounter the same delay. Your explication wb of interest to us both (smile). -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] baselayout2/openrc question
100202 Alan McKinnon wrote: The list of benefits from using latest unstable portage is very long. Portage is self-contained, unmasking it doesn't contaminate the system with legions of other unstable $STUFF So why has it continued to be marked 'unstable' for so long ? My long-standing policy ( 6 yr ) has been to stick to 'stable' for all system pkgs, but use 'unstable' for well-supported apps (eg KDE): I haven't run into a serious problem in all that time. -- ,, SUPPORT ___//___, Philip Webb ELECTRIC /] [] [] [] [] []| Cities Centre, University of Toronto TRANSIT`-O--O---' purslowatchassdotutorontodotca
Re: [gentoo-user] baselayout2/openrc question
On 2/2/2010 3:48 PM, Alan McKinnon wrote: No, you completely misunderstand what stable, unstable and masked mean. You are using stable (and call it unstable which is wrong). What you call masked is actually called unstable. Masked is something else entirely. Do not confuse these terms. They have *exact* meaning. Has there ever been any discussion on coming up with more precise wording for portage's error messages? I suspect a lot of confusion between masked/keyworded comes from the fact that portage calls them all Masked, e.g.: !!! All ebuilds that could satisfy =app-editors/vim-7.2.303 have been masked. !!! One of the following masked packages is required to complete your request: - app-editors/vim-7.2.303 (masked by: ~amd64 keyword) Not that I came up with any better wording off the top of my head, but is the portage team open to suggestions? Or has this issue been beaten to death already? --K
Re: [gentoo-user] baselayout2/openrc question
On Tuesday 02 February 2010 23:37:33 Philip Webb wrote: 100202 Alan McKinnon wrote: The list of benefits from using latest unstable portage is very long. Portage is self-contained, unmasking it doesn't contaminate the system with legions of other unstable $STUFF So why has it continued to be marked 'unstable' for so long ? I have no idea. You should ask Zac. There's an entry in packages.mask about wanting user test feedback, that doesn't say much. It especially says nothing about the quality of the stable vs unstable code bases My long-standing policy ( 6 yr ) has been to stick to 'stable' for all system pkgs, but use 'unstable' for well-supported apps (eg KDE): I haven't run into a serious problem in all that time. I can't think of an app that is better supported in Gentoo than portage. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] baselayout2/openrc question
On Tuesday 02 February 2010 23:40:17 Mike Edenfield wrote: On 2/2/2010 3:48 PM, Alan McKinnon wrote: No, you completely misunderstand what stable, unstable and masked mean. You are using stable (and call it unstable which is wrong). What you call masked is actually called unstable. Masked is something else entirely. Do not confuse these terms. They have *exact* meaning. Has there ever been any discussion on coming up with more precise wording for portage's error messages? I suspect a lot of confusion between masked/keyworded comes from the fact that portage calls them all Masked, e.g.: !!! All ebuilds that could satisfy =app-editors/vim-7.2.303 have been masked. !!! One of the following masked packages is required to complete your request: - app-editors/vim-7.2.303 (masked by: ~amd64 keyword) Not that I came up with any better wording off the top of my head, but is the portage team open to suggestions? Or has this issue been beaten to death already? mask is a computer term. It means something that defines an exclusion list. All packages in gentoo have masks, even if they are null. Stable can be considered to be a mask, it just happens to be empty so is always available on a system where the arch matches. When the devs talk about hard masking they mean something with an entry in packages.mask. Other terms are completely understood: arch, ~arch, etc. When users miscomprehend the terminology, it's not a failure in the terminology it's a failure by the user. Human languages are like that. No matter how well you try and nail down a definition for all time, users of the language will always try to change stuff. The current terms work well. Changing them is unlikely to be well received as they are so deeply entrenched already. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] waiting for uevents...
On Tuesday 02 February 2010 23:30:54 Philip Webb wrote: 100202 Alan McKinnon wrote: 100201 Valmor de Almeida wrote: On Mon, Feb 1, 2010 at 4:20 PM, Philip Webb purs...@ca.inter.net wrote: I had this on my stand-by machine discovered it was waiting for a broken CD drive; when I unplugged the drive, all was well. I had a drive that had not been used w no partitions or file system. I booted the machine from a Gentoo LiveCD with no problem (weird), made a partition and created a fs then rebooted and all worked. Don't know why I was able to boot from a LiveCD in the first place; maybe my kernel still need some fine tuning. You keep saying weird. It is not weird. What you describe is exactly the way it should work. Without further explanation from you, I don't agree: the machine shouldn't wait 5 min (mine) to decide the drive is broken there is a puzzle why the Gentoo CD wouldn't encounter the same delay. Your explication wb of interest to us both (smile). The thread quoted above did not mention time. The addition of that fact changes everything (as it always does). The omission of time gives one a completely different picture of the circumstances. -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] mysterious syslog message .
On Tuesday 02 February 2010 04:06:14 Iain Buchanan wrote: On Fri, 2010-01-29 at 17:29 +0200, Alan McKinnon wrote: On Friday 29 January 2010 16:26:42 Iain Buchanan wrote: I don't really care about any killswitch operation, but I'm interested in why I'm getting a . message. NetworkManager bug or misconfiguration error? Run syslog-ng with the -d switch to enable it's debug output (normally to messages), or use -dd to get even more debug output. Beware, this adds up real quick, so don't run it for long like that. The output may give you more of a clue as to what syslog-ng thinks the incoming messages are. Holy Debug Messages, Batman! Sure does add up real quick. 56,599 messages all with the same timestamp Feb 2 11:13:00; 100% cpu usage, and 200+Mb before I killed it. Shirley that's not right? The 50k of messages all look like this: Feb 2 11:12:59 orpheus syslog-ng[3739]: Filter rule evaluation begins; filter_rule='f_networkmanager' Feb 2 11:12:59 orpheus syslog-ng[3739]: Filter node evaluation result; filter_result='not-match' Feb 2 11:12:59 orpheus syslog-ng[3739]: Filter rule evaluation result; filter_result='not-match', filter_rule='f_networkmanager' That's definitely not right. Even with full debugging enabled no app should emit that amount of logs. Seeing as we are dealing with networkmanager with it's long history of being hard to deal with, I recommend you a. recognize the truth - that it is a piece of shit b. use wicd instead, which is decidedly not a piece of shit :-) -- alan dot mckinnon at gmail dot com
Re: [gentoo-user] Cannot print pdf documents from KDE4
On Saturday 30 January 2010 12:01:57 you wrote: On Friday 29 January 2010 22:04:44 Neil Bothwick wrote: On Fri, 29 Jan 2010 20:19:46 +, Mick wrote: I checked another machine (of a similar build) which does not seem to have app-text/poppler emerged (only app-text/poppler-data, app-text/poppler-utils, dev-libs/poppler, dev-libs/poppler-qt4, virtual/poppler, virtual/poppler-qt4, virtual/poppler-utils). What arch are you running on these machines? poppler recently moved from dev-libs to app-text on ~arch. This looks like you could be running the stable arch with a number of packages in portage.keywords? They are both running stable x86, with the only keyworded package being: ~kde- misc/kim4-0.9.5 What's the right way to proceed here? I see that app-text/poppler does not show the lcms flag until version 0.12.3-r2, which is currently in testing. I take it that app-text/poppler is not a dependency because it would have been pulled in when I emerged whichever meta package brought in Dophin/Konqueror. Is it that in time dev-libs/poppler will be deprecated and app-text/poppler will be pulled in then? To answer my own question: the right way to proceed was to wait for the mirrors to be updated and then portage unmerged/emerged the right packages. revdep-rebuild then partially fixed it. I had to emerge kde-base/kdegraphics- meta and kde-base/okular which did fix it. For some reason xpdf now won't remerge. Time for a new thread. Thanks for the pointer, lcms and app-text/poppler was the solution. :-) -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] GNOME: Selecting shut down in the menu sometimes lands me back a gdm login screen.
On Tuesday 02 February 2010 17:10:26 ubiquitous1980 wrote: Selecting shut down in the menu sometimes lands me back a gdm login screen. At other times, the computer shuts down normally. Does it eventually shutdown after it lands you at the gdm login screen? I suffer similar symptoms with xdm/fluxbox lately, but it shuts down. Only the shut down processes happen behind the screen - on another tty. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
[gentoo-user] VGA-out screen aspect ratio
I've only ever used my laptop's VGA-out into 4:3 screens and it always works great. I've now plugged it into a 16:9 screen for the first time, and it still displays 4:3 on that screen and on my laptop. Is there a way for it to detect the proper aspect ratio? Maybe it depends on the monitor's EDID? If not, can I manually change the aspect ratio? - Grant
Re: [gentoo-user] mysterious syslog message .
On Tuesday 02 February 2010 02:06:14 Iain Buchanan wrote:
On Fri, 2010-01-29 at 17:29 +0200, Alan McKinnon wrote:
On Friday 29 January 2010 16:26:42 Iain Buchanan wrote:
I don't really care about any killswitch operation, but I'm interested
in why I'm getting a . message. NetworkManager bug or
misconfiguration error?
Run syslog-ng with the -d switch to enable it's debug output (normally to
messages), or use -dd to get even more debug output.
Beware, this adds up real quick, so don't run it for long like that. The
output may give you more of a clue as to what syslog-ng thinks the
incoming messages are.
Holy Debug Messages, Batman! Sure does add up real quick.
56,599 messages all with the same timestamp Feb 2 11:13:00; 100% cpu
usage, and 200+Mb before I killed it.
Shirley that's not right?
The 50k of messages all look like this:
Feb 2 11:12:59 orpheus syslog-ng[3739]: Filter rule evaluation begins;
filter_rule='f_networkmanager' Feb 2 11:12:59 orpheus syslog-ng[3739]:
Filter node evaluation result; filter_result='not-match' Feb 2 11:12:59
orpheus syslog-ng[3739]: Filter rule evaluation result;
filter_result='not-match', filter_rule='f_networkmanager'
my syslog conf is directing network manager to a separate file:
@version: 3.0
# $Header:
/var/cvsroot/gentoo-x86/app-admin/syslog-ng/files/syslog-ng.conf.gentoo.3.
0,v 1.1 2009/05/25 20:07:21 mr_bones_ Exp $ #
# Syslog-ng default configuration file for Gentoo Linux
options {
chain_hostnames(no);
# The default action of syslog-ng is to log a STATS line
# to the file every 10 minutes. That's pretty ugly after a while.
# Change it to every 12 hours so you get a nice daily update of
# how many messages syslog-ng missed (0).
stats_freq(43200);
};
source src {
unix-stream(/dev/log max-connections(256));
internal();
file(/proc/kmsg);
};
destination messages { file(/var/log/messages); };
# By default messages are logged to tty12...
destination console_all { file(/dev/tty12); };
# ...if you intend to use /dev/console for programs like xconsole
# you can comment out the destination line above that references /dev/tty12
# and uncomment the line below.
#destination console_all { file(/dev/console); };
# NetworkManager log to different file
log {
source(src);
filter(f_networkmanager);
destination(df_networkmanager);
flags(final);
};
log { source(src); destination(messages); };
log { source(src); destination(console_all); };
filter f_networkmanager { program(NetworkManager); };
Could it be that NetworkManager should be networkmanager? Also try it
without and see if it fixes it.
destination df_networkmanager { file(/var/log/NetworkManager.log); };
Have you already created this file?
any ideas? thanks,
--
Regards,
Mick
signature.asc
Description: This is a digitally signed message part.
Re: [gentoo-user] VGA-out screen aspect ratio
On Tue, Feb 2, 2010 at 2:55 PM, Grant emailgr...@gmail.com wrote: I've only ever used my laptop's VGA-out into 4:3 screens and it always works great. I've now plugged it into a 16:9 screen for the first time, and it still displays 4:3 on that screen and on my laptop. Is there a way for it to detect the proper aspect ratio? Maybe it depends on the monitor's EDID? If not, can I manually change the aspect ratio? - Grant Not sure about how well it will work automatically, but try running xrandr and reading the output. It should tell you what monitors you have hooked up and what resolutions and scan frequencies they support. I did this and then put the ones I wanted into my xorg.conf file and was good to go. Hope this helps, Mark
Re: [gentoo-user] mysterious syslog message .
On Wed, 2010-02-03 at 00:05 +0200, Alan McKinnon wrote: On Tuesday 02 February 2010 04:06:14 Iain Buchanan wrote: The 50k of messages all look like this: That's definitely not right. Even with full debugging enabled no app should emit that amount of logs. and yet with debugging disabled, there's no cpu usage, so perhaps there's just a problem with my syslog-ng rules? Seeing as we are dealing with networkmanager with it's long history of being hard to deal with, I recommend you a. recognize the truth - that it is a piece of shit I appreciate the humour, but so far for me, it's Just Worked(TM). Even with this log file annoyance, it's still working. b. use wicd instead, which is decidedly not a piece of shit I had a look at that, but it doesn't do 2 things that I use NetworkManager for: 1. mobile broadband (essential for on the road) 2. NetworkManager sends dbus messages that evolution uses to toggle its online / offline state. I was sick of forever waiting for evolution to time out because I'd gone offline. (Granted, you may think evolution is another POS, but it does certain things that no other mail client can do, but that's another story) I found a post that suggested in fact iwlagn wasn't reloading properly after a suspend, so I've added UnloadModules iwlagn to /etc/hibernate/common.conf and so far I haven't seen the spurious log messages (cross my fingers). :-) thanks, -- Iain Buchanan iain at pcorp dot com dot au This is the tomorrow you worried about yesterday. And now you know why.
Re: [gentoo-user] baselayout2/openrc question
Alan McKinnon wrote: On Tuesday 02 February 2010 17:34:42 Tom Hendrikx wrote: As for the issue with openrc: =sys-apps/openrc-0.6.0-r1 depends on =sys-apps/sysvinit-2.87-r3, and both are in ~arch. Unmask both, emerge them, run etc-update and be fine. Portage's blocker list has historically been confusing and difficult for users to parse. They often don't know what to do - how many posts like that have you answered where the answer is simply unmerge this, merge that, merge world? It makes sense to me, probably to you too, and not much sense to a large chunk of gentoo userland. Latest portage fixes all that and makes it a non-issue. Those messages stump me too. I'm sort of getting to where they make sense but you have to think backward so that they do make sense. You sort of have to start at the bottom of the list and work your way up. I'm sure glad the latest portage takes care of most of that. I'm using Portage 2.2_rc62 and I have not had any problems with it. Dale :-) :-)
Re: [gentoo-user] baselayout2/openrc question
Alan McKinnon wrote: On Tuesday 02 February 2010 23:37:33 Philip Webb wrote: 100202 Alan McKinnon wrote: The list of benefits from using latest unstable portage is very long. Portage is self-contained, unmasking it doesn't contaminate the system with legions of other unstable $STUFF So why has it continued to be marked 'unstable' for so long ? I have no idea. You should ask Zac. There's an entry in packages.mask about wanting user test feedback, that doesn't say much. It especially says nothing about the quality of the stable vs unstable code bases I read on -dev that they want the older version tested more. I'm not sure why since it seems most people have just unmasked the newer version and moved on. It's not like the older version is better or anything. ;-) In my opinion, the old portage was good, the new one is even better. Now if the next version will prevent a person from borking their system, that would be heaven. lol You know, unmerge python and see what happens. Yes, you can still unmerge python, even the only version you have left, and portage not say a darn thing. It kills the heck out of portage tho. Dale :-) :-)
[gentoo-user] Gracefully shut down program by request through ssh?
Hi, I was running VMWare and the program inside of Windows has crashed. (Or maybe Windows crashed or maybe VMWare crashed - I cannot tell.) Gentoo is still alive and I can log in and look around but the mouse on that computer but its mouse is frozen so I cannot do anything at its screen. It seems the keyboard is dead also. top says there's nothing going on. No CPU cycles at all. Is there a way for me to ask Linux to talk to VMWare and see if it can shut itself down before I hit the reset button? Thanks, Mark
Re: [gentoo-user] baselayout2/openrc question
On Tue, 2 Feb 2010, Alan McKinnon wrote: On Tuesday 02 February 2010 14:47:46 David Relson wrote: On Tue, 2 Feb 2010 08:08:25 +0200 Alan McKinnon wrote: On Tuesday 02 February 2010 06:03:10 David Relson wrote: G'day, I've been running baselayout-2 for several months and it's been working fine AFAICT. Over the weekend I noticed that my USB thumb drive is no longer automounting. This evening I ran /etc/init.d/udev status which reported: * status: stopped. Running /etc/init.d/udev start reported: * The udev init-script is written for baselayout-2! * Please do not use it with baselayout-1!. * ERROR: udev failed to start The message occurs because /etc/init.d/udev checks for /etc/init.d/sysfs, which is not present. Googling indicates that /etc/init.d/sysf comes from sys-apps/openrc. I have openrc-0.3.0-r1 installed (from long ago). openrc-0.6.0-r1 is available, though keyworded ~amd64. Unmasking it and running emerge -p ... shows that sysvinit is a blocker. Is it safe to delete sysvinit and emerge openrc-0.6.0-r1? Am I likely to get myself into troubleif I do this? If so, how much and how deep? very very very very deep trouble if you restart the machine and everything is not complete yet. Do not do that. all version of baselayout-2 are marked unstable and you likely have an old version of sysvinit that is not compatible with the ancient openrc you do have. That openrc is not in portage anymore. You should upgrade to the latest unstable portage (which supports automatically resolving blockers). You need baselayout, openrc and sysvinit as well as /etc/init.d/sysfs. I have none of these in world yet all are present. With the latest portage, try again and let portage figure out for itself what it wants to do. Hi Alan, Reply appreciated! I've been running unstable versions of portage for many months and currently have 2.1.7.17, which _is_ the newest non-masked version. No, you completely misunderstand what stable, unstable and masked mean. You are using stable (and call it unstable which is wrong). What you call masked is actually called unstable. Masked is something else entirely. Do not confuse these terms. They have *exact* meaning. You need to keyword portage as ~ in packages.keywords to release portage-2.2, which is the version that supports automagic blocker resolution. portage-2.2 *is* masked: /usr/portage/profiles/package.mask: # Zac Medico zmed...@gentoo.org (05 Jan 2009) # Portage 2.2 is masked due to known bugs in the # package sets and preserve-libs features. portage-2.1.7.17 is all you can get with package.keywords (and 2.1.7.16 without, at least on x86). -Daniel *This .sig left intentionally blank*
Re: [gentoo-user] Gracefully shut down program by request through ssh?
On Tue, 2010-02-02 at 16:12 -0800, Mark Knecht wrote: Hi, I was running VMWare and the program inside of Windows has crashed. (Or maybe Windows crashed or maybe VMWare crashed - I cannot tell.) Gentoo is still alive and I can log in and look around but the mouse on that computer but its mouse is frozen so I cannot do anything at its screen. It seems the keyboard is dead also. So can you do things once logged in? Which screen are you talking about? Sounds like you're host is locked up, not just the guest? top says there's nothing going on. No CPU cycles at all. Is there a way for me to ask Linux to talk to VMWare and see if it can shut itself down before I hit the reset button? as in tell VMWare to do a windows shutdown? Not that I'm aware of. killall -15 vmware will send the SIGTERM to all vmware named processes. (You may need to use vmware-workstation, or just use ps to get the PID). If that doesn't work, follow up with a killall -9 vmware Then if you're still stuck, gnome-session-save with either --logout or --force-logout should log you out nicely. If that gets stuck, try kill -15 -1 from your user login (not root) to kill all your processess. Again, maybe a kill -9 -1 is required. It will log you out of the ssh session. If that fails (as you can tell I've done this before) try an acpi shutdown. If that fails, use the magic SysRq, but I don't think you'll need to go that far since you can ssh in. -- Iain Buchanan iaindb at netspace dot net dot au Simon: My God - you're like a trained ape. Without the training. --Episode #7, Jaynestown
Re: [gentoo-user] Gracefully shut down program by request through ssh?
On Wed, Feb 3, 2010 at 9:10 AM, Iain Buchanan iai...@netspace.net.au wrote: On Tue, 2010-02-02 at 16:12 -0800, Mark Knecht wrote: Hi, I was running VMWare and the program inside of Windows has crashed. (Or maybe Windows crashed or maybe VMWare crashed - I cannot tell.) Gentoo is still alive and I can log in and look around but the mouse on that computer but its mouse is frozen so I cannot do anything at its screen. It seems the keyboard is dead also. So can you do things once logged in? Which screen are you talking about? Sounds like you're host is locked up, not just the guest? top says there's nothing going on. No CPU cycles at all. Is there a way for me to ask Linux to talk to VMWare and see if it can shut itself down before I hit the reset button? as in tell VMWare to do a windows shutdown? Not that I'm aware of. killall -15 vmware will send the SIGTERM to all vmware named processes. (You may need to use vmware-workstation, or just use ps to get the PID). If that doesn't work, follow up with a killall -9 vmware Then if you're still stuck, gnome-session-save with either --logout or --force-logout should log you out nicely. If that gets stuck, try kill -15 -1 from your user login (not root) to kill all your processess. Again, maybe a kill -9 -1 is required. It will log you out of the ssh session. If that fails (as you can tell I've done this before) try an acpi shutdown. If that fails, use the magic SysRq, but I don't think you'll need to go that far since you can ssh in. -- Iain Buchanan iaindb at netspace dot net dot au Simon: My God - you're like a trained ape. Without the training. --Episode #7, Jaynestown i think Mark want to know if it is possible to send commands from host to guest. try vmrun. i used it use send showdown command to my windows guest once, and it worked. but it is not very nice to use. you need to give the full path of the command you are going to execute. -- Best Regards, David Shen http://twitter.com/davidshen84/
Re: [gentoo-user] Gracefully shut down program by request through ssh?
On Tue, Feb 2, 2010 at 6:52 PM, Xi Shen davidshe...@googlemail.com wrote: On Wed, Feb 3, 2010 at 9:10 AM, Iain Buchanan iai...@netspace.net.au wrote: On Tue, 2010-02-02 at 16:12 -0800, Mark Knecht wrote: Hi, I was running VMWare and the program inside of Windows has crashed. (Or maybe Windows crashed or maybe VMWare crashed - I cannot tell.) Gentoo is still alive and I can log in and look around but the mouse on that computer but its mouse is frozen so I cannot do anything at its screen. It seems the keyboard is dead also. So can you do things once logged in? Which screen are you talking about? Sounds like you're host is locked up, not just the guest? top says there's nothing going on. No CPU cycles at all. Is there a way for me to ask Linux to talk to VMWare and see if it can shut itself down before I hit the reset button? as in tell VMWare to do a windows shutdown? Not that I'm aware of. killall -15 vmware will send the SIGTERM to all vmware named processes. (You may need to use vmware-workstation, or just use ps to get the PID). If that doesn't work, follow up with a killall -9 vmware Then if you're still stuck, gnome-session-save with either --logout or --force-logout should log you out nicely. If that gets stuck, try kill -15 -1 from your user login (not root) to kill all your processess. Again, maybe a kill -9 -1 is required. It will log you out of the ssh session. If that fails (as you can tell I've done this before) try an acpi shutdown. If that fails, use the magic SysRq, but I don't think you'll need to go that far since you can ssh in. -- Iain Buchanan iaindb at netspace dot net dot au Simon: My God - you're like a trained ape. Without the training. --Episode #7, Jaynestown i think Mark want to know if it is possible to send commands from host to guest. try vmrun. i used it use send showdown command to my windows guest once, and it worked. but it is not very nice to use. you need to give the full path of the command you are going to execute. -- Best Regards, David Shen Yes, that was exactly the sort of thing I was looking for. It seems to me that if the machine is alive and vmware is alive (as I beleive they were) then it would be cool to tell vmplayer to reboot or shutdown Windows gracefully so as to cause as little problems with the disk image as possible. I got anxious about 30-40 minutes after sending the original post to the list and just issued a kill with no numeric value in top. vmware closed immediately. When I restarted vmplayer Windows acted like it does when you had to pull the plug on a physical box - complaining that it wasn't shut down properly, etc., and went through it's checks. The image came up fine and off it went to do some work. Very nice thinking that since WinXP is just a disk file that I have backed up on my network I can reload this machine in a couple of minutes or even move it to another machine to run and not lose too much time. I didn't have as much luck with VirtualBox that didn't seem to like me moving copies from one partition to another. I must go back and give that another try as I'd like to be using Open Source but for now VMWare is very nice. Thanks for your responses. Cheers, Mark
Re: [gentoo-user] Gracefully shut down program by request through ssh?
=== On Tue, 02/02, Mark Knecht wrote: === Thanks for your responses. === FYI, it is possible to control VMware from the shell. Use the vmrun tool. If the guest has vmware tools installed and is working properly you can do a clean shutdown. e.g. vmrun -T ws /path/to/vm.vmx stop soft -- Keith Dart -- -- ~ Keith Dart ke...@dartworks.biz public key: ID: 19017044 http://www.dartworks.biz/ =
