04-02-2014
Hi Palak,
Don't worry. When you are active here, for example by posting a question, you receive bits. When you get an infraction you lose bits. You'll be back in the positive in no time.
We have some rules and guidelines that we found necessary so these forums function well..
You can read them here:
the forum rules, but here is quick copy of the rules.
Quote:
RULES OF THE UNIX AND LINUX FORUMS
(1) No flames, shouting (all caps), sarcasm, bullying, profanity or arrogant posts.
(2) No negative comments about others or impolite remarks. Be patient.
(3) Refrain from idle chatter that does not contribute to the knowledge base. This does not apply to the forums in The Unix Lounge which are for off-topic discussions.
(4) Do not 'bump up' questions if they are not answered promptly. No duplicate or cross-posting and do not report a post or send a private message where your goal is to get an answer more quickly.
(5) Search the forums database with your keywords before asking.
(6) Do not post classroom or homework problems.
(7) No job postings from headhunters or recruiters except in The Unix Forums Job Board. See How to Post to The UNIX Forums Job Board for information on using the Job Board.
(8) No BSD vs. Linux vs. Windows or similar threads.
(9) Edit your posts if you see spelling or grammar errors (don't write in cyberchat or cyberpunk style). English only.
(10) Don't post your email address and ask for an email reply. Don't send a private message with a technical question. The forums are for the benefit of all, so all Q&A should take place in the forums.
(11) Post questions with descriptive subjects. For example, do not post questions with subjects like "Help Me!", "Urgent!!" or "Doubt". Post subjects like "Execution Problems with Cron" or "Help with Backup Shell Script".
(12) These are not hacker boards so hacker related posts will be promptly deleted or moderated.
(13) The forum administrators reserve the right to prune, move or edit posts that do not adhere to the rules or are technically inaccurate.
(14) The forum administrators reserve the right to remove users or change their posting status to read only without notice if any rules are not followed.
(15) No smoking in the forums.
Cheers.
The UNIX and Linux Forums
Last edited by Scrutinizer; 04-02-2014 at 01:15 AM..
This User Gave Thanks to Scrutinizer For This Post:
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello all,
I was wondering if anyone can tell me how to change 24 bits depth display to 8 bits depth display for Sun Ultra1, running Solaris 8? THANKS in advance. I think that the command is ffbconfig, but it has nothing about depth. (4 Replies)
Discussion started by: larry
4 Replies
2. UNIX for Dummies Questions & Answers
Hi.
I want to know how can I negate a write permission for a file to an expecific user when that user have that permission becouse he belongs to a group what have a write permission for the file. (4 Replies)
Discussion started by: sickoboy
4 Replies
3. Programming
Function: int fcntl(int fd, int cmd, struct flock * lock)
Data Type: struct flock
This structure is used with the fcntl function to describe a file lock. It has these members:
off_t l_start
This specifies the offset of the start of the region to which the lock applies, and... (1 Reply)
Discussion started by: DNAx86
1 Replies
4. AIX
Hello there:
I know that exist a procedure to convert an OS using 32bits kernel to 64 bits kernel. But, exist a procedure to convert an OS using 64bits to 32 bits kernel?
Please help me.
Regards. (2 Replies)
Discussion started by: GEIER
2 Replies
5. UNIX for Dummies Questions & Answers
people i have a problem i have a 32 bits sparc processor, and solaris 64 bits processor, i install a oracle data base 64 bits, but my oracle will not run because my processor is from 32 bits this is ok??, i know if i have x86 i cannot install a 64 bits operatin system in a 32 bits processor.
... (0 Replies)
Discussion started by: enkei17
0 Replies
6. Shell Programming and Scripting
How to change value in column 5 to negative based on value in column 2 ?
Example: For all records with A in column 2 change value in column 5 to negative.
file
Code:
1234~A~b~c~10~e~f~g~h~09/10/09
1234~A~b~c~75~e~f~g~h~11/12/10
1234~A~b~c~40~e~f~g~h~12/06/10
5678~B~b~c~2~e~f~g~h~01/11/11... (4 Replies)
Discussion started by: sigh2010
4 Replies
7. What is on Your Mind?
Ten movies have been nominated as best motion picture by the International Press Academy, presentation of the 2012 Satellite Awards will be held on 16th December at Los Angeles, CA.
Place your bits here on one of the below nominated movie of your choice:-
Argo
... (0 Replies)
Discussion started by: Yoda
0 Replies
LEARN ABOUT CENTOS
listen
LISTEN(7) PostgreSQL 9.2.7 Documentation LISTEN(7)
NAME
LISTEN - listen for a notification
SYNOPSIS
LISTEN channel
DESCRIPTION
LISTEN registers the current session as a listener on the notification channel named channel. If the current session is already registered
as a listener for this notification channel, nothing is done.
Whenever the command NOTIFY channel is invoked, either by this session or another one connected to the same database, all the sessions
currently listening on that notification channel are notified, and each will in turn notify its connected client application.
A session can be unregistered for a given notification channel with the UNLISTEN command. A session's listen registrations are
automatically cleared when the session ends.
The method a client application must use to detect notification events depends on which PostgreSQL application programming interface it
uses. With the libpq library, the application issues LISTEN as an ordinary SQL command, and then must periodically call the function
PQnotifies to find out whether any notification events have been received. Other interfaces such as libpgtcl provide higher-level methods
for handling notify events; indeed, with libpgtcl the application programmer should not even issue LISTEN or UNLISTEN directly. See the
documentation for the interface you are using for more details.
NOTIFY(7) contains a more extensive discussion of the use of LISTEN and NOTIFY.
PARAMETERS
channel
Name of a notification channel (any identifier).
NOTES
LISTEN takes effect at transaction commit. If LISTEN or UNLISTEN is executed within a transaction that later rolls back, the set of
notification channels being listened to is unchanged.
A transaction that has executed LISTEN cannot be prepared for two-phase commit.
EXAMPLES
Configure and execute a listen/notify sequence from psql:
LISTEN virtual;
NOTIFY virtual;
Asynchronous notification "virtual" received from server process with PID 8448.
COMPATIBILITY
There is no LISTEN statement in the SQL standard.
SEE ALSO
NOTIFY(7), UNLISTEN(7)
PostgreSQL 9.2.7 2014-02-17 LISTEN(7)