date:20140723

On 07/23/14 13:47, Robert Moskowitz wrote:
 OK.  I believe I figured out what is wrongish.

 I normally run gnome, so in my ~/.vnc/xstartup I have:

 exec gnome-session 

 as the last line.  But this fedora 20 arm system is running Xfce! So after a 
 quick google search, I changed that to:

 exec xfce4-session 

 But still I get vnc having a blank screen.  That no desktop is running in 
 vnc.  /var/log/messages says:

As I've mentioned in an earlier post  I've got no problems to run different 
desktops.

FWIW, I do edit the default $USER/.vnc/xstartup to change the lines with

exec /etc/X11/xinit/xinitrc

to

exec /home/user/.xinitrc

and I create a /home/user/.xinitrc containing

exec ck-launch-session dbus-launch --exit-with-session startkde

OR

exec ck-launch-session dbus-launch --exit-with-session startxfce4

You may want to consider trying that as I recall there being a problem if you 
don't involve dbus.

FWIW, this is on 2 3.15.6-200.fc20.x86_64 systems.


-- 
If you can't laugh at yourself, others will gladly oblige.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: vnc not into gnome but Xfce but still not working



$ grep -v ^# $HOME/.vnc/xstartup
startxfce4

$ grep -v ^# /etc/systemd/system/vncserver@\:1.service
[Unit]
Description=Remote desktop service (VNC)
After=syslog.target network.target

[Service]
Type=simple
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i  /dev/null 21 || :'
ExecStart=/sbin/runuser -l USER -c /usr/bin/vncserver %i -fg
ExecStop=/bin/sh -c '/usr/bin/vncserver -kill %i  /dev/null 21 || :'
ExecStopPost=/sbin/runuser -l root -c /usr/bin/Loginctl-Clean

[Install]
WantedBy=multi-user.target


poma


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: color display with man pages

2014-07-23 Thread Corinna Vinschen

