On 2013-04-08 17:13, Gibney, Dave wrote: > # fuser -cu /tmp > > /SYSTEM/tmp: 67108942c(OEDFLTU) 130c(OEDFLTU) 132c(OEDFLTU) 133c(OEDFLTU) > 134c(OEDFLTU) 135c(OEDFLTU) 136c(OEDFLTU) 137c(OEDFLTU) 13 > 8c(OEDFLTU) 139c(OEDFLTU) 140c(OEDFLTU) 141c(OEDFLTU) 142c(OEDFLTU) > 143c(OEDFLTU) 144c(OEDFLTU) 145c(OEDFLTU) 146c(OEDFLTU) 50331805 > c(OEDFLTU) 16777953(OMVSKERN) 83887581c(OEDFLTU) > > > And It would be disruptive to stop some of these after going through the > exercise of mapping them to active address spaces. Note 2nd to last is > OMVSKERN > Is that your list or the OP's list.
Is OEDFLTU the OMVS Default User? If so, there's a good argument here for assigning unique UIDs so culprits such as these can more readily be identified. Why are so many users using /tmp as their CWD? (Is that the norm for default user? There may be an argument here for not using /tmp as HOME.) I notice that merely by logging in, I get two handles on /tmp which persist until I log out; command is rlogind2. I wonder why? I haven't superuser, so I can't see other users' handles. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
