Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#21 ISpoofFile not allways written

closed
SHiZNO
Engine (43)
5
2007-01-17
2006-02-03
Anonymous
No

It looks like the ISpoofFile file is not always written
to on connecting to a server. I happens quite often we
get the wrong ident response.

Discussion

  • SHiZNO
    SHiZNO
    2006-02-03

    Logged In: YES
    user_id=1093455

    Can you provide a little more information such as how often
    it happens, can you predict or reproduce the bad behavior
    and how many users you have running inside the one znc instance?

    I haven't ran into this issue so it is going to be a little
    tricky to debug this. If you could send me your config
    (change the passwords) to prozac@rottenboy.com I will try to
    reproduce it. If I can't reproduce, I can provide you with
    some extra debugging info if you're willing to help out.

     
  • Logged In: NO

    We could call flock on the ISpoofFile so that multiple znc
    instances dont interfere with each other.

     
  • Psychon
    Psychon
    2007-01-17

    • status: open --> closed
     
  • Psychon
    Psychon
    2007-01-17

    Logged In: YES
    user_id=1654410
    Originator: NO

    I am closing this now, because i dont think the original author will ever respond again and there is a patch which locks the ISpoofFile using flock.
    I think i havent seen this happening and if it still happens some /msg *status jump should do the trick.