/etc/sysconfig/vncservers

, with systemd the process is quite different.

For our example I will setup vncserver to have display :3 running at a resolution of 1600×900. If you want a different number simply replace it with the number of choice.

sudo yum install tigervnc-server
sudo cp /lib/systemd/vncserver@.service /lib/systemd/vncserver@:3.service

Next you will need to edit the service file with the username you want vncserver to run under and any vnc options you want.

sudo vi /lib/systemd/system/vncserver@:3.service

The file will look something like this when you open it:

# comment redacted
[Unit]
Description=Remote desktop service (VNC)
After=syslog.target network.target

[Service]
Type=forking
ExecStart=/sbin/runuser -l  -c "/usr/bin/vncserver %i"
ExecStop=/sbin/runuser -l  -c "/usr/bin/vncserver -kill %i"

[Install]
WantedBy=multi-user.target

Change <USER> with the username you want to run vncserver under. For our case let’s use kdr.

Next add the vnc options you want after the %i. Since we want it to run at a resolution of 1600×900 we will add -geometry 1600x900.

ExecStart=/sbin/runuser -l kdr -c "/usr/bin/vncserver %i -geometry 1600x900"
ExecStop=/sbin/runuser -l kdr -c "/usr/bin/vncserver -kill %i"

Save the file and enable the service:

sudo systemctl enable vncserver@:3.service

Now configure the password you want to use to connect to vnc. Run this
as the user you setup in the *.service file above i.e. kdr.

vncpasswd
Password:
Verify:

We now have vncserver setup with a username and a password, and enabled in the system. Two more things to check. First thing is verify you have the port open. The vnc display number will map to 5900 series of ports. Since we chose 3 vncserver will listen on port 5903. If you choose 1, it’ll be 5901, etc.

Let’s see if iptables is configured to listen to this port:

sudo iptables --list | grep 5903

Nope, let’s update iptables:

sudo vi /etc/sysconfig/iptables

Add this to the file:

-A INPUT -p tcp -m state --state NEW -m tcp --dport 5903 -j ACCEPT

Save the file, then restart iptables and verify that the port is active.

sudo systemctl restart iptables.service

sudo iptables --list | grep 5903
ACCEPT     tcp  --  anywhere             anywhere             state NEW tcp dpt:5903

Ok FINALLY we can start up vncserver.

systemctl start vncserver@:3.service

Test it out by connecting with vncviewer host.example.com:3.
Enter the password you used for vncpasswd.

ENJOY!

I sincerely doubt that American economy is affected by $58 billion a year due to piracy. That is precisely the problem I have with all piracy bills, their ludicrous claims of lost revenue. These numbers are calculated as if all the pirated material was going to be acquired legally by all. Most of the people that pirate would never have purchased the material to begin with especially at the prices the owners use to calculate the inflated numbers.

The real problem is that the piracy sites are out of American jurisdiction, if you want to prevent piracy then you need to make the content more easily accessible. It used to be a time when people were pirating music left and right. But once the music industry allowed the sale of music online at a price consumers are willing to pay, it has become EASIER to acquire the music legally than through other means. For less than a $1 people can get their music fix right then and there legally.

If the movie industry made their movies easier to acquire at a cheaper price, I bet piracy would go down tremendously. But they are greedy machines trying to squeeze every penny out of something including paying Congress to do their bidding. Just look at what the studios do to cable companies and Netflix. The movie industry should be focused on getting their content out to the masses, because if people can get the latest movies from Netflix, cable or for any of their devices cheaply, they won’t have to pirate them. This legislation is, in my opinion, going after the wrong thing.

It is a shame that you support this horrible bill, come re-election time, I’ll be voting for the OTHER candidate.

Sincerely,
jesus rodriguez

January 19, 2012

Dear Friend,

Thank you for contacting me to express your concerns regarding the Preventing Real Online Threats to Economic Creativity and Theft of Intellectual Property Act of 2011, more commonly referred to as the PROTECT IP Act of 2011. I appreciate hearing your thoughts on this important issue.

On May 12, 2011, the Preventing Real Online Threats to Economic Creativity and Theft of Intellectual Property Act of 2011 (S. 968) was introduced in the Senate and referred to the Committee on the Judiciary. This bill would allow the Attorney General, or an intellectual property rights owner who has been harmed by an Internet site dedicated to infringing activities (ISDIA), also known as a rogue website, to take action against that site. A site would be designated as an ISDIA if their sole purpose is to facilitate copyright infringement, or promote or sale of counterfeited American works.