On Jul 22 22:40, Mark LaPierre wrote:
 On 07/22/14 04:55, Corinna Vinschen wrote:
  On Jul 22 13:37, Amila Perera wrote:
  Thank you for your feedback.
 
 
  On Tue, Jul 22, 2014 at 12:40 PM, Suvayu Ali fatkasuvayu+li...@gmail.com
  wrote:
 
  I tried with bash, it seems to work ... somewhat.  I see a yellow status
  at the bottom, but otherwise I see a regular man page.  When I `type
  man' after defining your function, I get a few colours among the variable
  definitions (blue, red, and underlined).
 
 
  Well, I only get the yellow status line color and some variables getting
  bold.
  I have never tried this with bash, though.
  
  Try this additionally to setting the LESS_TERMCAP_xx vars:
  
export GROFF_NO_SGR=yes
  
 
 Hey Corinna,
 
 Could you share some more details on how to use the LESS_TERMCAP_xx
 vars and export GROFF_NO_SGR=yes commands?  I'm assuming that you put
 them in your .bashrc file, no?

No, I'm tcsh user, sorry :}

I was just curious and experimented with it.  For bash you can do
something like this:
http://www.cyberciti.biz/faq/linux-unix-colored-man-pages-with-less-command/
and just add the GROFF_NO_SGR setting to it, I guess.


Corinna
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: vnc not into gnome but Xfce but still not working

On 07/23/2014 02:08 AM, Michael D. Setzer II wrote:

On 23 Jul 2014 at 1:47, Robert Moskowitz wrote:

Date sent:  Wed, 23 Jul 2014 01:47:37 -0400
From:   Robert Moskowitz r...@htt-consult.com
To: Community support for Fedora users
users@lists.fedoraproject.org
Subject:vnc not into gnome but Xfce but still not working
Send reply to:  Community support for Fedora users
users@lists.fedoraproject.org
 OK.  I believe I figured out what is wrongish.

I normally run gnome, so in my ~/.vnc/xstartup I have:

exec gnome-session 

as the last line.  But this fedora 20 arm system is running Xfce! So
after a quick google search, I changed that to:

exec xfce4-session 

But still I get vnc having a blank screen.  That no desktop is running
in vnc.  /var/log/messages says:

What exactly do you have in the /home/user/.vnc/xstartup file

Mine is as follows
#!/bin/sh

# Uncomment the following two lines for normal desktop:
unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
exec  /bin/sh /etc/xdg/xfce4/xinitrc #   X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ]  exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ]  xrdb $HOME/.Xresources
xsetroot -solid grey
#vncconfig -iconic 
xterm -geometry 80x24+10+10 -ls -title $VNCDESKTOP Desktop 
startxfce4 
#twm 

Note: The change in the xinitrc to use the xfce4 and the startxfce4 
Mine is quite different. This is created by tigervnc-server with only 
the last line changed by me:

.vnc]$ cat xstartup
#!/bin/sh

unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
OS=`uname -s`
if [ $OS = 'Linux' ]; then
case $WINDOWMANAGER in
*gnome*)
if [ -e /etc/SuSE-release ]; then
PATH=$PATH:/opt/gnome/bin
export PATH
fi
;;
esac
fi
if [ -x /etc/X11/xinit/xinitrc ]; then
exec /etc/X11/xinit/xinitrc
fi
if [ -f /etc/X11/xinit/xinitrc ]; then
exec sh /etc/X11/xinit/xinitrc
fi
[ -r $HOME/.Xresources ]  xrdb $HOME/.Xresources
xsetroot -solid grey
xterm -geometry 80x24+10+10 -ls -title $VNCDESKTOP Desktop 
exec xfce4-session 

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: vnc not into gnome but Xfce but still not working

On 07/23/2014 02:08 AM, Michael D. Setzer II wrote:

On 23 Jul 2014 at 1:47, Robert Moskowitz wrote:

Date sent:  Wed, 23 Jul 2014 01:47:37 -0400
From:   Robert Moskowitz r...@htt-consult.com
To: Community support for Fedora users
users@lists.fedoraproject.org
Subject:vnc not into gnome but Xfce but still not working
Send reply to:  Community support for Fedora users
users@lists.fedoraproject.org
 OK.  I believe I figured out what is wrongish.

I normally run gnome, so in my ~/.vnc/xstartup I have:

exec gnome-session 

as the last line.  But this fedora 20 arm system is running Xfce! So
after a quick google search, I changed that to:

exec xfce4-session 

But still I get vnc having a blank screen.  That no desktop is running
in vnc.  /var/log/messages says:

What exactly do you have in the /home/user/.vnc/xstartup file

Mine is as follows
#!/bin/sh

# Uncomment the following two lines for normal desktop:
unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
exec  /bin/sh /etc/xdg/xfce4/xinitrc #   X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ]  exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ]  xrdb $HOME/.Xresources
xsetroot -solid grey
#vncconfig -iconic 
xterm -geometry 80x24+10+10 -ls -title $VNCDESKTOP Desktop 
startxfce4 
#twm 

Note: The change in the xinitrc to use the xfce4 and the startxfce4 

So I changed mine to:

if [ -x /etc/X11/xinit/xinitrc ]; then
#  exec /etc/X11/xinit/xinitrc
  exec /etc/xdg/xfce4/xinitrc
fi
if [ -f /etc/X11/xinit/xinitrc ]; then
#  exec sh /etc/X11/xinit/xinitrc
  exec sh /etc/xdg/xfce4/xinitrc
fi

restarted the vncserver and connected.  Now I get a blank black screeen 
rather than a blank blue screen...

Do I need xfce installed on my notebook?  I only have gnome on it.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

kindof fixed - Re: vnc not into gnome but Xfce but still not working

On 07/23/2014 02:08 AM, Michael D. Setzer II wrote:

On 23 Jul 2014 at 1:47, Robert Moskowitz wrote:

Date sent:  Wed, 23 Jul 2014 01:47:37 -0400
From:   Robert Moskowitz r...@htt-consult.com
To: Community support for Fedora users
users@lists.fedoraproject.org
Subject:vnc not into gnome but Xfce but still not working
Send reply to:  Community support for Fedora users
users@lists.fedoraproject.org
 OK.  I believe I figured out what is wrongish.

I normally run gnome, so in my ~/.vnc/xstartup I have:

exec gnome-session 

as the last line.  But this fedora 20 arm system is running Xfce! So
after a quick google search, I changed that to:

exec xfce4-session 

But still I get vnc having a blank screen.  That no desktop is running
in vnc.  /var/log/messages says:

What exactly do you have in the /home/user/.vnc/xstartup file

Mine is as follows
#!/bin/sh

# Uncomment the following two lines for normal desktop:
unset SESSION_MANAGER
unset DBUS_SESSION_BUS_ADDRESS
exec  /bin/sh /etc/xdg/xfce4/xinitrc #   X11/xinit/xinitrc

[ -x /etc/vnc/xstartup ]  exec /etc/vnc/xstartup
[ -r $HOME/.Xresources ]  xrdb $HOME/.Xresources
xsetroot -solid grey
#vncconfig -iconic 
xterm -geometry 80x24+10+10 -ls -title $VNCDESKTOP Desktop 
startxfce4 
#twm 

Note: The change in the xinitrc to use the xfce4 and the startxfce4 

So I just cp your xstartup to my system and it works now. thanks.

So what is wrong with the default script? I am assuming I need to file a 
bug report on it.

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: kindof fixed - Re: vnc not into gnome but Xfce but still not working

On 07/23/14 19:34, Robert Moskowitz wrote:
 So I just cp your xstartup to my system and it works now. thanks.

 So what is wrong with the default script? I am assuming I need to file a bug 
 report on it. 

Nothing is wrong with the default script.

if [ -x /etc/X11/xinit/xinitrc ]; then
exec /etc/X11/xinit/xinitrc
fi

[egreshko@f20f ~]$ file /etc/X11/xinit/xinitrc
/etc/X11/xinit/xinitrc: POSIX shell script, ASCII text executable



-- 
If you can't laugh at yourself, others will gladly oblige.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: CPU/Memory

2014-07-23 Thread Daniel J Walsh

I would bet you have a mislabeled machine that is generating hundreds of
AVC's.

ausearch -m avc -ts today

If the system is mislabeled, the easiest thing to do would be

touch /.autorelabel; reboot

On 07/22/2014 07:02 PM, Rick Stevens wrote:
 On 07/22/2014 01:23 PM, Patrick Dupre issued this missive:
 Hello,

 I have 2 machines running fedora 20, one from 2007 with a dual processor
 and 3 Go, and a recent one (2013) with a quad processor an 8 Go.
 But it is a lot more convenient to use the old machine!!!
 The recent one is always busy, 4 processors running
 53.1 55.9 /usr/bin/python -Es /usr/sbin/setroublesootd -f
   and the memory becomes full quickly requiring swapping!!
 8 Go for the OS and firefox! Something is wrong.

 Should I kill setroublesootd?

 The first thing is to see why you're getting AVC denials from SELinux
 in the first place. setroubleshootd should only fire if it's getting
 denials. Try running sealert -b and see if you're getting denials and
 what you can do about them.

 --
 - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
 - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
 --
 -   To err is human, to moo bovine.  -
 --

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: systemd config files???

2014-07-23 Thread Rahul Sundaram

Hi


On Tue, Jul 22, 2014 at 4:39 PM, Anders Wegge Keller  wrote:


  The specific wording: requires users to modify files below /usr.


I am not sure picking up some words without the context is useful.  If you
read the full email, it was obviously talking about configuration files.

Rahul
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: kindof fixed - Re: vnc not into gnome but Xfce but still not working



On 07/23/2014 07:40 AM, Ed Greshko wrote:

On 07/23/14 19:34, Robert Moskowitz wrote:

So I just cp your xstartup to my system and it works now. thanks.

So what is wrong with the default script? I am assuming I need to file a bug 
report on it.

Nothing is wrong with the default script.

if [ -x /etc/X11/xinit/xinitrc ]; then
exec /etc/X11/xinit/xinitrc
fi

[egreshko@f20f ~]$ file /etc/X11/xinit/xinitrc
/etc/X11/xinit/xinitrc: POSIX shell script, ASCII text executable
Fine.  then why switching to Michael Setzer's xstartup result in vnc 
working?


The default did not work.  His does.  why?


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

NetworkManager not running? F20 arm xfce

In my vnc connection to my server, the xfce system bar's network manager 
tells me:


Networking disabled (when I place the mouse over the network icon)
Network Manager not running (when I click on the network icon, and this 
text is grey)


Yet in my ssh session to the server:

# systemctl status NetworkManager.service
NetworkManager.service - Network Manager
Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled)
Active: active (running) since Fri 2010-01-01 00:00:23 EST; 4 years 6 
months ago

Main PID: 319 (NetworkManager)
CGroup: /system.slice/NetworkManager.service
└─319 /usr/sbin/NetworkManager --no-daemon

Jan 01 00:01:15 cb2.htt-consult.com NetworkManager[319]: DHCPDISCOVER on 
eth0 to 255.255.255.255 port 6...f2)
Jan 01 00:01:23 cb2.htt-consult.com dhclient[853]: DHCPDISCOVER on eth0 
to 255.255.255.255 port 67 inte...f2)
Jan 01 00:01:23 cb2.htt-consult.com NetworkManager[319]: DHCPDISCOVER on 
eth0 to 255.255.255.255 port 6...f2)
Jan 01 00:01:24 cb2.htt-consult.com NetworkManager[319]: warn (eth0): 
DHCPv4 request timed out.
Jan 01 00:01:24 cb2.htt-consult.com dhclient[853]: Received signal 15, 
initiating shutdown.
Jan 01 00:01:24 cb2.htt-consult.com NetworkManager[319]: Received signal 
15, initiating shutdown.
Jan 01 00:01:24 cb2.htt-consult.com NetworkManager[319]: info (eth0): 
canceled DHCP transaction, DHCP...853
Jan 01 00:01:24 cb2.htt-consult.com NetworkManager[319]: info 
Activation (eth0) Stage 4 of 5 (IPv4 Co..
Jan 01 00:01:24 cb2.htt-consult.com NetworkManager[319]: info 
Activation (eth0) Stage 4 of 5 (IPv4 Co..
Jan 01 00:01:24 cb2.htt-consult.com NetworkManager[319]: info 
Activation (eth0) Stage 4 of 5 (IPv4 Co...te.

Hint: Some lines were ellipsized, use -l to show in full.

and

# ifconfig
eth0: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500
inet6 fe80::c4:3ff:fe82:c153 prefixlen 64 scopeid 0x20link
ether 02:c4:03:82:c1:53 txqueuelen 1000 (Ethernet)
RX packets 3339 bytes 326670 (319.0 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3469 bytes 1641253 (1.5 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 87 base 0x6000

eth0:avahi: flags=4163UP,BROADCAST,RUNNING,MULTICAST mtu 1500
inet 169.254.7.244 netmask 255.255.0.0 broadcast 169.254.255.255
ether 02:c4:03:82:c1:53 txqueuelen 1000 (Ethernet)
device interrupt 87 base 0x6000

lo: flags=73UP,LOOPBACK,RUNNING mtu 16436
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10host
loop txqueuelen 0 (Local Loopback)
RX packets 790 bytes 70412 (68.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 790 bytes 70412 (68.7 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

wlan0: flags=4099UP,BROADCAST,MULTICAST mtu 1500
ether 00:14:d1:4c:0f:79 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0


And note wlan0 which is not showing up in network manager...

Note that the only network connection is direct cable to my notebook. 
Separate message on wlan questions


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: kindof fixed - Re: vnc not into gnome but Xfce but still not working

On 07/23/14 21:49, Robert Moskowitz wrote:

 On 07/23/2014 07:40 AM, Ed Greshko wrote:
 On 07/23/14 19:34, Robert Moskowitz wrote:
 So I just cp your xstartup to my system and it works now. thanks.

 So what is wrong with the default script? I am assuming I need to file a 
 bug report on it.
 Nothing is wrong with the default script.

 if [ -x /etc/X11/xinit/xinitrc ]; then
 exec /etc/X11/xinit/xinitrc
 fi

 [egreshko@f20f ~]$ file /etc/X11/xinit/xinitrc
 /etc/X11/xinit/xinitrc: POSIX shell script, ASCII text executable
 Fine.  then why switching to Michael Setzer's xstartup result in vnc working?

 The default did not work.  His does.  why?

For the same reason my method would also have worked.

The /etc/X11/xinit/xinitrc which exists is exec'd since it does exist and is 
executable.  Subsequently /etc/X11/xinit/Xclients also exists and will be 
exec'd and that is pretty much useful only for GNOME or KDE.  So  
/etc/X11/xinit/xinitrc needs to be modified to get xfce to run.

Michael's is modified to suit the need.

I also modified it, but choose to do it in a different fashion.

Both methods work fine.

You could have also modified /etc/X11/xinit/Xclients to include support for 
xfce.  But, that is probably a bad idea since it very well may get changed on 
updates.

-- 
If you can't laugh at yourself, others will gladly oblige.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

wlan0 not working - F20 arm

I have this old Trendnet usb 802.11bg adapter plugged into my server.  
It is not showing in Network manager (see prior message) so I am trying 
via command lines:


# ifconfig wlan0 up
# iwlist wlan0 scan
wlan0 No scan results

Don't tell me that, my notebook is connected wirelessly and I can see 
b/g support in the APs here.


and

# ifconfig wlan0
wlan0: flags=4099UP,BROADCAST,MULTICAST  mtu 1500
ether 00:14:d1:4c:0f:79  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: kindof fixed - Re: vnc not into gnome but Xfce but still not working



On 07/23/2014 10:20 AM, Ed Greshko wrote:

On 07/23/14 21:49, Robert Moskowitz wrote:

On 07/23/2014 07:40 AM, Ed Greshko wrote:

On 07/23/14 19:34, Robert Moskowitz wrote:

So I just cp your xstartup to my system and it works now. thanks.

So what is wrong with the default script? I am assuming I need to file a bug 
report on it.

Nothing is wrong with the default script.

if [ -x /etc/X11/xinit/xinitrc ]; then
exec /etc/X11/xinit/xinitrc
fi

[egreshko@f20f ~]$ file /etc/X11/xinit/xinitrc
/etc/X11/xinit/xinitrc: POSIX shell script, ASCII text executable

Fine.  then why switching to Michael Setzer's xstartup result in vnc working?

The default did not work.  His does.  why?

For the same reason my method would also have worked.

The /etc/X11/xinit/xinitrc which exists is exec'd since it does exist and is 
executable.  Subsequently /etc/X11/xinit/Xclients also exists and will be 
exec'd and that is pretty much useful only for GNOME or KDE.  So  
/etc/X11/xinit/xinitrc needs to be modified to get xfce to run.

Michael's is modified to suit the need.

I also modified it, but choose to do it in a different fashion.

Both methods work fine.

You could have also modified /etc/X11/xinit/Xclients to include support for 
xfce.  But, that is probably a bad idea since it very well may get changed on 
updates.


And this is not a bug with the default xstartup script?


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: kindof fixed - Re: vnc not into gnome but Xfce but still not working

2014-07-23 Thread Michael D. Setzer II

On 23 Jul 2014 at 9:49, Robert Moskowitz wrote:

Date sent:  Wed, 23 Jul 2014 09:49:33 -0400
From:   Robert Moskowitz r...@htt-consult.com
To: Community support for Fedora users 
users@lists.fedoraproject.org
Subject:Re: kindof fixed - Re: vnc not into gnome but Xfce but 
still 
not
working
Send reply to:  Community support for Fedora users 
users@lists.fedoraproject.org

 On 07/23/2014 07:40 AM, Ed Greshko wrote:
  On 07/23/14 19:34, Robert Moskowitz wrote:
  So I just cp your xstartup to my system and it works now. thanks.

  So what is wrong with the default script? I am assuming I need to
  file a bug report on it.
  Nothing is wrong with the default script.

  if [ -x /etc/X11/xinit/xinitrc ]; then
  exec /etc/X11/xinit/xinitrc
  fi

  [egreshko@f20f ~]$ file /etc/X11/xinit/xinitrc
  /etc/X11/xinit/xinitrc: POSIX shell script, ASCII text executable
 Fine.  then why switching to Michael Setzer's xstartup result in vnc
 working?

 The default did not work.  His does.  why?

The default I believe is setup for gnome desktop, whereas mine has the two 
modifications for using xfce. Don't know what it would take to make a 
modified version that would work with either, or if nothing else just have the 
lines in the script and have instructions to comment out the ones that don't 
apply to the setup. 

Haven't setup the vnc with KDE, so don't know if it works that way as well 
with the default or if it needs a third option. 

 -- 
 users mailing list
 users@lists.fedoraproject.org
 To unsubscribe or change subscription options:
 https://admin.fedoraproject.org/mailman/listinfo/users
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
 Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have
 a question? Ask away: http://ask.fedoraproject.org

+--+
  Michael D. Setzer II -  Computer Science Instructor  
  Guam Community College  Computer Center  
  mailto:mi...@kuentos.guam.net
  mailto:msetze...@gmail.com
  http://www.guam.net/home/mikes
  Guam - Where America's Day Begins
  G4L Disk Imaging Project maintainer 
  http://sourceforge.net/projects/g4l/
+--+

http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)

BOINC@HOME CREDITS
ROSETTA 17941584.881866   |   SETI29593668.378551
ABC 16613838.513356   |   EINSTEIN28547237.391636

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: kindof fixed - Re: vnc not into gnome but Xfce but still not working

2014-07-23 Thread Michael D. Setzer II

On 23 Jul 2014 at 19:40, Ed Greshko wrote:

From:   Ed Greshko ed.gres...@greshko.com
Date sent:  Wed, 23 Jul 2014 19:40:11 +0800
To: Community support for Fedora users 
users@lists.fedoraproject.org
Subject:Re: kindof fixed - Re: vnc not into gnome but Xfce but 
still 
not
working
Send reply to:  Community support for Fedora users 
users@lists.fedoraproject.org

mailto:users-requ...@lists.fedoraproject.org?subject=unsubscribe

mailto:users-requ...@lists.fedoraproject.org?subject=subscribe

 On 07/23/14 19:34, Robert Moskowitz wrote:
  So I just cp your xstartup to my system and it works now. thanks.
 
  So what is wrong with the default script? I am assuming I need to
  file a bug report on it. 
 
 Nothing is wrong with the default script.
 
 if [ -x /etc/X11/xinit/xinitrc ]; then
 exec /etc/X11/xinit/xinitrc
 fi
 

Problem is that is you are running xfce for the vnc you need
exec  /bin/sh /etc/xdg/xfce4/xinitrc #   X11/xinit/xinitrc
and 
startxfce4  #twm 

The if just says if the file exist and is executible run it, doesn't check if 
that is 
the correct xinitrc for your configuration?

 [egreshko@f20f ~]$ file /etc/X11/xinit/xinitrc
 /etc/X11/xinit/xinitrc: POSIX shell script, ASCII text executable
 
 
 
 -- 
 If you can't laugh at yourself, others will gladly oblige.
 -- 
 users mailing list
 users@lists.fedoraproject.org
 To unsubscribe or change subscription options:
 https://admin.fedoraproject.org/mailman/listinfo/users
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
 Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have
 a question? Ask away: http://ask.fedoraproject.org


+--+
  Michael D. Setzer II -  Computer Science Instructor  
  Guam Community College  Computer Center  
  mailto:mi...@kuentos.guam.net
  mailto:msetze...@gmail.com
  http://www.guam.net/home/mikes
  Guam - Where America's Day Begins
  G4L Disk Imaging Project maintainer 
  http://sourceforge.net/projects/g4l/
+--+

http://setiathome.berkeley.edu (Original)
Number of Seti Units Returned:  19,471
Processing time:  32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)

BOINC@HOME CREDITS
ROSETTA 17941584.881866   |   SETI29593668.378551
ABC 16613838.513356   |   EINSTEIN28547237.391636

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: kindof fixed - Re: vnc not into gnome but Xfce but still not working

On 07/23/14 22:25, Robert Moskowitz wrote:
 And this is not a bug with the default xstartup script? 

No.  I'd classify it as a deficiency.   It works as it is designed.  It just 
doesn't have what you need for xfce.

-- 
If you can't laugh at yourself, others will gladly oblige.
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: wlan0 not working - F20 arm

2014-07-23 Thread Tom Horsley

On Wed, 23 Jul 2014 10:22:39 -0400
Robert Moskowitz wrote:

 # ifconfig wlan0

Are you sure that isn't just a leftover ifcfg file named wlan0?

On my f20 box, when I plug in a wireless dongle I get
some really helpful name like wlp0s29u1u2 (and to be
even more helpful, the name changes if I move the
exact same dongle to a different USB port - nothing
like having predictable names :-).
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: wlan0 not working - F20 arm



On 07/23/2014 10:40 AM, Tom Horsley wrote:

On Wed, 23 Jul 2014 10:22:39 -0400
Robert Moskowitz wrote:


# ifconfig wlan0

Are you sure that isn't just a leftover ifcfg file named wlan0?


Other than when the dongle is not plugged in, there is no entry for wlan 
in ifconfig.




On my f20 box, when I plug in a wireless dongle I get
some really helpful name like wlp0s29u1u2 (and to be
even more helpful, the name changes if I move the
exact same dongle to a different USB port - nothing
like having predictable names :-).


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: kindof fixed - Re: vnc not into gnome but Xfce but still not working


On 23.07.2014 16:32, Ed Greshko wrote:

On 07/23/14 22:25, Robert Moskowitz wrote:

And this is not a bug with the default xstartup script?


No.  I'd classify it as a deficiency.   It works as it is designed.  It just 
doesn't have what you need for xfce.



The reason why 'startxfce4' exists.
Why should it be simple when it can be complicated, ha! :)


experts fan club


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: vnc not into gnome but Xfce but still not working


On 23.07.2014 10:40, poma wrote:


$ grep -v ^# $HOME/.vnc/xstartup
startxfce4

$ grep -v ^# /etc/systemd/system/vncserver@\:1.service
[Unit]
Description=Remote desktop service (VNC)
After=syslog.target network.target

[Service]
Type=simple
ExecStartPre=/bin/sh -c '/usr/bin/vncserver -kill %i  /dev/null 21 || :'
ExecStart=/sbin/runuser -l USER -c /usr/bin/vncserver %i -fg
ExecStop=/bin/sh -c '/usr/bin/vncserver -kill %i  /dev/null 21 || :'
ExecStopPost=/sbin/runuser -l root -c /usr/bin/Loginctl-Clean

[Install]
WantedBy=multi-user.target



However if someone is eager enough to play with the 'Xspice'
http://www.spice-space.org/page/Features/Xspice

Server:
$ Xspice --port PORT --exit-on-disconnect --xsession startxfce4 
--disable-ticketing :2 

Client:
$ spicy -h Spice server address/hostname -p PORT


$ Xspice -h
$ spicy -?

$ repoquery -i xorg-x11-server-Xspice
$ repoquery -i spice-gtk-tools


remote desktop fan club


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: CPU/Memory

2014-07-23 Thread Patrick Dupre

Hello,

Thank.

I did a relabelling, and it seems a lot better.

===
 Patrick DUPRÉ | | email: pdu...@gmx.com
 Laboratoire de Physico-Chimie de l'Atmosphère | |
 Université du Littoral-Côte d'Opale   | |
 Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
 189A, avenue Maurice Schumann | | 59140 Dunkerque, France
===


 Sent: Wednesday, July 23, 2014 at 2:06 PM
 From: Daniel J Walsh dwa...@redhat.com
 To: Community support for Fedora users users@lists.fedoraproject.org
 Subject: Re: CPU/Memory

 I would bet you have a mislabeled machine that is generating hundreds of
 AVC's.
 
 ausearch -m avc -ts today
 
 If the system is mislabeled, the easiest thing to do would be
 
 touch /.autorelabel; reboot
 
 On 07/22/2014 07:02 PM, Rick Stevens wrote:
  On 07/22/2014 01:23 PM, Patrick Dupre issued this missive:
  Hello,
 
  I have 2 machines running fedora 20, one from 2007 with a dual processor
  and 3 Go, and a recent one (2013) with a quad processor an 8 Go.
  But it is a lot more convenient to use the old machine!!!
  The recent one is always busy, 4 processors running
  53.1 55.9 /usr/bin/python -Es /usr/sbin/setroublesootd -f
and the memory becomes full quickly requiring swapping!!
  8 Go for the OS and firefox! Something is wrong.
 
  Should I kill setroublesootd?
 
  The first thing is to see why you're getting AVC denials from SELinux
  in the first place. setroubleshootd should only fire if it's getting
  denials. Try running sealert -b and see if you're getting denials and
  what you can do about them.
 
  --
  - Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
  - AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
  --
  -   To err is human, to moo bovine.  -
  --
 
 -- 
 users mailing list
 users@lists.fedoraproject.org
 To unsubscribe or change subscription options:
 https://admin.fedoraproject.org/mailman/listinfo/users
 Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
 Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
 Have a question? Ask away: http://ask.fedoraproject.org

-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: partitioning

2014-07-23 Thread Chris Murphy

On Jul 16, 2014, at 11:21 AM, dustin kempter dust...@consistentstate.com
wrote:

Hi all, I am an SA in training and ive been reading a lot about the
importance of separating out your workspace/server into separate partitions
such as /, /data, /home, /ftp, /usr, /boot vs dividing it into just a /,
/boot, /data. and it seems that doing it how Ive been reading about with more
partitions is more secure but what about when one partition becomes full?

I'm not sure how it's made more secure. Features of the technology backing a
particular mount point is what would do that. For example raid1 /home, or
raid5/6 for /var for a server. Or a gluster volume at /var or /home.

Partitions are kindof annoying actually, for the exact reason of what happens
when the partition gets full. LVM makes this easier to manage because you can
resize an LV and then the filesystem. Even better is LVM thin provisioning,
where you make each volume an ideal size for its practical lifetime, it only
consumes from the VG what is actually being used. Filesystem resize is avoided,
which causes certain inefficiencies anyway and just adds to the
non-deterministic nature of filesystems (Btrfs is sortof an exception).

isnt that more of a problem vs one big /data partition where that is not an
issue?

Sure so use one big partition and maybe quotas to contain things, or LVM, or
gluster or ceph volumes. /boot on a plain partition makes sense, and for
workstations/laptops it's useful to have /home separate just because it makes
OS reinstalls easier than blowing away a whole system and restoring /home from
a backup.

what would you guys say the best solution would be? also read that you want
to have twice as much swap as RAM and that dividing swap into 2 partitions
helps with performance. is this true?

Best solution depends on the problem you want to avoid or solve. The
installer's python-blivet code has swap recommendations. It's something like 2x
up to a certain amount of memory, then it's 1x, and above maybe 64GB it's 1/2.
You really don't want to be under swap pressure with any regularity, to the
point if this is a server you might be better off with swap on an SSD. If
you're using XFS, you can estimate memory requirements for fs repair using:

xfs_repair -n -vv -m 1 dev

If you give xfs_repair the minimum it could be hours for a repair, not good for
a server. So again, if you can't afford the right amount of RAM to support the
filesystem size, then in a bind you can use an SSD for swap and while it won't
be fast it won't be dog slow (hours or days).

http://xfs.org/index.php/XFS_FAQ#Q:_Which_factors_influence_the_memory_usage_of_xfs_repair.3F

Chris Murphy
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

VM not accepted by NFS server -

2014-07-23 Thread Bob Goodwin - Zuni, Virginia, USA



I've created an Centos7 VM in this updated Fedora-20 box. NFS always 
works without a hitch however I can't mount the server from the VM.


[root@localhost bobg]# mount 192.168.1.8:/home/bobg/  /mnt/HOME1/
mount.nfs: access denied by server while mounting 192.168.1.8:/home/bobg/

Nothing changes, the hardware is a constant, but it says the server 
denies access and I can't see why, where can I be going wrong? Ssh, 
sftp, and ping all work from the VM, I just can't mount it from NFS.


Any help appreciated,

Bob

--
http://www.qrz.com/db/W2BOD
box10  Fedora-20/64bit Linux/XFCE

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: systemd config files???

2014-07-23 Thread Anders Wegge Keller

Rahul Sundaram methe...@gmail.com writes:

 Hi
 
 
 On Tue, Jul 22, 2014 at 4:39 PM, Anders Wegge Keller  wrote:
 
 
   The specific wording: requires users to modify files below /usr.
 
 
 I am not sure picking up some words without the context is useful.  If you
 read the full email, it was obviously talking about configuration files.

 Instead of having to guess at the meaning, why not just state the
intention without the absolutism? And depending on the definition of
what a configuration file actually is, even that statement brings at
least the kernel source and texlive-* into bad standing.

-- 
/Wegge

Leder efter redundant peering af dk.*,linux.debian.*
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: VM not accepted by NFS server -

2014-07-23 Thread Chris Adams

Once upon a time, Bob Goodwin - Zuni, Virginia, USA bobgood...@wildblue.net 
said:
 I've created an Centos7 VM in this updated Fedora-20 box. NFS always
 works without a hitch however I can't mount the server from the VM.
 
 [root@localhost bobg]# mount 192.168.1.8:/home/bobg/  /mnt/HOME1/
 mount.nfs: access denied by server while mounting 192.168.1.8:/home/bobg/

Possibly NFSv4 vs. NFSv3?  RHEL/CentOS 6 and earlier (and Fedora before
around 17 IIRC) default to NFSv3 mounts, while newer stuff defaults to
NFSv4.

Try adding -o nfsvers=3.

-- 
Chris Adams li...@cmadams.net
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

device p3p1 entered promiscuous

2014-07-23 Thread pgaltieri .

Today I noticed for the first time that I'm getting the following messages
in /var/log/messages on one of my F19 systems.

Jul 23 10:55:03 terrapin kernel: [  122.662105] device p3p1 entered
promiscuous mode
Jul 23 10:55:08 terrapin kernel: [  127.669312] device p3p1 left
promiscuous mode

These messages occur every 5 minutes and last 5 seconds.

I have 2 other F19 systems running on the same network that do not show
these messages.  The system that is seeing this problem is a Dell Inspiron
7537.

Anyone seen something similar?

I have attached the output of ps axlw in case someone can see which process
might be doing this.

This problem seems to have started on July 6 based on looking at the old
logs

[pgaltieri@terrapin Downloads]$ sudo grep promisc
/var/log/messages-20140629 | wc -l
27
[pgaltieri@terrapin Downloads]$ sudo grep promisc
/var/log/messages-20140706 | wc -l
21
[pgaltieri@terrapin Downloads]$ sudo grep promisc
/var/log/messages-20140713 | wc -l
1752
[pgaltieri@terrapin Downloads]$ sudo grep promisc
/var/log/messages-20140720 | wc -l
2843

Any help is appreciated.

Paolo


PS
Description: Binary data
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: device p3p1 entered promiscuous

2014-07-23 Thread Chris Adams

Once upon a time, pgaltieri . pgalti...@gmail.com said:
 Today I noticed for the first time that I'm getting the following messages
 in /var/log/messages on one of my F19 systems.
 
 Jul 23 10:55:03 terrapin kernel: [  122.662105] device p3p1 entered
 promiscuous mode
 Jul 23 10:55:08 terrapin kernel: [  127.669312] device p3p1 left
 promiscuous mode
 
 These messages occur every 5 minutes and last 5 seconds.

I'd check for cron jobs, sudo crontab -l and look in /etc/cron.d.

-- 
Chris Adams li...@cmadams.net
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: Taking the BTRFS plunge

2014-07-23 Thread Chris Murphy


On Jul 17, 2014, at 4:08 PM, Lists li...@benjamindsmith.com wrote:

 As a ZFS on Linux user, I noticed that there are btrfs packages for Fedora 
 20. Can anybody here comment on their stability? Are you adventurous enough 
 to use btrfs on root ? Has it saved your data? Have you lost data because of 
 it?
 
 Context: I'm planning on moving /home on my laptop to ZFS/BTRFS soon.

I think the top two things to keep in mind with Btrfs is: a.) don't 
underestimate the need for backing up; b.) don't use 'btrfs check --repair' 
a.k.a. btrfsck --repair, unless you've posted the specifics of your problem on 
the linux-btrfs@ list, it's still kinda dangerous. As in, it can make things 
worse. 

You always want to try 'mount -o recovery' first if a filesystem fails to 
mount. Then mount -o ro,recovery which if successful will at least let you 
update your backup before proceeding. Then possibly btrfs-zero-log at the 
expense of losing the most recent ~30 seconds of data. It is OK to do btrfs 
check without --repair, it only reports and it's good to include it in posting 
to linux-btrfs@.

I've found btrfs to be quite stable in single disk configurations. Most crashes 
I've had, btrfs either has no problem or repairs itself on normal mount. A 
small number of cases it wouldn't mount and I had to use 'mount -o recovery' 
which fixed the problem. But there are still many edge cases not yet fixed, and 
still being found, and there are different repair methods depending on the 
problem. So very quickly it can get chaotic.

Multiple device Btrfs volumes are much simpler in some respects than LVM or 
mdraid. But error notification is still weak. There's also confusion about how 
to properly report filesystem usage with df. The behaviors you get when 
mounting a file system degraded aren't always obvious either. Two recent 
problems I stumbled on:

1. systemd hangs waiting forever (no limit) for a missing root fs UUID when 
booting btrfs with a missing device. This happens due to some problems between 
btrfs kernel code and udev not making the volume UUID available when devices 
are missing; therefore systemd won't even attempt to mount root fs. OK so you 
use rd.break=pre-mount to get to a dracut shell before this hang; and then you 
have to know to use 'mount -o subvol=root,degraded /dev/sdaX /sysroot' and then 
'exit' twice. That's pretty icky UX wise.

2. Just yesterday I lost a test system on btrfs. I'd successfully mounted a 
single device degraded (simulated failed 2nd device), and successfully 
converted it from raid1 to single profile. However I'd forgotten to btrfs 
device delete missing to get rid of the 2nd device. Upon reboot, I wasn't 
permitted to mount the single device normally *OR* degraded. I could mount it 
ro,degraded but since it's ro, I can't use 'btrfs device delete' nor can I 
create read-only subvolume to use with btrfs send/receive. So yeah I can mount 
it ro, and get data off of it with cp or rsync, but basically it's not fixable 
and I'll have to blow it away.

*shrug*

So I'd say if you want something quite stable, use better hard drives and XFS, 
optionally with LVM so you can use pvmove; and thinp snapshots which don't 
suffer the performance or setup troubles conventional LVM snapshots do.


Chris Murphy
-- 
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: VM not accepted by NFS server -


On 23.07.2014 20:21, Chris Adams wrote:

Once upon a time, Bob Goodwin - Zuni, Virginia, USA bobgood...@wildblue.net 
said:

I've created an Centos7 VM in this updated Fedora-20 box. NFS always
works without a hitch however I can't mount the server from the VM.

[root@localhost bobg]# mount 192.168.1.8:/home/bobg/  /mnt/HOME1/
mount.nfs: access denied by server while mounting 192.168.1.8:/home/bobg/


Possibly NFSv4 vs. NFSv3?  RHEL/CentOS 6 and earlier (and Fedora before
around 17 IIRC) default to NFSv3 mounts, while newer stuff defaults to
NFSv4.

Try adding -o nfsvers=3.



/etc/sysconfig/nfs
RPCNFSDARGS=-d -s

systemctl restart nfs-server
journalctl -f --full


nfsd fan club


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: VM not accepted by NFS server -

2014-07-23 Thread Bob Goodwin - Zuni, Virginia, USA



On 07/23/14 14:21, Chris Adams wrote:

Once upon a time, Bob Goodwin - Zuni, Virginia, USA bobgood...@wildblue.net 
said:

I've created an Centos7 VM in this updated Fedora-20 box. NFS always
works without a hitch however I can't mount the server from the VM.

[root@localhost bobg]# mount 192.168.1.8:/home/bobg/  /mnt/HOME1/
mount.nfs: access denied by server while mounting 192.168.1.8:/home/bobg/

Possibly NFSv4 vs. NFSv3?  RHEL/CentOS 6 and earlier (and Fedora before
around 17 IIRC) default to NFSv3 mounts, while newer stuff defaults to
NFSv4.

Try adding -o nfsvers=3.



No, that's not it,

[root@localhost bobg]#  mount -o nfsvers=3 192.168.1.8:/home/bobg/  
/mnt/HOME1/

mount.nfs: access denied by server while mounting 192.168.1.8:/home/bobg/

But it does connect to my freenas server,

# mount 192.168.1.48:/mnt/nasdata/box48bobg  /mnt/BOX48

[root@localhost BOX48]# ll
total 88
drwxr-xr-x. 4 1001 root 1024 Apr 23 14:39 Apps
drwxr-xr-x. 2 1001 root  512 Jul 12 10:43 AvStuff
drwxr-xr-x. 2 1001 root  512 Apr 19 16:25 BookCLI
drwxr-xr-x. 2 1001 root 4096 Jun 13 17:09 digicam
drwxr-xr-x. 7 1001 root  512 Apr 15 18:21 gramps
drwxr-xr-x. 2 1001 root 2048 Apr 23 14:40 icons
drwxrwxr-x. 2 root root  512 Apr 23 14:17 notecase
drwxrwxrwx. 2 1001 root 1536 Jul 19 14:19 oocalc

.  snip  ...

Thanks,  Bob

--
http://www.qrz.com/db/W2BOD
box10  Fedora-20/64bit Linux/XFCE

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: VM not accepted by NFS server -

2014-07-23 Thread Bob Goodwin - Zuni, Virginia, USA



On 07/23/14 15:06, poma wrote:


/etc/sysconfig/nfs
RPCNFSDARGS=-d -s

systemctl restart nfs-server
journalctl -f --full


nfsd fan club


Ok, not sure what that did but now it's mounted. Hopefully it will work 
after a reboot.


Thank you,

Bob

--
http://www.qrz.com/db/W2BOD
box10  Fedora-20/64bit Linux/XFCE

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: VM not accepted by NFS server -


On 23.07.2014 22:59, Bob Goodwin - Zuni, Virginia, USA wrote:


On 07/23/14 15:06, poma wrote:


/etc/sysconfig/nfs
RPCNFSDARGS=-d -s

systemctl restart nfs-server
journalctl -f --full


nfsd fan club


Ok, not sure what that did but now it's mounted. Hopefully it will work
after a reboot.

Thank you,

Bob



First you adjust the debug logging directed to syslog, then it is applied, and 
with the journalctl, you can monitor server events. ;)


poma


--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: VM not accepted by NFS server -

2014-07-23 Thread Bob Goodwin - Zuni, Virginia, USA



On 07/23/14 17:28, poma wrote:


First you adjust the debug logging directed to syslog, then it is 
applied, and with the journalctl, you can monitor server events. ;)



poma 


Well this appears to be the area of interest however I don't know how to 
interpret it?


Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Mount 
Daemon...

Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Mount Daemon.
Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Server...
Jul 23 16:51:45 localhost.localdomain rpc.mountd[5596]: Version 1.3.0 
starting
Jul 23 16:51:45 localhost.localdomain kernel: NFSD: starting 90-second 
grace period (net 819a09c0)

Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Server.
Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFSv4 ID-name 
mapping daemon...
Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Remote 
Quota Server...
Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Remote 
Quota Server.
Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFSv4 ID-name 
mapping daemon.
Jul 23 16:54:04 localhost.localdomain dhclient[1081]: DHCPREQUEST on 
eth0 to 192.168.122.1 port 67 (xid=0xa15c2e7)
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: DHCPREQUEST 
on eth0 to 192.168.122.1 port 67 (xid=0xa15c2e7)
Jul 23 16:54:04 localhost.localdomain dhclient[1081]: DHCPACK from 
192.168.122.1 (xid=0xa15c2e7)
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: DHCPACK from 
192.168.122.1 (xid=0xa15c2e7)
Jul 23 16:54:04 localhost.localdomain dhclient[1081]: bound to 
192.168.122.14 -- renewal in 1474 seconds.
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: bound to 
192.168.122.14 -- renewal in 1474 seconds.
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: info 
(eth0): DHCPv4 state changed renew - renew
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: info   
address 192.168.122.14
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: info   plen 
24 (255.255.255.0)
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: info   
gateway 192.168.122.1
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: info   
server identifier 192.168.122.1
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: info   
lease time 3600
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: info   
nameserver '192.168.122.1'
Jul 23 16:54:04 localhost.localdomain dbus[665]: [system] Activating via 
systemd: service name='org.freedesktop.nm_dispatcher
Jul 23 16:54:04 localhost.localdomain dbus-daemon[665]: dbus[665]: 
[system] Activating via systemd: service name='org.freedes
Jul 23 16:54:04 localhost.localdomain systemd[1]: Starting Network 
Manager Script Dispatcher Service...
Jul 23 16:54:04 localhost.localdomain dbus-daemon[665]: dbus[665]: 
[system] Successfully activated service 'org.freedesktop.n
Jul 23 16:54:04 localhost.localdomain dbus[665]: [system] Successfully 
activated service 'org.freedesktop.nm_dispatcher'



--
http://www.qrz.com/db/W2BOD
box10  Fedora-20/64bit Linux/XFCE

--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: VM not accepted by NFS server -

2014-07-23 Thread Rick Stevens

On 07/23/2014 04:14 PM, Bob Goodwin - Zuni, Virginia, USA issued this 
missive:


On 07/23/14 17:28, poma wrote:


First you adjust the debug logging directed to syslog, then it is
applied, and with the journalctl, you can monitor server events. ;)


poma


Well this appears to be the area of interest however I don't know how to
interpret it?

Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Mount
Daemon...
Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Mount Daemon.
Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Server...
Jul 23 16:51:45 localhost.localdomain rpc.mountd[5596]: Version 1.3.0
starting
Jul 23 16:51:45 localhost.localdomain kernel: NFSD: starting 90-second
grace period (net 819a09c0)
Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Server.
Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFSv4 ID-name
mapping daemon...
Jul 23 16:51:45 localhost.localdomain systemd[1]: Starting NFS Remote
Quota Server...
Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFS Remote
Quota Server.
Jul 23 16:51:45 localhost.localdomain systemd[1]: Started NFSv4 ID-name
mapping daemon.
Jul 23 16:54:04 localhost.localdomain dhclient[1081]: DHCPREQUEST on
eth0 to 192.168.122.1 port 67 (xid=0xa15c2e7)
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: DHCPREQUEST
on eth0 to 192.168.122.1 port 67 (xid=0xa15c2e7)
Jul 23 16:54:04 localhost.localdomain dhclient[1081]: DHCPACK from
192.168.122.1 (xid=0xa15c2e7)
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: DHCPACK from
192.168.122.1 (xid=0xa15c2e7)
Jul 23 16:54:04 localhost.localdomain dhclient[1081]: bound to
192.168.122.14 -- renewal in 1474 seconds.
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: bound to
192.168.122.14 -- renewal in 1474 seconds.
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: info
(eth0): DHCPv4 state changed renew - renew
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: info
address 192.168.122.14
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: info   plen
24 (255.255.255.0)
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: info
gateway 192.168.122.1
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: info server
identifier 192.168.122.1
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: info lease
time 3600
Jul 23 16:54:04 localhost.localdomain NetworkManager[757]: info
nameserver '192.168.122.1'
Jul 23 16:54:04 localhost.localdomain dbus[665]: [system] Activating via
systemd: service name='org.freedesktop.nm_dispatcher
Jul 23 16:54:04 localhost.localdomain dbus-daemon[665]: dbus[665]:
[system] Activating via systemd: service name='org.freedes
Jul 23 16:54:04 localhost.localdomain systemd[1]: Starting Network
Manager Script Dispatcher Service...
Jul 23 16:54:04 localhost.localdomain dbus-daemon[665]: dbus[665]:
[system] Successfully activated service 'org.freedesktop.n
Jul 23 16:54:04 localhost.localdomain dbus[665]: [system] Successfully
activated service 'org.freedesktop.nm_dispatcher'


Bob, get on the NFS server and verify that it's allowing mounts from the
DHCP domain. It appears your VM is using DHCP to get an IP and it may be
that your NFS server isn't exporting to the network or IP your client
got via DHCP.

The fact you got it mounted this time may just indicate that THIS TIME
you got an IP allowed by the server. Next time, you may not be so
lucky. :-/
--
- Rick Stevens, Systems Engineer, AllDigitalri...@alldigital.com -
- AIM/Skype: therps2ICQ: 22643734Yahoo: origrps2 -
--
- Millihelen (n): The amount of beauty required to launch one ship.  -
--
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/users
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org

Re: VM not accepted by NFS server -