> Being able to assure by default that all of a user's spawned processes are terminated when the user logs out is a much more secure default behavior than the o

> Being able to assure by default that all of a user's spawned processes are terminated when the user logs out is a much more secure default behavior than the opposite. When the user has explicitly requested that processes not terminate when he hangs up by using the nohup command, that is precisely what not to do. This is fundamentally broken behaviour. > Besides, the release notes provided the workaround in line, so that interested users wouldn't have to hunt for a solution. In honour of Towel Day: Mr Prosser: But, Mr Dent, the plans have been available in the local planning office for the last nine months. Arthur: Oh yes, well as soon as I heard I went straight round to see them, yesterday afternoon. You hadn’t exactly gone out of your way to call attention to them had you? I mean like actually telling anybody or anything. Mr Prosser: But the plans were on display… Arthur: On display? I eventually had to go down to the cellar to find them. Mr Prosser: That’s the display department. Arthur: With a torch. Mr Prosser: The lights had probably gone out. Arthur: So had the stairs. Mr Prosser: But look, you found the notice, didn’t you? Arthur: Yes yes I did. It was on display at the bottom of a locked filing cabinet stuck in a disused lavatory with a sign on the door saying beware of the leopard. End users cannot be expected to read the release notes for each release of something their distribution forces on them.