Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Can't get to the first problem because of HN hug but anyway there are fake ways to "solve" it like renaming the logfile (what they test for solved is provided).


This is a self-test, not a certification. The goal is not to defeat the verification goal, but to learn something. So yeah, it's perfectly acceptable that the tests are not bullet-proof.


Depends on how the broken program writes to the log.

If it does

    while true; do echo hello >> bad.log; done
Then renaming bad.log will not solve the challenge.


Replace it with a symlink to /dev/null! Or /dev/full if we feel like it.

(Yes, these are bad solutions, since the instructions explicitly said to stop the process which is writing.)


It will still keep writing to an open inode


No, the “while” loop I was commenting would not.


There are ways to cheat but not so simple; there's a script that checks for the solution and a hash of the script is checked for modifications.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: