Sponsored Content
Full Discussion: Tynt Tracer Must Die
Contact Us Post Here to Contact Site Administrators and Moderators Tynt Tracer Must Die Post 302416075 by Neo on Saturday 24th of April 2010 08:16:40 PM
Old 04-24-2010
Agreed.

That is also a significant negative. We certainly don't want users to be troubled when they copy-and-paste into editors.

If we were seeing Tynt generating significant attribution links back to the site, then it might make sense to ask posters to opt-out on a broswer-by-browser basis. However, since we are only seeing an insignificant number of attribution links back to the site, the benefit of Tynt does not outweight the negatives for a forum like ours.

We greatly appreciate feedback from our users. Thank you very much.
 

5 More Discussions You Might Find Interesting

1. News, Links, Events and Announcements

Live Free or Die!

Mods: Delete this if you think that this is not appropriate. I found this rather amusing. If you go to www.unix.net now you will see the OpenGroup selling license plates that read "Live Free or Die/Unix/Unix is a trademark of the OpenGroup" (http://www.unix.net/unix_plates.html) I just... (12 Replies)
Discussion started by: auswipe
12 Replies

2. Solaris

what time did my process die ??

Hi there I have a backup script that runs every night and for some reason ive been getting in in the morning and the process has died, Is there any way I can tell when it died? if not .....would anybody recommend some scripting that i could do that would be able to tell me this information ... (3 Replies)
Discussion started by: hcclnoodles
3 Replies

3. UNIX for Dummies Questions & Answers

Python 2.5 must die.

I am using SunOS 5.7 I have installed Python 2.5 via make install Without going into details, I'd like to uninstall it and replace it with an earlier version. Maybe as far back as 2.2.3. Unfortuantely, make uninstall gives me Don't know how to make target 'uninstall'. This is thematically... (2 Replies)
Discussion started by: Dbecker
2 Replies

4. UNIX for Advanced & Expert Users

Shell Script Dependency/Tracer

Hello All, We have a very old system at hand in which there are hundreds of shell scripts that use other shell scripts, all on the same server. There are several that are not used at all as well. In short, it's an unmanaged system thats been lying around for many years, and it needs to be... (12 Replies)
Discussion started by: ag79
12 Replies

5. Shell Programming and Scripting

FTP Connection die out

Hi, I will ftp aroung 80 files after connecting to an FTP Server. But after 2 minutes of connection, it is timed out and connection is dying. Server had a 2 minute connection timeout if connection is idle. But my question, Isn't tranfering files not considered as an activity. Is the connection... (7 Replies)
Discussion started by: vasuarjula
7 Replies
inviso_rt_meta(3erl)					     Erlang Module Definition					      inviso_rt_meta(3erl)

NAME
inviso_rt_meta - Direct API to the Inviso Runtime Component's meta tracer DESCRIPTION
This module provides a direct API to the inviso meta tracer. These functions are only meant to be used in meta tracing CallFunc and Remove- Func . It can sometimes be necessary to manipulate meta match-patterns from CallFunc s and RemoveFunc s. The problem then is that call-funcs and remove-funcs are meta trace call-backs executed inside the inviso meta tracer's context. Hence making calls to the regular API's manipulat- ing meta trace-patterns will hang the inviso meta tracer!. To remedy this problem, a number of useful tpm-functions are available in this API. It must be understood that their actions are local to the Erlang node where they are called. EXPORTS
tpm_ms(Mod,Func,Arity,MSname,MS) -> {ok,0} | {ok,1} | {error,not_initiated} See inviso:tpm_ms/6 for details. Note that this function only effects meta trace-patterns on the Erlang node where the function is called. This also implies that only the local inviso meta tracer's name-database is updated with MSname . tpm_ms_tracer(Mod,Func,Arity,MSname,MS) -> {ok,0} | {ok,1} | {error,not_initiated} See inviso:tpm_ms_ms/6 for details. Note that this function only effects meta trace-patterns on the Erlang node where the function is called. This also implies that only the local inviso meta tracer's name-database is updated with MSname . list_tpm_ms(Mod,Func,Arity) -> [MSname] Returns a list of all MSname in use for Mod:Func/Arity . This can be useful instead of having to have an own-implemented database over currently in use meta match-functions for a particular function. ctpm_ms(Mod,Func,Arity,MSname) -> ok See inviso:ctpm_ms/5 for details. Note that this function only effects meta trace-patterns on the Erlang node where the function is called. This also implies that only the local inviso meta tracer's name-database is updated with MSname . get_tracer() -> Tracer Types Tracer = pid() | port() Returns the pid or port acting as the receiver of regular trace messages. This is useful if it is necessary to manipulate meta trace-patterns by hand (using erlang:trace_pattern/3 ) and the {tracer,Tracer} must be used in one of the match-function bodies. Ericsson AB inviso 0.6.2 inviso_rt_meta(3erl)
All times are GMT -4. The time now is 04:57 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy