On 26 December 2016 at 07:47, bruce wrote:
> ls /cloud_nfs/*PID.dat
>
> /cloud_nfs/1.2.3.4_PID.dat
> /cloud_nfs/100.2.3.4_PID.dat
>
>
> find . -regex '*\./*(\d+.\d+)*' not working.. ive seen multiple
> examples.. so i'm doing something wrong...
>
> i've cd'd to the dir in question to run th
I am trying to setup a home server under Centos. I relegated my well working
iptables script to plan B.
The server acts as a modem/router. enp3s0 is the NIC for the internal private
network.
enp6s0/ ppp0 provide WAN access. I assigned enp3s0 to internal zone and added
services.
pppoe daemon is u
I am trying to setup a home server under Centos. I relegated my well
working iptables script to plan B. The server acts as a modem/router.
enp3s0 is the NIC for the internal private network. enp6s0/ ppp0 provide
WAN access. I assigned enp3s0 to internal zone and added services. pppoe
daemon is up a
On Mon, 2016-12-26 at 07:55 +0800, Ed Greshko wrote:
> For some reason there is no "Waiting for process" in the failing case. So,
> it would seem,
> either the PID being checked had already finished but another one had started
> and locked
> the database but somehow dnf is unaware of it and trie
Thanks Ahmad
Mind totally blew by the regextype attribute... simple works as expected..
'ppreciate it..
On Mon, Dec 26, 2016 at 5:29 AM, Ahmad Samir wrote:
> On 26 December 2016 at 07:47, bruce wrote:
>> ls /cloud_nfs/*PID.dat
>>
>> /cloud_nfs/1.2.3.4_PID.dat
>> /cloud_nfs/100.2.3.4_PID.dat
On 12/26/16 20:37, Patrick O'Callaghan wrote:
> On Mon, 2016-12-26 at 07:55 +0800, Ed Greshko wrote:
>> For some reason there is no "Waiting for process" in the failing case. So,
>> it would seem,
>> either the PID being checked had already finished but another one had
>> started and locked
>>
On Mon, 2016-12-26 at 21:56 +0800, Ed Greshko wrote:
>
> On 12/26/16 20:37, Patrick O'Callaghan wrote:
> > On Mon, 2016-12-26 at 07:55 +0800, Ed Greshko wrote:
> > > For some reason there is no "Waiting for process" in the failing case.
> > > So, it would seem,
> > > either the PID being checked
I have a 3rd party app that use a Java GUI, so it won't run on a headless JVM.
I had it working until I installed a different app using dnf. It overwrote my
JVM with a headless one and now the Java GUI app is broken. Is there a way to
install/register a non-headless JVM with Fedora so it won'
http://www.projectatomic.io/blog/2015/06/notes-on-fedora-centos-and-docker-storage-drivers/
Does the above recommendation still hold true with Fedora 25/Docker 1.12.5?
If so, is the configuration the same?
Thanks,
Dave
___
users mailing list -- users@list
I followed the instructions in the Fedora 25 Installation Guide and the DNF
system upgrade document, using `sudo dnf system-upgrade download --refresh
--releasever=25` and then the `sudo dnf system-upgrade reboot` command.
I then worked through an issue with the stock repositories and packages
cau
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi,
has anybody got the same problem? I added the LibreOffice-Writer icon to
gnome-shell favourites, but if I start the Writer it generates a new
icon looking like some icon for gnome-terminal. I already had this
problem a couple of years ago, as gn
Last time this came up, it was because the running LibreOffice binary name
doesn't match the application name that was added to the dock. I think a fix
has to come from LibreOffice's / LO's packager.
Cheers!
Eric
> On Dec 26, 2016, at 16:11, Anca Tibor Attila wrote:
>
> -BEGIN PGP SIGNED
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Am Montag, den 26.12.2016, 16:26 -0500 schrieb Eric Griffith:
> Last time this came up, it was because the running LibreOffice binary
> name doesn't match the application name that was added to the dock. I
> think a fix has to come from LibreOffice's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi
Am Montag, den 26.12.2016, 16:26 -0500 schrieb Eric Griffith:
> Last time this came up, it was because the running LibreOffice binary
> name doesn't match the application name that was added to the dock. I
> think a fix has to come from LibreOffic
I have been getting random GPU lockups on Fedora 25.
I have the following GPU: VGA compatible controller: Advanced Micro Devices,
Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 6530M/6550M]
I use the opensource driver on Wayland. I'm think the beginning of the random
lockups coincided
On Mon, 2016-12-26 at 20:58 +, Schlaegel wrote:
> I followed the instructions in the Fedora 25 Installation Guide and the DNF
> system upgrade document, using `sudo dnf system-upgrade download --refresh
> --releasever=25` and then the `sudo dnf system-upgrade reboot` command.
>
> I then worked
On Mon, Dec 26, 2016 at 12:37:46PM -0700, Dave Johansen wrote:
> http://www.projectatomic.io/blog/2015/06/notes-on-fedora-centos-and-docker-storage-drivers/
> Does the above recommendation still hold true with Fedora 25/Docker 1.12.5?
> If so, is the configuration the same?
Quick glance, yeah, loo
On 12/26/2016 04:21 PM, Patrick O'Callaghan wrote:
On Mon, 2016-12-26 at 20:58 +, Schlaegel wrote:
After a month of updates, I started seeing warnings about the size of the
var partition. Somehow /var/cache/PackageKit/24/metadata is still there and
very large. I tried `sudo pkcon refresh for
18 matches
Mail list logo
