lost and found ( for me ? )

Showing posts with label Fedora 17 64bit. Show all posts
Showing posts with label Fedora 17 64bit. Show all posts

how to install / set up Remote Desktop Free NX on Fedora 17 64bit


[root@f17-64 hattori]# cat /etc/fedora-release
Fedora release 17 (Beefy Miracle)
[root@f17-64 hattori]# uname -ri
3.6.9-2.fc17.x86_64 x86_64

[ install FreeNX server on Fedora 17 ]

you can install FreeNX server via yum
[root@f17-64 hattori]# yum install -y freenx-server

configure FreeNX server
# nxsetup --install --setup-nomachine-key
Setting up /etc/nxserver ...done
Setting up /var/lib/nxserver/db ...done
Setting up /var/log/nx/nxserver.log ...done
Adding user "nx" to group "utmp" ...done
Setting up known_hosts and authorized_keys ...done
Setting up permissions ...done

----> Testing your nxserver configuration ...
Warning: Invalid value "COMMAND_FOOMATIC=/usr/bin/foomatic-ppdfile"
        Users will not be able to use foomatic.
Warning: Invalid value "COMMAND_START_KDE=startkde"
        Users will not be able to request a KDE session.
Warning: Invalid value "COMMAND_START_CDE=cdwm"
        Users will not be able to request a CDE session.
Warning: Invalid value "COMMAND_SMBMOUNT=smbmount". You'll not be able to use SAMBA.
Warning: Invalid value "COMMAND_SMBUMOUNT=smbumount". You'll not be able to use SAMBA.
Warning: Invalid cupsd version of "/usr/sbin/cupsd". Need version 1.2.
        Users will not be able to enable printing. Ignore if you use cups > 1.2

 Warnings occured during config check.
 To enable these features please correct the configuration file.

<---- done

----> Testing your nxserver connection ...
HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
<--- done

Ok, nxserver is ready.

PAM authentication enabled:
 All users will be able to login with their normal passwords.

 PAM authentication will be done through SSH.
 Please ensure that SSHD on localhost accepts password authentication.

 You can change this behaviour in the /etc/nxserver/node.conf file.
Have Fun!



NX server’s configuration
# cat /etc/nxserver/node.conf
ENABLE_PASSDB_AUTHENTICATION="0"
ENABLE_SSH_AUTHENTICATION="1"
ENABLE_CLIPBOARD="both"
NX_LOG_LEVEL=4
NX_LOGFILE=/var/log/nx/nxserver.log
COMMAND_MD5SUM="md5sum"


start freenx server
[root@f17-64 hattori]# systemctl restart freenx-server.service

[root@f17-64 hattori]# systemctl status freenx-server.service
freenx-server.service - FreeNX Server
 Loaded: loaded (/usr/lib/systemd/system/freenx-server.service; enabled)
 Active: active (exited) since Wed, 12 Dec 2012 01:03:54 +0900; 2s ago
Process: 7927 ExecStopPost=/usr/libexec/nx/nxserver --cleanup (code=exited, status=1/FAILURE)
Process: 7853 ExecStop=/usr/libexec/nx/nxserver --stop (code=exited, status=0/SUCCESS)
Process: 8078 ExecStart=/usr/libexec/nx/nxserver --start (code=exited, status=0/SUCCESS)
Process: 8004 ExecStartPre=/usr/libexec/nx/nxserver --cleanup (code=exited, status=1/FAILURE)
Process: 8001 ExecStartPre=/usr/libexec/nx/freenx-server-check-setup (code=exited, status=0/SUCCESS)
 CGroup: name=systemd:/system/freenx-server.service


how to run FreeNX server when booting up Fedora 17.
# systemctl enable freenx-server.service
ln -s '/usr/lib/systemd/system/freenx-server.service' '/etc/systemd/system/multi-user.target.wants/freenx-server.service'


check configuration
# nxsetup --test

----> Testing your nxserver configuration ...
Warning: Invalid value "COMMAND_FOOMATIC=/usr/bin/foomatic-ppdfile"
        Users will not be able to use foomatic.
Warning: Invalid value "COMMAND_START_KDE=startkde"
        Users will not be able to request a KDE session.
Warning: Invalid value "COMMAND_START_CDE=cdwm"
        Users will not be able to request a CDE session.
Warning: Invalid value "COMMAND_SMBMOUNT=smbmount". You'll not be able to use SAMBA.
Warning: Invalid value "COMMAND_SMBUMOUNT=smbumount". You'll not be able to use SAMBA.
Warning: Invalid cupsd version of "/usr/sbin/cupsd". Need version 1.2.
        Users will not be able to enable printing. Ignore if you use cups > 1.2

 Warnings occured during config check.
 To enable these features please correct the configuration file.

<---- done

----> Testing your nxserver connection ...
HELLO NXSERVER - Version 3.2.0-74-SVN OS (GPL, using backend: 3.5.0)
<--- done


[ connect to FreeNX server from NX client ]

install FreeNX client from http://www.nomachine.com/download-client-linux.php

in case of NX client for Fedora , pleaes change permission of ipp file.
# chmod 755 /usr/lib/cups/backend/ipp


start nx client and set up

enter freenx server’ip



specify UNIX , GNOME



here’s detailed configuration



connect




okay

Fedora 17 64bit : can’t update via yum ( the result is always “no packages marked for update” )

I have one desktop machine and one laptop machine and I have installed Fedora 17 64bit on both boxes.
Whenever I try to update packages with “yum update” on the desktop machine , the result is always “No Packages marked for Update”
I , however , can update packages with “yum update” on the laptop machine.


[root@f17-64 ~]# uname -ri
3.5.5-2.fc17.x86_64 x86_64
[root@f17-64 ~]# cat /etc/fedora-release
Fedora release 17 (Beefy Miracle)

[root@f17-64 ~]# yum update -y
Loaded plugins: langpacks, presto, refresh-packagekit
No Packages marked for Update

After issuing “yum clean all” , I can update packages.
[root@f17-64 ~]# yum clean all
Loaded plugins: langpacks, presto, refresh-packagekit
Cleaning repos: fedora google-chrome updates
Cleaning up Everything

[root@f17-64 ~]# yum update -y
<snip>
 vlgothic-p-fonts.noarch 0:20120928-1.fc17                                     
 wodim.x86_64 0:1.1.11-14.fc17                                                 
 xulrunner.x86_64 0:16.0.1-1.fc17                                              
 ykpers.x86_64 0:1.8.0-1.fc17                                                  
 zeitgeist.x86_64 0:0.9.5-1.fc17                                               
 zeitgeist-datahub.x86_64 0:0.9.5-1.fc17                                       

Complete!
[root@f17-64 ~]#

Seen from /var/log/yum.log , I can not update packages after Oct 12th.
[root@f17-64 ~]# egrep "Oct" /var/log/yum.log | awk '{print $1,$2}' | uniq | tail -2
Oct 12
Oct 18

It seems that there is any problem with yum-related data such as metadata , headers etc...