This issue also affects the 6.2.1.0 client. I received the note below from a 
client admin. His is a LinuxX86 node running TSM 6.2.1.0. Has this been fixed 
in a later client?

Thank you,
Keith

--------------------------------------
dsmc segfaults on startup:

[root@i136 ~]# dsmc sched
Segmentation fault
[root@i136 ~]#

Looking at the trace for dsmc, it seems to have a problem with /etc/issue:

.....
mmap2(NULL, 25462, PROT_READ, MAP_SHARED, 3, 0) = 0xfffffffff78f7000
close(3)                                = 0
futex(0x57fa4c, FUTEX_WAKE_PRIVATE, 2147483647) = 0
open("/dev/tty", O_RDONLY|O_LARGEFILE)  = 3
ioctl(3, SNDCTL_TMR_TEMPO or TCGETA, {B38400 opost isig icanon echo
...}) = 0
close(3)                                = 0
brk(0x88cd000)                          = 0x88cd000
uname({sys="Linux", node="i136", ...})  = 0
open("/etc/issue", O_RDONLY|O_LARGEFILE) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=206, ...}) = 0
mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0xfffffffff78f6000
read(3, "\nWelcome to India.FutureGrid.Org"..., 4096) = 206
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++
[root@i136 ~]#

I removed the content from /etc/issue, and dsmc starts without problems.