01-14-2013
Thank you for the quick reply.
10 More Discussions You Might Find Interesting
1. IP Networking
Hey guys, I have just started using IP tables and was wondering if anyone could direct me to any good online resources as I am totally new to this. Thanks. (1 Reply)
Discussion started by: 182x
1 Replies
2. IP Networking
Trying to create a whitelist to limit bandwidth. My sync speed is 1536/256 kbps.
Simple rules in order:
1. Do not limit (or set to 1536/256) MAC 00:00:00:00:00 (computer is in 192.168.1.0/24).
2. Do not limit (or set to 1536/256) MAC 00:00:00:00:01 (computer is in 192.168.1.0/24).
3. Do not... (1 Reply)
Discussion started by: kripz
1 Replies
3. IP Networking
Thanks in advance
I have to remove ip_tables_name from /proc/net/...
i was trying to do so and getting the following error
cmd : rm ip_tables_names
error : rm: remove regular empty file `ip_tables_names'? y
rm: cannot remove `ip_tables_names': Operation not permitted (4 Replies)
Discussion started by: sudeepiit
4 Replies
4. IP Networking
I have a CentOS 5.2 (10.20.21.73) machine that I need help with configuring iptables. According to documentation I believe this line should allow all communication between my machine and another machine (other machine has no firewall)
-A RH-Firewall-1-INPUT -s 10.20.21.12 -j ACCEPT
#... (1 Reply)
Discussion started by: beaker457
1 Replies
5. IP Networking
What should be the iptables rule so that only the subnet 64.61.11.224/255.255.255.248 may access the mysql port 3306 (1 Reply)
Discussion started by: proactiveaditya
1 Replies
6. IP Networking
Hello
We have one linux machine in the office which happens to be an important firewall. I just know the basics and need to make one change
Essentially it is forward mysql traffic to another internal machine.
This is the original rule (forward to 192.20.0.17) which is working
... (0 Replies)
Discussion started by: rina5392
0 Replies
7. UNIX for Dummies Questions & Answers
Hi,
On the IPTABLES, I did iptables --flush. I want to start fresh. Now I only want two things. Allow one ip address to this server. Allow port 443 as incoming from every where. Please advice how to do this.
This is what I did so for.
iptables -I INPUT -i eth0 -s 1.2.3.4 -j ACCEPT... (5 Replies)
Discussion started by: samnyc
5 Replies
8. IP Networking
photo... (1 Reply)
Discussion started by: beerpong1
1 Replies
9. Red Hat
Hi
I enable the IPtables but port 80 was not working. Below is my active configuration (10 Replies)
Discussion started by: ranjancom2000
10 Replies
10. Ubuntu
Hi
I need help with an iptables configuration, this is what I have
server A
Server B
A and B are using different gateways
i am sending port 22 from A to B, I see the packages coming in B but B is not sending the package to internet. please give me some examples. (0 Replies)
Discussion started by: lmartinez073
0 Replies
LEARN ABOUT CENTOS
xcb_randr_get_crtc_gamma_blue_length
xcb_randr_get_crtc_gamma(3) XCB Requests xcb_randr_get_crtc_gamma(3)
NAME
xcb_randr_get_crtc_gamma -
SYNOPSIS
#include <xcb/randr.h>
Request function
xcb_randr_get_crtc_gamma_cookie_t xcb_randr_get_crtc_gamma(xcb_connection_t *conn, xcb_randr_crtc_t crtc);
Reply datastructure
typedef struct xcb_randr_get_crtc_gamma_reply_t {
uint8_t response_type;
uint8_t pad0;
uint16_t sequence;
uint32_t length;
uint16_t size;
uint8_t pad1[22];
} xcb_randr_get_crtc_gamma_reply_t;
Reply function
xcb_randr_get_crtc_gamma_reply_t *xcb_randr_get_crtc_gamma_reply(xcb_connection_t *conn, xcb_randr_get_crtc_gamma_cookie_t cookie,
xcb_generic_error_t **e);
Reply accessors
uint16_t *xcb_randr_get_crtc_gamma_red(const xcb_randr_get_crtc_gamma_request_t *reply);
int xcb_randr_get_crtc_gamma_red_length(const xcb_randr_get_crtc_gamma_reply_t *reply);
xcb_generic_iterator_t xcb_randr_get_crtc_gamma_red_end(const xcb_randr_get_crtc_gamma_reply_t *reply);
uint16_t *xcb_randr_get_crtc_gamma_green(const xcb_randr_get_crtc_gamma_request_t *reply);
int xcb_randr_get_crtc_gamma_green_length(const xcb_randr_get_crtc_gamma_reply_t *reply);
xcb_generic_iterator_t xcb_randr_get_crtc_gamma_green_end(const xcb_randr_get_crtc_gamma_reply_t *reply);
uint16_t *xcb_randr_get_crtc_gamma_blue(const xcb_randr_get_crtc_gamma_request_t *reply);
int xcb_randr_get_crtc_gamma_blue_length(const xcb_randr_get_crtc_gamma_reply_t *reply);
xcb_generic_iterator_t xcb_randr_get_crtc_gamma_blue_end(const xcb_randr_get_crtc_gamma_reply_t *reply);
REQUEST ARGUMENTS
conn The XCB connection to X11.
crtc TODO: NOT YET DOCUMENTED.
REPLY FIELDS
response_type
The type of this reply, in this case XCB_RANDR_GET_CRTC_GAMMA. This field is also present in the xcb_generic_reply_t and can be
used to tell replies apart from each other.
sequence The sequence number of the last request processed by the X11 server.
length The length of the reply, in words (a word is 4 bytes).
size TODO: NOT YET DOCUMENTED.
DESCRIPTION
RETURN VALUE
Returns an xcb_randr_get_crtc_gamma_cookie_t. Errors have to be handled when calling the reply function xcb_randr_get_crtc_gamma_reply.
If you want to handle errors in the event loop instead, use xcb_randr_get_crtc_gamma_unchecked. See xcb-requests(3) for details.
ERRORS
This request does never generate any errors.
SEE ALSO
AUTHOR
Generated from randr.xml. Contact xcb@lists.freedesktop.org for corrections and improvements.
XCB
2014-06-10 xcb_randr_get_crtc_gamma(3)