A recent study suggests that copyright piracy alone costs the American economy as much as $58 billion a year and countless jobs. I strongly support the goal of reducing the theft of intellectual property that is so important to North Carolina’s economy, including our budding film industry, which is why I and 40 of my bipartisan cosponsors originally cosponsored this legislation last July.

As with all proposed legislation, legitimate concerns have been raised about some of the specific provisions in this bill. I believe that supporters and opponents of the bill, all of whom agree, after all, on the need to combat the theft of American intellectual property, should work together to address those concerns. As you may know, the Senate is scheduled to begin consideration of this legislation later this month, and I intend to approach the debate and amendment process with an open mind. Through a full and robust debate, I believe we can improve the legislation, ultimately reaching an agreement that will protect intellectual property without limiting innovation and creativity or creating unintended consequences.

Again, thank you for contacting my office. It is truly an honor to represent North Carolina in the United States Senate, and I hope you will not hesitate to contact me in the future should you have any further questions or concerns.

Sincerely,

Kay R. Hagan

It’s that time again, another release of Candlepin and associated projects available for your enjoyment. With this release we have subscription-manager in Fedora as well as a debut build of Thumbslug.

For more information on Candlepin, please visit: http://candlepinproject.org/

Features & Enhancements

subscription-manager

• added support for host registration and guest association when host can not register itself
• virt-who work to handle ESX guests
• subscription-manager available in fedora

candlepin

• build modified to use the tito hotness instead of bunch of disjoint bash scripts
• disable manifest rules import
• added support for host registration and guest association when host can not register itself

thumbslug

• added appropriate init scripts to run as a service
• uses Candlepin CRL
• thumbslug talks to akamai
• created puppet module for katello

Bugs fixed

subscription-manager

candlepin

thumbslug

Download & Setup

Make sure you read over the Candlepin Setup Guide, which is located at https://fedorahosted.org/candlepin/wiki/Setup.

As well as the Headpin Install Guide which can be found at https://fedorahosted.org/candlepin/wiki/headpin/Install

Just give me the bits already! You can get the various bits at the urls below.

Candlepin:
http://repos.fedorapeople.org/repos/candlepin/candlepin/

Thumbslug:
http://repos.fedorapeople.org/repos/candlepin/thumbslug/

Headpin:
http://repos.fedorapeople.org/repos/katello

Subscription Manager:
http://repos.fedorapeople.org/repos/candlepin/subscription-manager/

December 21, 1996 – October 31, 2011

http://repos.fedorapeople.org/repos/candlepin/candlepin/

Make sure you read over the Setup Guide, which is located at
https://fedorahosted.org/candlepin/wiki/Setup

For more information on Candlepin, please visit our project page.

Features & Enhancements

client

• A number of GUI changes
  • Center the machine type column header
  • Move quantity column to the end
  • Center the Arch column header
  • Center tree view table properties
  • Add ‘* Click to Adjust Quantity’ label to places allowing editable subscription quantity
  • New icons for red/green
  • Add virt_only attribute to subscription detail pane
  • Display subscription assistant’s subscriptions as a tree
  • Double click or button press (enter, return, space) on row will expand/collapse row
  • Update to All Available Subscriptions tab to put stacked subscriptions under parent node
  • Moved multi-entitlement column (*) next to the quantity column
  • Made the contract selector a little wider so all columns were visible (no manual resize)
• Initial work done for the healing feature
  • Changes to rhsmcertd to support healing frequency (part I)
  • Add autoheal option to certmgr.py
  • Only autoheal when required
  • Use server-side consumer autoheal flag
• Misc items
  • Update the strings and the remote server location
  • Make “make stylish” run all the checks, make whitespace “pop”
  • Update translations
  • managerlib was expecting a single ent_cert, but we return a list
  • Add a “refresh” method to cert_sorter
  • Add a require_connection callback to commands

server

• upgraded to RESTEasy 2.2.1GA
• export virt entitlements to non-candlepin consumers
• refactored pinsetter to work in clustering mode
• add new api to query jobs by owner, principal, consumer uuid

Bugs fixed