4K monitors?
by Tom Horsley
I see prices are getting better on 4K monitors (samsung has
one on sale for $599 at the moment), but I still find it
impossible to figure out if any given video card will
actually work with one :-(.
Is anyone using a 4K monitor on fedora with open source
video drivers and actually getting a 60HZ 3840x2160
image of a single desktop?
If so, care to share which video card and monitor
you use?
9 years, 9 months
Updates gui broken in F20?
by Richard Shaw
I usually use yum from cli so it's not a big deal for me but lately when
I've gotten the updates notification in gnome-shell, when I click "install
updates" nothing happens.
Anyone else seeing this?
Thanks,
Richard
9 years, 9 months
Network availability systemd dependency failure at boot
by Sam Varshavchik
It looks like after the last systemd update, systemd appears to start jobs
that have a dependency on network availability before the network is
actually up.
After booting, a crapload of services reliably fail to start: httpd, dhcpd,
named, and others. All of them come up fine if I manually start them, after
boot completes.
Sifting through /var/log/messages, the common thread is that the network is
NOT up, when the jobs start:
Jul 5 07:16:41 shorty httpd: (99)Cannot assign requested address: AH00072:
make_sock: could not bind to address 216.27.136.223:8443
Jul 5 07:16:41 shorty httpd: no listening sockets available, shutting down
Jul 5 07:16:41 shorty httpd: AH00015: Unable to open logs
And:
Jul 5 07:16:40 shorty dhcpd:
Jul 5 07:16:40 shorty dhcpd: No subnet declaration for lan0 (no IPv4
addresses).
Jul 5 07:16:40 shorty dhcpd: ** Ignoring requests on lan0. If this is not
what
Jul 5 07:16:40 shorty dhcpd: you want, please write a subnet declaration
Jul 5 07:16:40 shorty dhcpd: in your dhcpd.conf file for the network segment
Jul 5 07:16:40 shorty dhcpd: to which interface lan0 is attached. **
Jul 5 07:16:40 shorty dhcpd:
Jul 5 07:16:40 shorty dhcpd:
Jul 5 07:16:40 shorty dhcpd: Not configured to listen on any interfaces!
Here's bind shutting down before the server reboot:
Jul 5 07:14:30 shorty named[1072]: no longer listening on 127.0.0.1#53
Jul 5 07:14:30 shorty named[1072]: no longer listening on 192.168.0.1#53
Jul 5 07:14:30 shorty named[1072]: no longer listening on 216.254.115.190#53
Note all the IP addresses that my bind is listening on. Now, here's bind
again, when the system comes up after a reboot:
Jul 5 07:16:39 shorty named[1071]: loading configuration from
'/etc/named.conf'
Jul 5 07:16:39 shorty named[1071]: using default UDP/IPv4 port range:
[1024, 65535]
Jul 5 07:16:39 shorty named[1071]: using default UDP/IPv6 port range:
[1024, 65535]
Jul 5 07:16:39 shorty named[1071]: listening on IPv4 interface lo,
127.0.0.1#53
Jul 5 07:16:39 shorty named[1071]: generating session key for dynamic DNS
…
That's it. Only 127.0.0.1 was up for bind to listen on. Even lan0,
192.168.0.1, isn't up yet.
Sifting through systemd docs, it appears that services that require network
availability should state an After dependency on "network-online.target".
Wonderful. Can someone explain why, if that's true, only kdump.service
appears to explicitly state that dependency?
[root@shorty system]# fgrep -- network-online.target *.target
[root@shorty system]# fgrep -- network-online.target *.service
kdump.service:After=network.target network-online.target remote-fs.target
So, I see two possible explanations:
1) network-online.target was introduced in the most recent systemd update.
Prior to that, its equivalent functionality was done in some other way,
possibly integrated with network.target. The last update unceremoniously
introduced network-online.target, with no advance notice, and without any
coordination with packages that need to use it, and thus breaking everything.
2) everything was always like that. Everything was always broken, but until
the recent systemd update, its internal logic happened to kick things off in
the right order. The last update changed some internal scheduling logic, and
now everything is broken.
So, how should this mess get fixed? Start filing bugs against all these
packages, requesting a change to their systemd service file, to state a
dependency on network-online.target?
9 years, 9 months
Re: Network availability systemd dependency failure at boot
by R. G. Newbury
> On Sat, 05 Jul 2014 08:13:45 -0400
> Sam Varshavchik wrote:
>
>> Everything was always broken
>
> I'm pretty sure everything was always broken.
> I never had the combination of postfix, dovecot,
> and stunnel operational more than about 10% of
> the time with pure systemd.
>
> I just took a more practical approach and made
> an rc.local script that restarted services I found
> not always coming up right after a short delay.
> This sort of thing:
>
> /bin/bash -c 'sleep 5 ; service stunnel restart' > /dev/null 2>&1 < /dev/null &
> /bin/bash -c 'sleep 7 ; service postfix restart' > /dev/null 2>&1 < /dev/null &
>
> That at least works up to the day systemd decides
> no one needs rc.local and they drop support for
> it (a day that is sure to come :-).
Direct support for rc.local has already been "deprecated". Somewhere I
read something from Lennart and it was clear that he has an almost
religious hatred for doing things 'the old way', so much so that
rc.local is not 'desired'.
And since systemd wants to run everything as the final user, there are
all lots of problems now in creating folders etc which were easy to do
before and difficult now, which some lines in rc.local can easily avoid.
But not easy to set up.
I've been playing with using @reboot in a cron script. Using @reboot is
effectively a run-once trigger for cron. I am still not sure exactly
when in the boot sequence the @reboot is triggered. Hopefully after the
network is up! ( The @reboot gem learnt from that dangerous extremist
publication Linux Journal!)
Geoff
9 years, 9 months
X thinks it is up, but screen is black?
by Tom Horsley
In my quest for more pixels, I'm trying to get my
new UHD monitor working in 3840x2160 resolution.
The nouveau driver doesn't know how to drive
the GTX 750Ti card, so I had to install the
nvidia binary drivers from rpmfusion.
At this point, everything seems to work except
for the one minor detail that the screen is
always black :-).
X thinks it is up and running, the Xorg log
file shows it recognizing the video card
and selecting 3840x2160 resolution. Nothing
that seems like an error appears anywhere
I've looked. I just have that black screen
problem (Ctrl-Alt-F2 does get me to a console,
so it works fine in console mode - it also
worked in 1920x1080 mode on a different
video source that couldn't support UHD
resolution).
Does any of this sound familiar to anyone?
(I'm off to try stuff like a different cable
in the hope that it is something dumb).
9 years, 9 months
lxde
by Balint Szigeti
hello all,
does somebody tell me, lxde can handle the dual monitor? I mean, the DE
will give 2 desktop instead of monitor extend or duplication. So, if I
press, ctrl-tab on 1 monitor it will show the windows in that screen and
the other will be independent.
Balint
9 years, 9 months
OT: Web server no longer works
by Jonathan Ryshpan
I run a small weather station that acts as a web server. Recently it's
become impossible to access it via the web, though I can still access it
over my local network. Some details:
* My ISP is AT&T using their Uverse service.
* The server was accessible from the web a month or so ago.
* The server has web address oaklandweather.no-ip.org, which
currently resolves to 99.121.57.131, and probably will for some
time.
* I can ping the server either over the LAN or via the web without
trouble.
* An attempt to connect to the weather station as a web server
(HTTP) times out.
I'm pretty sure that the Uverse gateway is set up correctly: It worked
properly in the past and I haven't made any changes to it. An
inspection of the settings doesn't show anything obviously wrong.
Has AT&T changed its terms of service? I vaguely remember the terms of
service don't allow customers to run servers; but I can't find any such
restriction in documents available on the web. Also the (AT&T supplied)
gateway has a function to explicitly open a "pinhole" allowing HTTP
service from a computer on the customer side of the gateway.
Thanks - jon
9 years, 9 months
postfix starting before network
by David Benfell
Hi all,
I have no idea why this might be happening. I've looked at the systemd
control file for postfix and compared it to dovecot's. Both want the
network.target before starting.
The difference is that dovecot starts correctly. Postfix does not. The
problem has only appeared since Saturday, when I probably did a yum
update.
Postfix issues an error from one of the pre-commands having to do with
the aliases database saying its network interface (and it duly lists
the IPv4 address) doesn't exist. Starting postfix manually later
works.
Thanks!
--
David Benfell <benfell(a)parts-unknown.org>
See https://parts-unknown.org/node/2 if you don't understand the
attachment.
9 years, 10 months
changes made to a file are also made in his copy
by angelo.moreschini@medident-sw.it
Hi,
I apologize for a trivial question but that's because I yet have not much experience with Linux.
I made, some time ago, a copy of the smb.conf file, for security reasons, before making to it any changes:
(cp smb.conf.original smb.conf.original.orig )
Yesterday I wanted to give a look at the contents of the old file(smb.conf.original) that I had copied; but I found that both files have the same content.
I made other changes, in order to do experiments, and I have always seen that the changes made to a file are always shown on the other file.
The command "ls -l" shows the two files are colored blue which (I think) indicates that the files are a link to each other.
Since I am convinced that I used the "cp" command; my question is:
which mistake can I have made to create a link of the file instead of a copy of it?
Thank you
Regards
Angelo
9 years, 10 months