Multiple ttsessions & Common FIle Scope

Thread View: alt.soft-sys.tooltalk

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by Buzz Moschetti Mon, 17 Aug 1992 20:29

Author: Buzz Moschetti
Date: Mon, 17 Aug 1992 20:29

13 lines
1205 bytes

Can two discrete ttsession environments communicate through a common file
scope?  I think not, but I may be wrong.  The environment is: many logins
to one machine, all running non-GUI apps.  OK, that means the .login gets
	exec ttsession -c $SHELL
At boot time, I wish to run a service that supports common needs of ALL the
users' apps; say, for example, ticket printing.  All users (running under
different ttsessions) fire up apps that join a common file /tmp/common_services.
Apps fire "print a ticket" messages into this scope; the "server" registers
interest in them and performs the operation.

So far I can't get it to work.  Am I missing something?  I know that the file
scoping mechanism works if I use the same ttsession (via $SUN_TT_SESSION) but
this solution is not possible.

Re: Multiple ttsessions & Common FIle Scope

Author: Geoffrey Clemm
Date: Tue, 18 Aug 1992 09:12

36 lines
2082 bytes

In article <BUZZ.92Aug17162904@toxicavenger.bear.com> buzz@toxicavenger.bear.com (Buzz Moschetti) writes:
>   Can two discrete ttsession environments communicate through a common file
>   scope?  I think not, but I may be wrong.

It probably is the case that you need: Patch-ID# 100626-03

The problems this patch fixes are:

1085317 session-scoped patterns with no op fail
1074150 ttdbck doesn't open existing DB files and/or dumps core
1074612 crash in tt_message_send on file-scoped queued msg.
1066949 ttdbck -k <objid key> -x -F <file> <database> dumps core
1071723 Crash in tt_file_join("/usr/include/stdio.h") on victoria
1070440 core dump in tt_file_join during otype test
1068765 dbserver incorrectly resolves pathnames when exported symlinks are used
1071035 ToolTalk clients should not have to link with libX
1072772 File scope messages should not require X authority
1081742 auto-started clients that exit after handling cause problems
1077513 If a request is observed by its own sender, he won't be told when it fails.
1082628 Can't add ptype to classing engine DB when messages are start and queue
1084299 auto-starting caused by notices fails
1093746 File scoped messages do not work accross multiple ttsessions.
1095103 TT_BOTH patterns never match any message

In particular, bugid 1093746 says it all.

One question for my old colleagues back at Sun:

How did a bug of this magnitude make it into FCS ???
(Not wanting to put you guys on the spot or anything :-).

Cheers,

Geoff
--
geoff@bellcore.com

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads