commit c90f903a667ed5744b93b6b89892de4e8c045d17
Author: Stephen Bennett <spb@exherbo.org> Date: Fri Dec 31 17:14:05 2010 +0000 Expire umode +p correctly if it's set via oper_umodes, as well as by user_mode. Bug found by tgies.
This commit is contained in:
parent
bd73ea56ba
commit
8c76e73bcf
|
@ -1430,6 +1430,13 @@ oper_up(struct Client *source_p, struct oper_conf *oper_p)
|
||||||
user_join(&me, source_p, aconf->autojoin_opers, NULL);
|
user_join(&me, source_p, aconf->autojoin_opers, NULL);
|
||||||
}
|
}
|
||||||
|
|
||||||
|
/* If we're setting +p, expire it */
|
||||||
|
if(ConfigFileEntry.expire_override_time && MyClient(source_p) && source_p->umodes & UMODE_OVERRIDE)
|
||||||
|
{
|
||||||
|
source_p->localClient->override_timeout_event =
|
||||||
|
rb_event_addonce("expire_override", expire_umode_p, source_p, ConfigFileEntry.expire_override_time);
|
||||||
|
}
|
||||||
|
|
||||||
return (1);
|
return (1);
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue