On 1/11/07, bardo <[EMAIL PROTECTED]> wrote: > Not sure about the cause, but as a workaround you could start the > network daemon in background by prepending an '@' in rc.conf, like > @network. This way it will timeout, but only in the background. Maybe > it won't solve the problem, if it waits for the daemon to > fail/succeed.
This would be the perfect solution, but running it in the background might end up having the ifplugd daemon run before it, and that is what screws up gkrellm. (In fact, if the ifplugd daemon runs before it, it simply won't work.) Though I could do that and forget about ifplugd alltogether. (I'll do that temporarily.) A better solution would be to add a choice in the init script, something like "Would you like to start the network daemon?" That way I can start it when I have a cable, and not start it when I don't have it. I don't know much about how init scripts work though, nor do I know how to do this. It should probbably be fairly simple. On 1/11/07, bardo <[EMAIL PROTECTED]> wrote: > To find out where the problem is, just after booting with ifplugd > start "strace gkrellm" from a console and you'll see all gkrellms > system calls. You'll then find out what it's looking for when it > hangs. I'll admit to not having enough intelligence to understand its output. I did try though. I'll pastebin it if you want. _______________________________________________ arch mailing list [email protected] http://www.archlinux.org/mailman/listinfo/arch
