#41767 closed defect (fixed)
chkrootkit 0.49 runtime binaries not found
Reported by: | dazuelos (dan) | Owned by: | ryandesign (Ryan Carsten Schmidt) |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 2.2.1 |
Keywords: | Cc: | ||
Port: | chkrootkit |
Description (last modified by ryandesign (Ryan Carsten Schmidt))
MacOS X: 10.8.3
port install chkrootkit
--> OK
On running it, a few related binaries are not found:
Checking `sniffer'... not tested: can't exec ./ifpromisc Checking `wted'... not tested: can't exec ./chkwtmp Checking `z2'... not tested: can't exec ./chklastlog Checking `chkutmp'... not tested: can't exec ./chkutmp
These binaries are correctly installed:
$ ls -l /opt/local/bin/chkutmp -rwxr-xr-x 1 root admin 4296 Nov 25 16:31 /opt/local/bin/chkutmp $
Change History (9)
comment:1 Changed 11 years ago by dazuelos (dan)
comment:2 follow-up: 5 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Description: | modified (diff) |
---|---|
Keywords: | chkrootkit removed |
Port: | chkrootkit added; sysutils/chkrootkit removed |
I've fixed it; see WikiFormatting for more information.
comment:3 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Owner: | changed from macports-tickets@… to ryandesign@… |
---|---|
Status: | new → assigned |
chkrootkit appears to expect you to run it from the directory it was compiled in. I'll see if I can fix it to work from its installed location.
comment:4 follow-up: 7 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
comment:5 Changed 11 years ago by dazuelos (dan)
Replying to ryandesign@…:
I've fixed it; see WikiFormatting for more information.
Thank for the fix + thank for the doc ;). Is there any easy way to ask for a Wiki interface where a typed 'return' means
return?
Is this such a foolish request?
comment:6 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
We use Trac, so we're bound to its wiki syntax.
comment:7 Changed 11 years ago by dazuelos (dan)
Replying to ryandesign@…:
I think you rightly analysed the fault (use of ./ rather than standard PATH).
How may I test it?
comment:8 follow-up: 9 Changed 11 years ago by ryandesign (Ryan Carsten Schmidt)
Run:
sudo port selfupdate sudo port upgrade outdated
comment:9 Changed 11 years ago by dazuelos (dan)
Replying to ryandesign@…:
sudo port selfupdate sudo port upgrade outdated
Tested: OK. Nice & fast fix!
How may I fix the original presentation of this ticket which was correctly written but ended up as a piece of bulk unreadable text? All returns were eaten leading to endless lines, and I saw this formatting uggliness after having spent too much time formatting a decent message?