Re: [gentoo-user] gentoo-sources-3.2.0-r1 and genkernel
Il 06/01/2012 10:51, András Csányi ha scritto: under /boot directory. Did I missed something? Is there anything new in genkernel? Should I report it? Check /etc/genkernel/genkernel.conf maybe is commented the option that install it into /boot . hth A.
Re: [gentoo-user] gentoo-sources-3.2.0-r1 and genkernel
On 10 January 2012 10:12, Andrea Perotti apero...@cutaway.it wrote: Il 06/01/2012 10:51, András Csányi ha scritto: under /boot directory. Did I missed something? Is there anything new in genkernel? Should I report it? Check /etc/genkernel/genkernel.conf maybe is commented the option that install it into /boot . Wow! Thank you very much! I haven't realized that there is a config file for genkernel. I found a few interesting options in this file! :) -- - - -- Csanyi Andras (Sayusi Ando) -- http://sayusi.hu -- http://facebook.com/andras.csanyi -- Trust in God and keep your gunpowder dry! - Cromwell
Re: [gentoo-user] Re: OT crontab not understood
On 09.01.2012 19:31, James wrote: Daniel Troeder daniel at admin-box.com writes: So I have installed sys-process/vixie-cron Ah, excellent. Just so you know, Paul Vixie is one of the un_sung heros of the the internet. just look up Paul Vixie on wikepedia and you'll quickly realize that he is one of the Titans that has worked tirelessly over the decades to make the internet what it is today. Some think of him as the daddy of DNS http://www.techdirt.com/articles/20110825/23232315691/paul-vixie-explains-how-protect-ip-will-break-internet.shtml hth, James WOW - great CV (@wikipedia)! and he's also funny: note that i hold the single-author record for total CERT advisories, proving that in my copious youth i knew how to sling code but not how to manage risk. (I guess this comes from authoring bind :) signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] Re: Beta test Gentoo with mdev instead of udev; version 3
On 09.01.2012 22:08, Walter Dnes wrote: On Mon, Jan 09, 2012 at 04:47:22PM +0700, Pandu Poluan wrote Is it possible to load the firmware blob after booting, from the shell? I don't think so. These are not standard kernel modules (*.o) files. You could build the radeon driver as module and load that after booting via modprobe radeon modeset=1 The firmware then gets loaded from the module. I do that here because building the driver inside the kernel makes problems for me. Greetings Sebastian Beßler signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] How to get raid
This is true, however it's a temporary measure only, and I have backups. Once the prices drop again, I'll buy another 1.5TB disk and convert back to a RAID5. On Tue, 2012-01-10 at 13:14 +0700, Pandu Poluan wrote: On Jan 10, 2012 8:48 AM, Jeff Cranmer j...@lotussevencars.com wrote: Me too. mdadm --detail /dev/md0 thinks that /dev/sdc1 is faulty. I'm not sure whether it's really faulty, or just that my setup for RAID is screwed up. How do I get rid of an existing /dev/md0? you stop it. Override the superblock with dd.. and lose all data on the disks. I'm thinking that I can try creating a RAID1 array using the two allegedly good disks and see if I can make that work. yeah If that works, I'll get rid of it and try recreating the RAID1 with one good disk and the one that mdadm thinks is faulty. you don't have to. You can migrate a 2 disk raid1 to a 3 disk raid5. Howtos are availble via google. just saying - box in suspend to ram. I change the cable (and connector on mobo) on a disk with two raid 1 partitions on it. One came back after starting the box. The other? Nothing I tried worked. At the end I dd'ed the partition.. and did a complete 'faulty disk/replacement' resync argl. OK, so lesson learned. Just because it builds correctly in a RAID1 array, that doesn't mean that the drive isn't toast. I ran badblocks on the three drive components and, surprise, surprise, /dev/sdc came up faulty. I think I'll just build the two non-faulty drives as a RAID0 array until the hard drive prices come back down to pre-Thailand flood prices and backup regularly. Thanks for all the help. Jeff RAID 0?!?! Please reconsider. With RAID 0, *any* single drive failure will result in *total* data loss. Rgds,
Re: [gentoo-user] ntpd crashing
On Tue, 2012-01-10 at 13:56 +0800, W.Kenworthy wrote: Define crashing? This looks more like problems with yout TZ variables than ntpd. try ntpq -p to check if its actually running/locked. If ntpd is freewheeling, it is prpbably because your time is too far from lock so it will silently fail (default config). If ntpd has really crashed (ps aux will confirm), try running the daemon manually from a console - if it segfaults or comes up with a missing library, try ldd /usr/sbin/ntpd to find which lib is needed and fix. BillK ntpd -p returns: ntpq: read: Connection refused /etc/init.d/ntpd status returns: * status: crashed /etc/init.d/ntpd stop returns * Caching service dependencies ... [ ok ] * Stopping ntpd ... * start-stop-daemon: no matching processes found I tried running /usr/sbin/ntpd from a console, and nothing much happens. There now appears to be a process running for ntpd, but my time is still wrong. ps -aux shows root 21470 0.0 0.0 26140 1908 ?Ss 07:22 0:00 /usr/sbin/ntpd ntpq -p now returns remote refid st t when poll reach delay offset jitter == ntp.cox.net .GPS.1 u5 647 42.229 1800133 3.020 235-69-67-68.st 130.88.200.6 3 u4 647 47.125 1800132 1.457 clock.team-cymr 172.16.65.22 2 u3 647 50.691 1800132 0.905 sulfur.mednor.n 164.67.62.1942 u1 647 88.498 1800131 2.870 After a few minutes, I repeated ntpq -p, and got connection refused. The program is crashed. No error messages appear in the command window. The offset is large, which may be why it's crashing. There may be some problem setting the hardware clock, since I had an error on bootup stating that I was unable to set the hardware clock by any method until I set clock_systohc=NO in /etc/conf.d/hwclock (which just prevents it trying to set the hardware clock). hwclock --debug output may be useful: hwclock from util-linux 2.20.1 hwclock: Open of /dev/rtc failed: No such file or directory No usable clock interface found. hwclock: Cannot access the Hardware Clock via any known method. Jeff
Re: [gentoo-user] ntpd crashing
Jeff Cranmer wrote: On Tue, 2012-01-10 at 13:56 +0800, W.Kenworthy wrote: Define crashing? This looks more like problems with yout TZ variables than ntpd. try ntpq -p to check if its actually running/locked. If ntpd is freewheeling, it is prpbably because your time is too far from lock so it will silently fail (default config). If ntpd has really crashed (ps aux will confirm), try running the daemon manually from a console - if it segfaults or comes up with a missing library, try ldd /usr/sbin/ntpd to find which lib is needed and fix. BillK ntpd -p returns: ntpq: read: Connection refused /etc/init.d/ntpd status returns: * status: crashed /etc/init.d/ntpd stop returns * Caching service dependencies ... [ ok ] * Stopping ntpd ... * start-stop-daemon: no matching processes found I tried running /usr/sbin/ntpd from a console, and nothing much happens. There now appears to be a process running for ntpd, but my time is still wrong. ps -aux shows root 21470 0.0 0.0 26140 1908 ?Ss 07:22 0:00 /usr/sbin/ntpd ntpq -p now returns remote refid st t when poll reach delay offset jitter == ntp.cox.net .GPS.1 u5 647 42.229 1800133 3.020 235-69-67-68.st 130.88.200.6 3 u4 647 47.125 1800132 1.457 clock.team-cymr 172.16.65.22 2 u3 647 50.691 1800132 0.905 sulfur.mednor.n 164.67.62.1942 u1 647 88.498 1800131 2.870 After a few minutes, I repeated ntpq -p, and got connection refused. The program is crashed. No error messages appear in the command window. The offset is large, which may be why it's crashing. There may be some problem setting the hardware clock, since I had an error on bootup stating that I was unable to set the hardware clock by any method until I set clock_systohc=NO in /etc/conf.d/hwclock (which just prevents it trying to set the hardware clock). hwclock --debug output may be useful: hwclock from util-linux 2.20.1 hwclock: Open of /dev/rtc failed: No such file or directory No usable clock interface found. hwclock: Cannot access the Hardware Clock via any known method. No kidding the offset is large. If you just sent this email a few minutes ago. The email's send date is Tue, 10 Jan 2012 07:33:49 -0500. The mail server which received it logged it as on Tue, 10 Jan 2012 10:33:53 -0700, which suggests you're about five hours off. Hm. That sounds like your tz (-0500) is being applied twice.
Re: [gentoo-user] ntpd crashing
Am 10.01.2012 18:43, schrieb Michael Mol: Jeff Cranmer wrote: On Tue, 2012-01-10 at 13:56 +0800, W.Kenworthy wrote: Define crashing? This looks more like problems with yout TZ variables than ntpd. try ntpq -p to check if its actually running/locked. If ntpd is freewheeling, it is prpbably because your time is too far from lock so it will silently fail (default config). If ntpd has really crashed (ps aux will confirm), try running the daemon manually from a console - if it segfaults or comes up with a missing library, try ldd /usr/sbin/ntpd to find which lib is needed and fix. BillK ntpd -p returns: ntpq: read: Connection refused /etc/init.d/ntpd status returns: * status: crashed /etc/init.d/ntpd stop returns * Caching service dependencies ... [ ok ] * Stopping ntpd ... * start-stop-daemon: no matching processes found I tried running /usr/sbin/ntpd from a console, and nothing much happens. There now appears to be a process running for ntpd, but my time is still wrong. ps -aux shows root 21470 0.0 0.0 26140 1908 ?Ss 07:22 0:00 /usr/sbin/ntpd ntpq -p now returns remote refid st t when poll reach delay offset jitter == ntp.cox.net .GPS.1 u5 647 42.229 1800133 3.020 235-69-67-68.st 130.88.200.6 3 u4 647 47.125 1800132 1.457 clock.team-cymr 172.16.65.22 2 u3 647 50.691 1800132 0.905 sulfur.mednor.n 164.67.62.1942 u1 647 88.498 1800131 2.870 After a few minutes, I repeated ntpq -p, and got connection refused. The program is crashed. No error messages appear in the command window. The offset is large, which may be why it's crashing. There may be some problem setting the hardware clock, since I had an error on bootup stating that I was unable to set the hardware clock by any method until I set clock_systohc=NO in /etc/conf.d/hwclock (which just prevents it trying to set the hardware clock). hwclock --debug output may be useful: hwclock from util-linux 2.20.1 hwclock: Open of /dev/rtc failed: No such file or directory No usable clock interface found. hwclock: Cannot access the Hardware Clock via any known method. No kidding the offset is large. If you just sent this email a few minutes ago. The email's send date is Tue, 10 Jan 2012 07:33:49 -0500. The mail server which received it logged it as on Tue, 10 Jan 2012 10:33:53 -0700, which suggests you're about five hours off. Hm. That sounds like your tz (-0500) is being applied twice. Besides, ntpd does not correct such large differences. It is not designed to do this, especially on a running system. Activate /etc/init.d/ntp-client. It will set the clock so that ntpd can keep it in sync afterwards. You can start ntp-client on a running system but it might lead to funny errors or crashes of applications. Better add it to runlevel default and restart. Regards, Florian Philipp signature.asc Description: OpenPGP digital signature
[gentoo-user] Resetting the root passwd
Ok, I did something really dumb... I changed the root passwd for a system I manage last week, but neglected to write it down, and now what I *thought* I had changed it to isn't working... I know, I know, really *really* dumb, but that's where I am... I know I can boot into Single User mode, remount the root partition read/write, and edit /etc/shadow (removing the encrypted passwd), then rest it using passwd, but... Some of the accounts in /etc/shadow have a '*' where the encrypted passwd would be, and some have a '!'... (ie, one is sshd:!:... and another is halt:*:...) Does it matter what I change it to? Should I use a *, !, or nothing at all (so that there is *nothing* between the two :: that would normally contain the encrypted passwd)? Thanks...
Re: [gentoo-user] ntpd crashing
Florian Philipp writes: Am 10.01.2012 18:43, schrieb Michael Mol: Jeff Cranmer wrote: Hm. That sounds like your tz (-0500) is being applied twice. Besides, ntpd does not correct such large differences. It is not designed to do this, especially on a running system. Activate /etc/init.d/ntp-client. It will set the clock so that ntpd can keep it in sync afterwards. You can start ntp-client on a running system but it might lead to funny errors or crashes of applications. Better add it to runlevel default and restart. Or set NTPD_OPTS=-s in /etc/conf.d/ntpd, this will set the clock immediately when ntpd is being started. Wonko
[gentoo-user] Re: XFCE4 keyboard shortcuts not working
I have the following (default) keyboard shortcuts in xfce4: XF86Display Superp ControlEscape ControlAltDelete AltF2 AltF2 works, but ControlEscape and ControlAltDelete don't work. I don't know what keys correspond to XF86Display and Superp so I haven't tested those. The commands associated with the two shortcuts that don't work do execute successfully so I'm not sure what the problem is. Does anyone know how to fix this? - Grant This is a problem that was introduced in GTK = 2.24.7 recently. There is a fix for libxfce4ui to make the keyboard shortcuts work again at https://bugzilla.redhat.com/show_bug.cgi?id=768704 but vte needs to be patched, too. For more info see https://bugzilla.redhat.com/show_bug.cgi?id=626792 - Grant
Re: [gentoo-user] ntpd crashing
Florian Philipp wrote: Besides, ntpd does not correct such large differences. It is not designed to do this, especially on a running system. Activate /etc/init.d/ntp-client. It will set the clock so that ntpd can keep it in sync afterwards. You can start ntp-client on a running system but it might lead to funny errors or crashes of applications. Better add it to runlevel default and restart. Regards, Florian Philipp Two things. One, you need to set the clock manually since it is s far off. I would do this: ntpdate -b -u pool.ntp.org then start ntpd. Second thing, if you are dual booting with windows, you have to edit the config file to set it correctly: It is set in /etc/conf.d/hwclock and it has a message about how to set it. I think it is UTC. It tells you in the file tho. If it is not in yours, let me know and I'll post it. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS=--quiet-build=n
Re: [gentoo-user] Resetting the root passwd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 10.01.2012 19:46, Tanstaafl wrote: Ok, I did something really dumb... I changed the root passwd for a system I manage last week, but neglected to write it down, and now what I *thought* I had changed it to isn't working... I know, I know, really *really* dumb, but that's where I am... I know I can boot into Single User mode, remount the root partition read/write, and edit /etc/shadow (removing the encrypted passwd), then rest it using passwd, but... Some of the accounts in /etc/shadow have a '*' where the encrypted passwd would be, and some have a '!'... (ie, one is sshd:!:... and another is halt:*:...) Does it matter what I change it to? Should I use a *, !, or nothing at all (so that there is *nothing* between the two :: that would normally contain the encrypted passwd)? Thanks... The simpelest solution should be to copy the password-hash of a user whose password is know to you. Afterwards you can log in an change the password again. And for the future: http://xkcd.com/936/ ;) -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJPDI20AAoJEJwwOFaNFkYceuMH/0DJgaQ+6HH0zUkKl8y5wTW6 Kn2grThJwhrbAhzpQxRV2UOvwnVIc93LIfZXdtqISzyhYCtUo1BaYMCVNIn6Rcmj wbgk1sI3ql49SvH+Tfai/DyW0WzHbFmSsYu36xzGl02xZpuUeKSpk/cTmINz1wq4 HUA/Ej9x0jEAcNNby5t5neiTt4B3ILaFyAMQbVKVIyZy/8beoR/Rn+7bET0DoFJU QneX+fa98IYjLUFlAjENQnyNly/koEt/+RIrffbBAPUOYc3wcX+e/q9vIVrKad3H Ah+BpQOwAkceog33Y2HqNrKMMOfp3R2Nm1GgbqQpFe7N2A329OqLBPfMPs8Ejts= =EHqa -END PGP SIGNATURE-
Re: [gentoo-user] Resetting the root passwd
On Tue, 10 Jan 2012 13:46:59 -0500 Tanstaafl tansta...@libertytrek.org wrote: Ok, I did something really dumb... I changed the root passwd for a system I manage last week, but neglected to write it down, and now what I *thought* I had changed it to isn't working... I know, I know, really *really* dumb, but that's where I am... I know I can boot into Single User mode, remount the root partition read/write, and edit /etc/shadow (removing the encrypted passwd), then rest it using passwd, but... Some of the accounts in /etc/shadow have a '*' where the encrypted passwd would be, and some have a '!'... (ie, one is sshd:!:... and another is halt:*:...) Does it matter what I change it to? Should I use a *, !, or nothing at all (so that there is *nothing* between the two :: that would normally contain the encrypted passwd)? The password field in shadow contains one of three types of values: - a valid hash - nothing (meaning the account has no password at all) - an invalid hash (meaning the account cannot be logged into as no password will ever hash to that value) The third type has some standard values set by convention over the years to indicate why the password is not valid. Because they are just loose conventions there's not much consistency by usually is goes like this: * means the account is definitely a system account, should never have a valid shell and no-one must ever log into that account. Accounts like bin are like this, and Gentoo gives these /bin/false as a shell ! means it is a valid account that probably should not have a login shell but might run with a proper environment. The man account is like this and Gentoo usually gives these nologin as a shell. So what's the difference? Not much really, it's all a fine case of semantics and to you they ought to be treated the same. I might even have the explanation the wrong way round or be completely wrong, that's how poorly documented this all is :-) To reset root's password, set the field to blank (nothing between the ::) -- Alan McKinnnon alan.mckin...@gmail.com
Re: [gentoo-user] Resetting the root passwd
On Tue, Jan 10, 2012 at 08:12:53PM +0100, Hinnerk van Bruinehsen wrote: On 10.01.2012 19:46, Tanstaafl wrote: Ok, I did something really dumb... I changed the root passwd for a system I manage last week, but neglected to write it down, and now what I *thought* I had changed it to isn't working... I know, I know, really *really* dumb, but that's where I am... I know I can boot into Single User mode, remount the root partition read/write, and edit /etc/shadow (removing the encrypted passwd), then rest it using passwd, but... Some of the accounts in /etc/shadow have a '*' where the encrypted passwd would be, and some have a '!'... (ie, one is sshd:!:... and another is halt:*:...) Does it matter what I change it to? Should I use a *, !, or nothing at all (so that there is *nothing* between the two :: that would normally contain the encrypted passwd)? Thanks... The simpelest solution should be to copy the password-hash of a user whose password is know to you. Afterwards you can log in an change the password again. And for the future: http://xkcd.com/936/ ;) Or boot from a Live CD, chroot and set the password from there.
Re: [gentoo-user] ntpd crashing
On Tue, 10 Jan 2012 13:02:38 -0600 Dale rdalek1...@gmail.com wrote: Florian Philipp wrote: Besides, ntpd does not correct such large differences. It is not designed to do this, especially on a running system. Activate /etc/init.d/ntp-client. It will set the clock so that ntpd can keep it in sync afterwards. You can start ntp-client on a running system but it might lead to funny errors or crashes of applications. Better add it to runlevel default and restart. Regards, Florian Philipp Two things. One, you need to set the clock manually since it is s far off. I would do this: ntpdate -b -u pool.ntp.org then start ntpd. Second thing, if you are dual booting with windows, If he dual-boots with Windows then running ntpd at all is pretty pointless. ntpd is designed to take a longish time to correct an offset, and to creep up slowly on the correct time. The primary goal is that every second on the wall-clock between now and when the time is corrected will happen (i.e. it won't suddenly jump to the right time the way ntpdate does). For a laptop/desktop (the only use case that would dual-boot), the machine likely won't be up long enough to correct largish errors. Servers with long uptimes should use ntpd, especially if it's apps timestamp data. Laptops and desktops should instead use ntpdate every one or few hours, that is more suitable for those machines (usually they only care about what the correct time is now). -- Alan McKinnnon alan.mckin...@gmail.com
Re: [gentoo-user] ntpd crashing
Alan McKinnon wrote: On Tue, 10 Jan 2012 13:02:38 -0600 Dale rdalek1...@gmail.com wrote: Florian Philipp wrote: Besides, ntpd does not correct such large differences. It is not designed to do this, especially on a running system. Activate /etc/init.d/ntp-client. It will set the clock so that ntpd can keep it in sync afterwards. You can start ntp-client on a running system but it might lead to funny errors or crashes of applications. Better add it to runlevel default and restart. Regards, Florian Philipp Two things. One, you need to set the clock manually since it is s far off. I would do this: ntpdate -b -u pool.ntp.org then start ntpd. Second thing, if you are dual booting with windows, If he dual-boots with Windows then running ntpd at all is pretty pointless. ntpd is designed to take a longish time to correct an offset, and to creep up slowly on the correct time. The primary goal is that every second on the wall-clock between now and when the time is corrected will happen (i.e. it won't suddenly jump to the right time the way ntpdate does). For a laptop/desktop (the only use case that would dual-boot), the machine likely won't be up long enough to correct largish errors. Servers with long uptimes should use ntpd, especially if it's apps timestamp data. Laptops and desktops should instead use ntpdate every one or few hours, that is more suitable for those machines (usually they only care about what the correct time is now). Wouldn't it make more sense to get the clock set correctly on bootup with ntpdate, and then have ntpd keep things in line moving forward? Otherwise, every couple hours, you'd have your cron'd ntpddate jumping the clock around. I've had apps get stuck in infinite loops from retrograde clocks, and having it happen at the wrong time during a compile process has its own context-sensitive consequences.
[gentoo-user] mt-daapd automake error
Hello, I'm updating my system and I will emerge the mt-daapd package. revdep-rebuild shows no errors and the system is working. The emerge call builds the depended packages exception net-dns/avahi and the media-sound/mt-daapd. I'm building it with: [ebuild N ] net-dns/avahi-0.6.30-r2 USE=dbus gdbm introspection -autoipd -bookmarks -doc -gtk -gtk3 -howl-compat -ipv6 -mdnsresponder-compat -mono -python -qt4 -test -utils [ebuild N ] media-sound/mt-daapd-0.2.4.2 USE=avahi vorbis The avahi package breaks with: * Failed Running automake ! * * Include in your bugreport the contents of: * * /var/tmp/portage/net-dns/avahi-0.6.30-r2/temp/automake.out * ERROR: net-dns/avahi-0.6.30-r2 failed (prepare phase): * Failed Running automake ! * * Call stack: * ebuild.sh, line 85: Called src_prepare * environment, line 5772: Called eautoreconf * environment, line 1596: Called eautomake * environment, line 1565: Called autotools_run_tool 'automake' '--add-missing' '--copy' '--foreign' * environment, line 1248: Called die * The specific snippet of code: * die Failed Running $1 !; * * If you need support, post the output of 'emerge --info =net-dns/avahi-0.6.30-r2', * the complete build log and the output of 'emerge -pqv =net-dns/avahi-0.6.30-r2'. * The complete build log is located at '/var/tmp/portage/net-dns/avahi-0.6.30-r2/temp/build.log'. * The ebuild environment file is located at '/var/tmp/portage/net-dns/avahi-0.6.30-r2/temp/environment'. * S: '/var/tmp/portage/net-dns/avahi-0.6.30-r2/work/avahi-0.6.30' The automake.out creates the error: * automake * * PWD: /var/tmp/portage/net-dns/avahi-0.6.30-r2/work/avahi-0.6.30 * automake --add-missing --copy --foreign configure.ac:143: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... ../../lib/autoconf/general.m4:2591: _AC_COMPILE_IFELSE is expanded from... ../../lib/autoconf/general.m4:2607: AC_COMPILE_IFELSE is expanded from... ../../lib/m4sugar/m4sh.m4:606: AS_IF is expanded from... ../../lib/autoconf/general.m4:2032: AC_CACHE_VAL is expanded from... ../../lib/autoconf/general.m4:2053: AC_CACHE_CHECK is expanded from... configure.ac:143: the top level configure.ac:300: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected in body ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... configure.ac:300: the top level service-type-database/Makefile.am:21: `pkglibdir' is not a legitimate directory for `DATA' How I can fix this problem? Thanks Phil
Re: [gentoo-user] ntpd crashing
Am 10.01.2012 21:59, schrieb Michael Mol: Alan McKinnon wrote: On Tue, 10 Jan 2012 13:02:38 -0600 Dale rdalek1...@gmail.com wrote: Florian Philipp wrote: Besides, ntpd does not correct such large differences. It is not designed to do this, especially on a running system. Activate /etc/init.d/ntp-client. It will set the clock so that ntpd can keep it in sync afterwards. You can start ntp-client on a running system but it might lead to funny errors or crashes of applications. Better add it to runlevel default and restart. Regards, Florian Philipp Two things. One, you need to set the clock manually since it is s far off. I would do this: ntpdate -b -u pool.ntp.org then start ntpd. Second thing, if you are dual booting with windows, If he dual-boots with Windows then running ntpd at all is pretty pointless. ntpd is designed to take a longish time to correct an offset, and to creep up slowly on the correct time. The primary goal is that every second on the wall-clock between now and when the time is corrected will happen (i.e. it won't suddenly jump to the right time the way ntpdate does). For a laptop/desktop (the only use case that would dual-boot), the machine likely won't be up long enough to correct largish errors. Servers with long uptimes should use ntpd, especially if it's apps timestamp data. Laptops and desktops should instead use ntpdate every one or few hours, that is more suitable for those machines (usually they only care about what the correct time is now). Wouldn't it make more sense to get the clock set correctly on bootup with ntpdate, and then have ntpd keep things in line moving forward? Otherwise, every couple hours, you'd have your cron'd ntpddate jumping the clock around. I've had apps get stuck in infinite loops from retrograde clocks, and having it happen at the wrong time during a compile process has its own context-sensitive consequences. It depends on how bad your clock is. If the skew is too large, ntpd cannot keep up, even if you initially set it to the correct time. If your clock is too good and doesn't drift, you can just forget ntpd and save the RAM for something you actually need. Regards, Florian Philipp signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] ntpd crashing
On 10-Jan-12 22:18, Florian Philipp wrote: Wouldn't it make more sense to get the clock set correctly on bootup with ntpdate, and then have ntpd keep things in line moving forward? Otherwise, every couple hours, you'd have your cron'd ntpddate jumping the clock around. I've had apps get stuck in infinite loops from retrograde clocks, and having it happen at the wrong time during a compile process has its own context-sensitive consequences. It depends on how bad your clock is. If the skew is too large, ntpd cannot keep up, even if you initially set it to the correct time. If your clock is too good and doesn't drift, you can just forget ntpd and save the RAM for something you actually need. step threshold is 0.128s if default settings for ntpd are used. If time difference is less, time is corrected using slewing (depending on kernel settings, in my case +/- 0.5ms per second). If it is more, stepping is used instead. So there is no way ndpd could not keep up. But changing time with stepping might cause problems for some applications (i.e. dovecot in some previous versions just died). If ntpd is configured with tinker step 0, step adjustments never occur. But if clock is off more than 0.5ms/s, time gets never synchronised and deviation will keep increasing... Jarry -- ___ This mailbox accepts e-mails only from selected mailing-lists! Everything else is considered to be spam and therefore deleted.
Re: [gentoo-user] ntpd crashing
On Tue, 2012-01-10 at 13:02 -0600, Dale wrote: Florian Philipp wrote: Besides, ntpd does not correct such large differences. It is not designed to do this, especially on a running system. Activate /etc/init.d/ntp-client. It will set the clock so that ntpd can keep it in sync afterwards. You can start ntp-client on a running system but it might lead to funny errors or crashes of applications. Better add it to runlevel default and restart. Regards, Florian Philipp Two things. One, you need to set the clock manually since it is s far off. I would do this: ntpdate -b -u pool.ntp.org then start ntpd. Second thing, if you are dual booting with windows, you have to edit the config file to set it correctly: It is set in /etc/conf.d/hwclock and it has a message about how to set it. I think it is UTC. It tells you in the file tho. If it is not in yours, let me know and I'll post it. Dale :-) :-) Thanks. ntpdate -b -u pool.ntp.org synchronised my clock. My system is not tainted by Windoze, so no problems there. I'm still a little concerned by the results of hwclock --debug hwclock from util-linux 2.20.1 hwclock: Open of /dev/rtc failed: No such file or directory No usable clock interface found. hwclock: Cannot access the Hardware Clock via any known method. Initially, the RTC options were not enabled in my kernel, but even after setting these, I'm still getting this error. I'm adding all the device drivers as modules and trying again to see if I can remove this error. I suspect it is the root cause of my ntp issues. Jeff
Re: [gentoo-user] Resetting the root passwd
Perfect answer Alan, many thanks... On 2012-01-10 3:38 PM, Alan McKinnon alan.mckin...@gmail.com wrote: On Tue, 10 Jan 2012 13:46:59 -0500 Tanstaafltansta...@libertytrek.org wrote: Ok, I did something really dumb... I changed the root passwd for a system I manage last week, but neglected to write it down, and now what I *thought* I had changed it to isn't working... I know, I know, really *really* dumb, but that's where I am... I know I can boot into Single User mode, remount the root partition read/write, and edit /etc/shadow (removing the encrypted passwd), then rest it using passwd, but... Some of the accounts in /etc/shadow have a '*' where the encrypted passwd would be, and some have a '!'... (ie, one is sshd:!:... and another is halt:*:...) Does it matter what I change it to? Should I use a *, !, or nothing at all (so that there is *nothing* between the two :: that would normally contain the encrypted passwd)? The password field in shadow contains one of three types of values: - a valid hash - nothing (meaning the account has no password at all) - an invalid hash (meaning the account cannot be logged into as no password will ever hash to that value) The third type has some standard values set by convention over the years to indicate why the password is not valid. Because they are just loose conventions there's not much consistency by usually is goes like this: * means the account is definitely a system account, should never have a valid shell and no-one must ever log into that account. Accounts like bin are like this, and Gentoo gives these /bin/false as a shell ! means it is a valid account that probably should not have a login shell but might run with a proper environment. The man account is like this and Gentoo usually gives these nologin as a shell. So what's the difference? Not much really, it's all a fine case of semantics and to you they ought to be treated the same. I might even have the explanation the wrong way round or be completely wrong, that's how poorly documented this all is :-) To reset root's password, set the field to blank (nothing between the ::)
Re: [gentoo-user] ntpd crashing
On Tue, 10 Jan 2012 15:59:45 -0500 Michael Mol mike...@gmail.com wrote: Servers with long uptimes should use ntpd, especially if it's apps timestamp data. Laptops and desktops should instead use ntpdate every one or few hours, that is more suitable for those machines (usually they only care about what the correct time is now). Wouldn't it make more sense to get the clock set correctly on bootup with ntpdate, and then have ntpd keep things in line moving forward? Otherwise, every couple hours, you'd have your cron'd ntpddate jumping the clock around. I've had apps get stuck in infinite loops from retrograde clocks, and having it happen at the wrong time during a compile process has its own context-sensitive consequences. I suppose it all comes down to the quality of the RTC itself. Time keeping daemons were never written with clocks losing a few seconds an hour in mind (as such hardware is obviously horribly broken) This raises one of my long-standing beefs with clocks: For the price of an average burger I can buy a wristwatch from any old arb street vendor that is about three seconds a year out. But it is rather common to find server grade hardware costing three months wages with pathetic clocks inside. How come? The silicon in the cheap wristwatch will cost about 20 cents a pop and they pump them out by the millions. I'm still looking for a valid reason why crap clocks in expensive computers are still commonplace... -- Alan McKinnnon alan.mckin...@gmail.com
Re: [gentoo-user] No display w/ kernel 3.2.0
Am 2012-01-05 23:15, schrieb Stefan G. Weichinger: otoh it might be a bug and not my fault anyway. still no clue what this is all about ... *sigh* and I can't find any bug-reports on this. Gotta file one myself and maybe make myself a fool because of some small issue ... ;-) S
Re: [gentoo-user] ntpd crashing
Am 10.01.2012 22:42, schrieb Jarry: On 10-Jan-12 22:18, Florian Philipp wrote: Wouldn't it make more sense to get the clock set correctly on bootup with ntpdate, and then have ntpd keep things in line moving forward? Otherwise, every couple hours, you'd have your cron'd ntpddate jumping the clock around. I've had apps get stuck in infinite loops from retrograde clocks, and having it happen at the wrong time during a compile process has its own context-sensitive consequences. It depends on how bad your clock is. If the skew is too large, ntpd cannot keep up, even if you initially set it to the correct time. If your clock is too good and doesn't drift, you can just forget ntpd and save the RAM for something you actually need. step threshold is 0.128s if default settings for ntpd are used. If time difference is less, time is corrected using slewing (depending on kernel settings, in my case +/- 0.5ms per second). If it is more, stepping is used instead. So there is no way ndpd could not keep up. But changing time with stepping might cause problems for some applications (i.e. dovecot in some previous versions just died). If ntpd is configured with tinker step 0, step adjustments never occur. But if clock is off more than 0.5ms/s, time gets never synchronised and deviation will keep increasing... Jarry I can't find the counter example I had in mind on the archive now. Since your explanation sounds sensible, I guess that in that other thread some configuration issue was also involved or ntpd simply took too long to skew back to correct time (as the man-page states, this might take 2000s per second difference). Regards, Florian Philipp signature.asc Description: OpenPGP digital signature
Re: [gentoo-user] ntpd crashing
Jeff Cranmer wrote: On Tue, 2012-01-10 at 13:02 -0600, Dale wrote: Florian Philipp wrote: Besides, ntpd does not correct such large differences. It is not designed to do this, especially on a running system. Activate /etc/init.d/ntp-client. It will set the clock so that ntpd can keep it in sync afterwards. You can start ntp-client on a running system but it might lead to funny errors or crashes of applications. Better add it to runlevel default and restart. Regards, Florian Philipp Two things. One, you need to set the clock manually since it is s far off. I would do this: ntpdate -b -u pool.ntp.org then start ntpd. Second thing, if you are dual booting with windows, you have to edit the config file to set it correctly: It is set in /etc/conf.d/hwclock and it has a message about how to set it. I think it is UTC. It tells you in the file tho. If it is not in yours, let me know and I'll post it. Dale :-) :-) Thanks. ntpdate -b -u pool.ntp.org synchronised my clock. My system is not tainted by Windoze, so no problems there. I'm still a little concerned by the results of hwclock --debug hwclock from util-linux 2.20.1 hwclock: Open of /dev/rtc failed: No such file or directory No usable clock interface found. hwclock: Cannot access the Hardware Clock via any known method. Initially, the RTC options were not enabled in my kernel, but even after setting these, I'm still getting this error. I'm adding all the device drivers as modules and trying again to see if I can remove this error. I suspect it is the root cause of my ntp issues. Jeff Yea, the command I gave will set the clock and it doesn't care how far off it is. I cranked up a old rig that didn't even have a battery in it. It was set to waay back. It was literally years off. When I ran that command, it was set. Then it was a matter of keeping it set. I forgot to mention, in the same file is two other settings. I set both of mine to yes. One of them sets it to the correct time from the BIOS when it boots and one sets the BIOS during shutdown. Since you only run Linux, that may be a good setting for you too. I'm Linux only to. Hope that helps too. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS=--quiet-build=n
Re: [gentoo-user] ntpd crashing
What he wants is tinker panic 0 - see man ntp.conf Allows a slew below the threshold, and a step at anything over, no matter how great - works well as long as you are not doing sophisticated DB stuff (rollbacks). I am concerned about the rtc error: try ... bunyip ~ # ls -al /dev/rtc* crw--- 1 root root 10, 135 Jan 1 15:54 /dev/rtc bunyip ~ # If no rtc node you need to investigate the kernel options and/or loading of the relevant module - the options are confusing. BillK -Original Message- From: Jarry mr.ja...@gmail.com Reply-to: gentoo-user@lists.gentoo.org To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] ntpd crashing Date: Tue, 10 Jan 2012 22:42:07 +0100 On 10-Jan-12 22:18, Florian Philipp wrote: Wouldn't it make more sense to get the clock set correctly on bootup with ntpdate, and then have ntpd keep things in line moving forward? Otherwise, every couple hours, you'd have your cron'd ntpddate jumping the clock around. I've had apps get stuck in infinite loops from retrograde clocks, and having it happen at the wrong time during a compile process has its own context-sensitive consequences. It depends on how bad your clock is. If the skew is too large, ntpd cannot keep up, even if you initially set it to the correct time. If your clock is too good and doesn't drift, you can just forget ntpd and save the RAM for something you actually need. step threshold is 0.128s if default settings for ntpd are used. If time difference is less, time is corrected using slewing (depending on kernel settings, in my case +/- 0.5ms per second). If it is more, stepping is used instead. So there is no way ndpd could not keep up. But changing time with stepping might cause problems for some applications (i.e. dovecot in some previous versions just died). If ntpd is configured with tinker step 0, step adjustments never occur. But if clock is off more than 0.5ms/s, time gets never synchronised and deviation will keep increasing... Jarry
Re: [gentoo-user] Re: korganize-4.7.3 broken
On Monday 09 Jan 2012 16:38:52 James wrote: Mick michaelkintzios at gmail.com writes: Try Settings/Configure and then add new account, or fire up kcmshell4 kcm_akonadi and add resources as desired. I had to use the settings-configureKorganizer-calenders and then put the explict path into the config menu ~/.kde4/share/apps/korganizer/std.ics to get the calender to show up. then select the box in lower lefthand corner as suggested. Never had to do that before. However, as the e-news item says KDEPIM 4.7 is really borked right now. YEP! Most people have recommended to move to T'bird, Claws, or mutt. Tbird ++1! great, easy, universal (doz) . I don't blame you! I've emerged KDEPIM-4.7.4 on my test box and it continues to be broken - badly. The pop3 messages are self-duplicating and the imap4 messages inbox is always empty ... I did not yet try deleting akonadi db and nepomuk and trying re-importing everything. I'm not sure if it is even worth it to bother with KDE anymore. -- Regards, Mick signature.asc Description: This is a digitally signed message part.
Re: [gentoo-user] No display w/ kernel 3.2.0
On Tue, Jan 10, 2012 at 2:16 PM, Stefan G. Weichinger li...@xunil.at wrote: Am 2012-01-05 23:15, schrieb Stefan G. Weichinger: otoh it might be a bug and not my fault anyway. still no clue what this is all about ... *sigh* and I can't find any bug-reports on this. Gotta file one myself and maybe make myself a fool because of some small issue ... ;-) S It's not about making yourself a fool at all. You've done all the basic stuff and then a lot more and it's still not working. My suggestion would be to try the IntelGfx list. They helped me quite a lot when I first brought up the machine I tested for you. http://lists.freedesktop.org/mailman/listinfo/intel-gfx Good luck, Mark
Re: [gentoo-user] ntpd crashing
On Tuesday 10 January 2012 21:45:21 Jeff Cranmer wrote: Initially, the RTC options were not enabled in my kernel, but even after setting these, I'm still getting this error. I'm adding all the device drivers as modules and trying again to see if I can remove this error. I suspect it is the root cause of my ntp issues. It's possible that your kernel is creating /dev/rtc0 instead of /dev/rtc. What does ls -d /dev/rt* show? -- Rgds Peter Linux Counter 5290, 1994-04-23
Re: [gentoo-user] ntpd crashing
Peter Humphrey wrote: ls -d /dev/rt* This is mine: root@fireball / # ls -dl /dev/rt* lrwxrwxrwx 1 root root 4 Jan 1 15:39 /dev/rtc - rtc0 crw--- 1 root root 254, 0 Jan 1 15:39 /dev/rtc0 root@fireball / # Mine links rtc to rtc0 which should work if the OP have the same. Dale :-) :-) -- I am only responsible for what I said ... Not for what you understood or how you interpreted my words! Miss the compile output? Hint: EMERGE_DEFAULT_OPTS=--quiet-build=n
Re: [gentoo-user] Re: korganize-4.7.3 broken
On Tue, Jan 10, 2012 at 10:53:48PM +, Mick wrote: However, as the e-news item says KDEPIM 4.7 is really borked right now. YEP! Most people have recommended to move to T'bird, Claws, or mutt. Tbird ++1! great, easy, universal (doz) . When I was still using Windows, TBird was (and still is) my client of choice. But when I made the switch in 2005, I immediately started using KMail, because it was a good looking and well working program and I don't like TB's dependence on GTK in the Linux realm. I don't blame you! I've emerged KDEPIM-4.7.4 on my test box and it continues to be broken - badly. The pop3 messages are self-duplicating and the imap4 messages inbox is always empty ... And here an IMAP account first downloaded all emails from the server, apparently changed some status header in them and thusly started to upload the whole shebang back to the server. Even though, with 100 MB, my inbox is tiny, I interrupted the process by logging out. Then I synced my inbox with offlineimap (my usual way of using imap with mutt) and found many messages were duplicates now. *facepalm* There was not just one occasion when I thought I'd write a simple Qt-based desktop from scratch (e.g in the likes and scope of Xfce). ^^ -- Gruß | Greetings | Qapla' I forbid any use of my email addresses with Facebook services. The best thing is you buy a string and shoot yourself where the water is deepest. pgp0YePEvZ9i9.pgp Description: PGP signature
Re: [gentoo-user] No display w/ kernel 3.2.0
Am 10.01.2012 23:57, schrieb Mark Knecht: It's not about making yourself a fool at all. You've done all the basic stuff and then a lot more and it's still not working. My suggestion would be to try the IntelGfx list. They helped me quite a lot when I first brought up the machine I tested for you. http://lists.freedesktop.org/mailman/listinfo/intel-gfx the next list to subscribe to, sigh ... sometimes I think I am on a list for nearly every piece of software I use ;) Will try maybe as soon as get motivated again for this issue. Thanks, Stefan
Re: [gentoo-user] Re: korganize-4.7.3 broken
On Wednesday 11 Jan 2012 05:36:39 Frank Steinmetzger wrote: There was not just one occasion when I thought I'd write a simple Qt-based desktop from scratch (e.g in the likes and scope of Xfce). ^^ razor-qt!! [1] havent tried it yet (kdepim dosnt hate me as much) but heard good things about it. [1] http://razor-qt.org/ -- - Yohan Pereira
