Visit Our UNIX and Linux User Community

Contact Us Post Here to Contact Site Administrators and Moderators Question regarding my blog-thread Post 303046078 by Neo on Thursday 23rd of April 2020 09:06:28 AM
Old 04-23-2020
Normally, all attachments uploaded to the forums should be in format:


This is how attachment inserted correctly into the forum posts will look when you edit the post.

Here is an example from one of my posts (in the editor);

Question regarding my blog-thread-screen-shot-2020-04-23-80547-pmjpg

The reason I hid my post is that we will be moving to the new forums soon, and I did not want to annoy you about this.
This User Gave Thanks to Neo For This Post:
Test Your Knowledge in Computers #782
Difficulty: Medium
Bill Gates dropped out of Yale University to start his own company
True or False?

3 More Discussions You Might Find Interesting

1. Programming

How to cancel a thread safely from the initial thread?

how about asynchronous canceling? or with signal? if with signal whether it effects the process? my english so badly :( :( (1 Reply)
Discussion started by: alan.zhao
1 Replies

2. Programming

Question on creation of Thread pool

dear sir/madam presently i am in a process of creating a multithread pool using clone() system call in unix with c programming. i am facing some problem ie., i am able create multithread pool and able to keep all the threads in wait state,but when i call kill (afunction revoke a... (6 Replies)
Discussion started by: Radha
6 Replies

3. Shell Programming and Scripting

Blog-Thread: Creating a Shell Wrapper and Runtime Modifier (SWARM)

SWARM = Shell Wrapper and Runtime Modifier But as a matter of fact, it's more like a Text User Interface framework for scripts. Which was the original title (TUI) of the first split-up iteration from Script-Tools. Script-Tools is still the 'end/final-project', SWARM is just the way to get... (32 Replies)
Discussion started by: sea
32 Replies
ATTACH(5)							File Formats Manual							 ATTACH(5)

attach, session, nop - messages to initiate activity SYNOPSIS
Tnop tag[2] Rnop tag[2] Tsession tag[2] chal[8] Rsession tag[2] chal[8] authid[28] authdom[48] Tattach tag[2] fid[2] uid[28] aname[28] ticket[72] auth[13] Rattach tag[2] fid[2] qid[8] rauth[13] DESCRIPTION
The nop request does nothing overt but may be used to synchronize the channel between two service hosts initially. The session request is used to initialize a connection between a client and a server. All outstanding I/O on the connection is aborted. The set of messages between session requests is called a session. The host's user name (authid) and its authentication domain (authdom) identify the key to be used when authenticating to this host. The exchanged challenges (chal) are used in the authentication algorithm. If authid is a null string no authentication is performed in this session. The tag should be NOTAG (value 0xFFFF) for a nop or session message. The attach message serves as a fresh introduction from a user on the client machine to a server. The message identifies the user (uid) and may select the file tree to access (aname). The ticket and auth arguments contains authorization data derived from the exchanged chal- lenges of the session message; see auth(6). As a result of the attach transaction, the client will have a connection to the root directory of the desired file tree, represented by fid. An error is returned if fid is already in use. The server's idea of the root of the file tree is represented by the returned qid. ENTRY POINTS
An attach transaction will be generated for kernel devices (see intro(3)) when a system call evaluates a file name beginning with Pipe(2) generates an attach on the kernel device pipe(3). The mount system call (see bind(2)) generates an attach messages to the remote file server. When the kernel boots, an attach is made to the root device, root(3), and then an attach is made to the requested file server machine. SEE ALSO
auth(6) ATTACH(5)

Featured Tech Videos

All times are GMT -4. The time now is 12:47 AM.
Unix & Linux Forums Content Copyright 1993-2020. All Rights Reserved.
Privacy Policy