View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000222 | LDMud | Runtime | public | 2004-11-26 22:27 | 2019-08-29 21:29 |
| Reporter | Assigned To | Gnomi | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | fixed | ||
| Summary | 0000222: Driver should pass signals to mudlib | ||||
| Description | Short: Driver should pass signals to the mudlib Date: Wed, 29 Mar 2000 01:27:56 +0200 From: Freaky <Freaky@UNItopia.RUS.Uni-Stuttgart.DE> Type: Feature State: New Ein besserer Signal-Handler wuerde auch gut tun, so dass man z.B. vor einem Crash noch was machen kann, oder besser auf Signale reagieren kann. (see 'Reopening of logfiles' for an application) Ausserdem sollte sie evt. ein Signal-Handling bekommen, dass man z.B. SIG_USR2 einer Master-Funktion zuweisen kann, die dann z.B. das MUD sauber runterfahren kann. Momentan mache ich das ueber den external-Master-reload (SIG_USR1) | ||||
| Tags | No tags attached. | ||||
| External Data (URL) | |||||
|
|
OK, this is half obsolete: re-open the logfiles is now possible with USR2, clean shutdown (in theory) with HUP. The wider issue: should we pass all unknown signals to the mudlib and ignore them after that (ok, some you can't ignore, I know), letting the mudlib decide what to do? |
|
|
Implemented in LDMud 3.5.2. |
