Search Results

Well, scp is free, too, and the rcp family is considered a security problem many places.

rcp sends files, so if they wll when to an incoming directory with names that reflected the sender and...

xinetd/inetd/u_inetd are more tcp related, for independent services, so 1) you would have to worry about parallel operation and 2) the overhead per message is high unless the protocol maintains the...

A common dir means there is only one place to look when woken up to process input. The file name itself can contain unique information like what user sent it and what the sequence number is. A "kill...

There may be a hundred scripts running with the same name, but they will all have different process ID's. No. The usual procedure is for a process to save a file under /var/run/ somewhere containing...

Yes, kill is named for it's most popular use, termination, but it is just a signal sender.

in shell, trap is the shell signal catcher. SIGINT was available, but for apps SIGUSR1 and SIGUSR2 are...

A signal is a way to tell a program to do something when told instead of constantly checking for something. If it hasn't been told to do anything when it gets the signal, the signal will probably...

Polling is an architectural choice. If the originators have a subscription list or a common destination, they can push. Polling is about pulling information that may not exist yet. Then there are...

Oddly enough, that approach sounds a lot like how an email originated. It could work. Polling is never efficient but if more sensible method are denied you nothing better pops to mind.

Writing to the tty of another user usually has permission problems. If you have one window for the discussion, which is "tail -f mtg_file" and one for comments 'while read l ;do echo `id -un`": $l"...

Well, scripts and commands they can call, apparently.

One paradigm that might work for you is to have users drop comments as files in a dir, and have a daemon gor around polling all the comments...

talk is positively ancient, and seems to use ancient BSD networking protocols no longer extant. If you can get it, ntalk seems the more modern equivalent.

wall and write are for sending messages to local terminals. They do not send messages across the network.

Regards,
Alister

Some sort of JAVA or PERL app would be very portable and consistent across O/S.

If you want it to be utterly open, you might write something using UDP on a fixed high port and broadcast messages. It works to run at least one big name stock exchange. I suppose you might want...

I suppose it depends on what you call sending a message. email works for most of us. You can ssh between hosts, but to message people youu need to find specific tty names as well. If you want them...