Development/xline.db

From Inspire IRCd (InspIRCd)

This page has been marked as Development Material. Information posted here may be subject to change and/or only available in unstable versions of InspIRCd.

xline.db

(14:25:36) <@Trystan> yea
(14:25:58) <@Trystan> config settings are perm, vrs quick command to do it when need be. theres a few like that
(15:06:47) <+w00t2> I wonder really whether the new xline system shouldn't combine the two optionally
(15:07:15) <+w00t2> i.e. xline.db -> all lines saved when one is updated
(15:07:33) <+w00t2> it would help prevent services having to enforce them, which would be beneficial for large networks i imagine
(15:07:40) <&Om> xline.db!? o_O
(15:07:49) <&Om> do I need to keep up more? :p
(15:07:53) <+w00t2> (i.e. you wouldn't need to burst 20-200 glines, which would then be applied against a few thousand people)
(15:07:56) <+w00t2> Om, i'm theorising
(15:08:23) <+w00t2> i'm saying perhaps we should start storing the bans/etc added through /gline, /cban, etc so they don't always need re-adding on restart
(15:08:39) <+w00t2> it has some disadvantages of course, we'd probably need to write them in a human readable way
(15:08:46) <+w00t2> though i suppose that is easy
(15:09:06) <+w00t2> alternatively we'd need a tool to remove one from the cli in case some idiot managed to ban all opers or something equally ridiculous
(15:09:30) <&Om> I'd go for human-reable
(15:09:33) <&Om> readable
(15:09:36) <+w00t2> same
(15:09:38) <+w00t2> then we could just 
(15:09:48) <+w00t2> <include file="xline.db">
(15:09:48) <&Om> And probably an existing format
(15:09:52) <+w00t2> ^
(15:09:53) <+w00t2> :p
(15:10:03) <&Om> *like* XML
(15:10:06) <@Trystan> w00t2 some idiot user should just be told rm -rf xline.db
(15:10:11) <&Om> ..or the conf format
(15:10:16) <+w00t2> Om, if we save them the exact way we load them now.. :p
(15:10:21) <&Om> yeah yeah :p
(15:10:39) <+w00t2> Trystan: mistakes happen, that's not really a viable solution
(15:10:45) <&Om> possibly with an extra flag in the tag..
(15:10:47) <+w00t2> this behaviour should of course be optional
(15:10:58) <&Om> so you could do bin/inspircd -nosavedxlines
(15:11:02) <+w00t2> not everyone will want us writing files to disk
(15:11:10) <+w00t2> Om, why?
(15:11:15) <&Om> and it could ignore the ones it had written, but keep the ones you'd actually configured
(15:11:22) <&Om> idiot recovery?
(15:11:28) <+w00t2> (15:08:39) <+w00t2> it has some disadvantages of course, we'd probably need to write them in a human readable way
(15:11:28) <+w00t2> (15:08:46) <+w00t2> though i suppose that is easy
(15:11:28) <+w00t2> (15:09:06) <+w00t2> alternatively we'd need a tool to remove one from the cli in case some idiot managed to ban all opers or something equally ridiculous
(15:11:36) <+w00t2> if we write them the same way the conf does
(15:11:39) <+w00t2> they just need to shut down
(15:11:41) <+w00t2> open the file
(15:11:44) <+w00t2> remove the offending line
(15:11:45) <+w00t2> and start
(15:11:46) <&Om> yeah
(15:11:54) <&Om> i was only duggesting an alterntive :<
(15:11:56) <+w00t2> so no need for the -nosaved flag really
(15:11:58) <&Om> suggesting
(15:12:05) * +w00t2 wikifies this