View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001409 | unreal | ircd | public | 2003-12-05 00:00 | 2003-12-05 14:57 |
| Reporter | w00t | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | sometimes |
| Status | closed | Resolution | open | ||
| Product Version | 3.2-beta16 | ||||
| Summary | 0001409: /rehash | ||||
| Description | Can we do some clarification of /rehash please? One would expect /rehash <server> to reload _everything_ yet it doesnt reload MOTD, me {} etc. As another sideline, if I create an oper {} and rehash, it doesnt seem to work all the time... | ||||
| Additional Information | Don't know if I have said this before, but I generally have to restart the IRCd to get it to work. This is _not_ human error here. I edit the IRCd conf, add it in and do a rehash and then attempt to oper... no workies ;) Anyone else had a similar problem? | ||||
| 3rd party modules | |||||
|
|
beta16??? |
|
|
*sigh*... Yeah, havent had the time to login to the shell and upgrade. Not a major problem since my server is no longer a hub ;) Still, b19 HAS been uploaded :D yay! And until I took matters into hand, we were running Unreal3.1.5.1-Valek (?) So we are better off. We have other servers running b19 and the issue appears common. |
|
|
There were several remote rehash bugs 3 versions ago (did not work if >1 hop for example). And if you weren't oper at that serv you prolly wouldn't see any (error) notices. Perhaps that caused your oper block confusion (coz tested&works _fine_ at beta19). You are right however that '/rehash <server>' didn't reload the motd/rules files. Fixed in CVS (.1997). |
