| Art Alexion on 3 Nov 2006 13:06:26 -0000 |
|
On Thursday 02 November 2006 15:49, Will Dyson wrote: > On 11/1/06, Art Alexion <art.alexion@verizon.net> wrote: > > On Wednesday 01 November 2006 02:17, Will Dyson wrote: > > > On 10/31/06, Art Alexion <art.alexion@verizon.net> wrote: > > > > Right. That is the problem. The script is 20hal. It starts hald. > > > > I attached it earlier. I don't think the script itself is the > > > > problem, though, because I can't start hal in daemonized mode even > > > > without the script. > > > > > > Hmm. If you run 'hald --daemon=no' in a terminal, do the things that > > > depend on it start working? Like lshal, for example. That would be > > > strange if it did, I think. > > > > I don't know. > > > > > So lets see what is going wrong with hald in daemonize mode. As > > > Stephen pointed out, strace takes an -f argument to follow children of > > > the traced program. Using it should reveal what is going on with it in > > > daemonize mode. > > > > > > # strace -f -o hald.strace -s 150 hald > > > > This command basically froze the terminal for a couple of hours until I > > killed hald from another terminal. There was a resulting file, but it > > was over 13 MB, so I ran it again to get this smaller file. Again, the > > attachment is sent off-list. > > Sorry Art, > > It looks like you killed hald before it had a chance for the 250 > second time-out to fire. I would be somewhat interested in seeing a > longer run (gzip the output). I'll send or post under separate cover. > > In this trace, it appeared to be still working on probing your serial > ports when killed. It thinks you have 48 serial ports, btw. This could > be one reason it is taking longer than 250 seconds to startup. I'll let it run for 6 minutes. > > It is doing a fair amount of work to probe each port, which apparently > includes re-reading all of its xml config files and forking a child. > Nobody has accused hald of being efficient :( > > Could you post the output of 'ls -l /dev/ttyS*' please? My system > shows just the 4 entries that you would expect. Is your udev getting > confused for some reason? arthur@rodney:~/Desktop $ ls -l /dev/ttyS* crw-rw---- 1 root dialout 4, 64 2006-10-30 14:21 /dev/ttyS0 crw-rw---- 1 root dialout 4, 65 2006-10-28 04:42 /dev/ttyS1 crw-rw---- 1 root dialout 4, 74 2006-10-28 04:42 /dev/ttyS10 crw-rw---- 1 root dialout 4, 75 2006-10-28 04:42 /dev/ttyS11 crw-rw---- 1 root dialout 4, 76 2006-10-28 04:42 /dev/ttyS12 crw-rw---- 1 root dialout 4, 77 2006-10-28 04:42 /dev/ttyS13 crw-rw---- 1 root dialout 4, 78 2006-10-28 04:42 /dev/ttyS14 crw-rw---- 1 root dialout 4, 79 2006-10-28 04:42 /dev/ttyS15 crw-rw---- 1 root dialout 4, 80 2006-10-28 04:42 /dev/ttyS16 crw-rw---- 1 root dialout 4, 81 2006-10-28 04:42 /dev/ttyS17 crw-rw---- 1 root dialout 4, 82 2006-10-28 04:42 /dev/ttyS18 crw-rw---- 1 root dialout 4, 83 2006-10-28 04:42 /dev/ttyS19 crw-rw---- 1 root dialout 4, 66 2006-10-28 04:42 /dev/ttyS2 crw-rw---- 1 root dialout 4, 84 2006-10-28 04:42 /dev/ttyS20 crw-rw---- 1 root dialout 4, 85 2006-10-28 04:42 /dev/ttyS21 crw-rw---- 1 root dialout 4, 86 2006-10-28 04:42 /dev/ttyS22 crw-rw---- 1 root dialout 4, 87 2006-10-28 04:42 /dev/ttyS23 crw-rw---- 1 root dialout 4, 88 2006-10-28 04:42 /dev/ttyS24 crw-rw---- 1 root dialout 4, 89 2006-10-28 04:42 /dev/ttyS25 crw-rw---- 1 root dialout 4, 90 2006-10-28 04:42 /dev/ttyS26 crw-rw---- 1 root dialout 4, 91 2006-10-28 04:42 /dev/ttyS27 crw-rw---- 1 root dialout 4, 92 2006-10-28 04:42 /dev/ttyS28 crw-rw---- 1 root dialout 4, 93 2006-10-28 04:42 /dev/ttyS29 crw-rw---- 1 root dialout 4, 67 2006-10-28 04:42 /dev/ttyS3 crw-rw---- 1 root dialout 4, 94 2006-10-28 04:42 /dev/ttyS30 crw-rw---- 1 root dialout 4, 95 2006-10-28 04:42 /dev/ttyS31 crw-rw---- 1 root dialout 4, 96 2006-10-28 04:42 /dev/ttyS32 crw-rw---- 1 root dialout 4, 97 2006-10-28 04:42 /dev/ttyS33 crw-rw---- 1 root dialout 4, 98 2006-10-28 04:42 /dev/ttyS34 crw-rw---- 1 root dialout 4, 99 2006-10-28 04:42 /dev/ttyS35 crw-rw---- 1 root dialout 4, 100 2006-10-28 04:42 /dev/ttyS36 crw-rw---- 1 root dialout 4, 101 2006-10-28 04:42 /dev/ttyS37 crw-rw---- 1 root dialout 4, 102 2006-10-28 04:42 /dev/ttyS38 crw-rw---- 1 root dialout 4, 103 2006-10-28 04:42 /dev/ttyS39 crw-rw---- 1 root dialout 4, 68 2006-10-28 04:42 /dev/ttyS4 crw-rw---- 1 root dialout 4, 104 2006-10-28 04:42 /dev/ttyS40 crw-rw---- 1 root dialout 4, 105 2006-10-28 04:42 /dev/ttyS41 crw-rw---- 1 root dialout 4, 106 2006-10-28 04:42 /dev/ttyS42 crw-rw---- 1 root dialout 4, 107 2006-10-28 04:42 /dev/ttyS43 crw-rw---- 1 root dialout 4, 108 2006-10-28 04:42 /dev/ttyS44 crw-rw---- 1 root dialout 4, 109 2006-10-28 04:42 /dev/ttyS45 crw-rw---- 1 root dialout 4, 110 2006-10-28 04:42 /dev/ttyS46 crw-rw---- 1 root dialout 4, 111 2006-10-28 04:42 /dev/ttyS47 crw-rw---- 1 root dialout 4, 69 2006-10-28 04:42 /dev/ttyS5 crw-rw---- 1 root dialout 4, 70 2006-10-28 04:42 /dev/ttyS6 crw-rw---- 1 root dialout 4, 71 2006-10-28 04:42 /dev/ttyS7 crw-rw---- 1 root dialout 4, 72 2006-10-28 04:42 /dev/ttyS8 crw-rw---- 1 root dialout 4, 73 2006-10-28 04:42 /dev/ttyS9 I've never been happy with udev, even with earlier releases. Getting it to recognize my Palm phone was such a problem that I gave up and sync with the serial, rather than usb port. > > Also, have you tried simply reinstalling the udev and hal packages? I have reinstalled hal and dbus twice with no change. Once with an apt-get --reinstall and another where I first removed, then installed. I will try to reinstall udev this time. > Please try reinstalling the udev package first, as I suspect that is > the root of the problem. -- _____________________________________________________________ Art Alexion Arthur S. Alexion LLC PGP fingerprint: 52A4 B10C AA73 096F A661 92D2 3B65 8EAC ACC5 BA7A The attachment - signature.asc - is my electronic signature; no need for alarm. Info @ http://mysite.verizon.net/art.alexion/encryption/signature.asc.what.html _____________________________________________________________ Attachment:
pgpAuhFvWKVF4.pgp ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|