Summary: | net.eth1 keeps restarting | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | ebfe <knabberknusperhaus> |
Component: | [OLD] baselayout | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | 2006.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: | the /etc/conf.d/net |
Description
ebfe
2006-10-23 16:02:35 UTC
Please attach your /etc/conf.d/net Created attachment 100332 [details]
the /etc/conf.d/net
Looks like predown() show be postdown() Also, net scripts are re-entrant and I'd guess that you want to check for that by putting this at the top of each custom function. ${IN_BACKGROUND} && return 0 The changes don't affect the service's behaviour. As I cannot resolve this to not being a hardware issue, i change the resolution to invalid. What bugs me is the fact that the service itself is stopped and restarted over and over. A hardware bug, killing the nic after a while shouldn't be able to trigger the service. (In reply to comment #4) > What bugs me is the fact that the service itself is stopped and restarted over > and over. A hardware bug, killing the nic after a while shouldn't be able to > trigger the service. It's probably wpa_supplicant getting all fussey because you're messing with the kill switch. Does it work if you remove your preup/postdown functions? same problem without the hooks. the killswitch doesnt affect the nic's ability to accept iwconfig/wpa_supplicant calls. it just doenst transmit a damn thing. also the problem of the service suddendly stopping and restarting occurs some twenty minutes after it has been started the first time. again, I don't understand why the service stops in the first place. (In reply to comment #6) > again, I don't understand why the service stops in the first place. wpa_supplicant stops itself with IN_BACKGROUND=true when link is lost. Maybe this is what you're seeing - check your logs. |