#22044 closed defect (fixed)
aiccu: kextstat always returns 0 now, startup script needs to be revised
Reported by: | packwidth@… | Owned by: | cr@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.8.1 |
Keywords: | Cc: | jmroot (Joshua Root), ryandesign (Ryan Carsten Schmidt) | |
Port: | aiccu |
Description (last modified by blb@…)
It appears that
kextstat -lb foo.tun
always returns 0 in 10.6.1, even if foo.tun isn't loaded. To work around this, the LaunchDaemon wrapper script could use
kextstat -l|grep -q foo.tun
instead.
Change History (7)
comment:1 follow-up: 2 Changed 15 years ago by blb@…
Description: | modified (diff) |
---|
comment:2 Changed 15 years ago by packwidth@…
Replying to blb@…:
Is this against the tuntaposx port?
While the aiccu port depends on tuntaposx, it seems to try to load foo.tun itself before it starts up. As tuntaposx loads both foo.tun and foo.tap in its own startup script, this whole exercise could probably be dropped altogether.
comment:3 Changed 15 years ago by blb@…
Cc: | cr@… added |
---|---|
Keywords: | aiccu added |
Owner: | changed from macports-tickets@… to febeling@… |
Port: | tuntaposx added |
comment:4 Changed 14 years ago by jmroot (Joshua Root)
Owner: | changed from febeling@… to macports-tickets@… |
---|
comment:5 Changed 14 years ago by jmroot (Joshua Root)
Cc: | cr@… removed |
---|---|
Keywords: | aiccu removed |
Owner: | changed from macports-tickets@… to cr@… |
Port: | aiccu added; tuntaposx removed |
Summary: | kextstat always returns 0 now, startup script needs to be revised → aiccu: kextstat always returns 0 now, startup script needs to be revised |
It doesn't appear that this was ever a problem with tuntaposx.
comment:6 Changed 14 years ago by jmroot (Joshua Root)
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:7 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Cc: | jmr@… ryandesign@… added |
---|
Shouldn't this get a revision bump as well?
Note: See
TracTickets for help on using
tickets.
Is this against the tuntaposx port?