Skip to main content
added 58 characters in body
Source Link
Lee Woodman
  • 555
  • 5
  • 18

OK i managed to solve this, the first thread in this question made me check my centos server to see if the mesg y was still in any of the bashrc files and i found the culprit in /etc/bashrc on my centos box. I was logging in from a terminal to whm from Ubuntu (whether Ubuntu made a difference i'm unsure).

OK i managed to solve this, the first thread in this question made me check my centos server to see if the mesg y was still in any of the bashrc files and i found the culprit in /etc/bashrc on my centos box. I was logging in from a terminal to whm.

OK i managed to solve this, the first thread in this question made me check my centos server to see if the mesg y was still in any of the bashrc files and i found the culprit in /etc/bashrc on my centos box. I was logging in from a terminal to whm from Ubuntu (whether Ubuntu made a difference i'm unsure).

Source Link
Lee Woodman
  • 555
  • 5
  • 18

OK i managed to solve this, the first thread in this question made me check my centos server to see if the mesg y was still in any of the bashrc files and i found the culprit in /etc/bashrc on my centos box. I was logging in from a terminal to whm.