Into cups printer configuration file, I have set "ErrorPolicy retry-
job". When I print to a printer power off, I do not want stop printer,
I want cups still try to print until printer is power on.
And this work great if I print on a Fedora server (without GUI).
If I print a document from gnome on a printer unplugged or power off,
this printer is stopped, and when I power on it, I must go to into
control panel to start it.
How to disable this Gnome "unconfigurable" behavior (into Gnome contro
panel there are no options to do this)?
(inviato dal mio Linux Fedora 26 Workstation)
Over the past few weeks, my laptop has been running chronyc at full blast.
12657 root 20 0 20624 1308 1160 R 93.8 0.0 1739:52 chronyc
I looked up chronyc and found that this controls NTP. I use NTP, but do I need to keep this around? Or is the good old ntp good enough? From what I understand, openntp would also work but that is not available on Fedora.
I guess I am wondering if there is a major cost to sudo dnf erase chronyc -y.
Important Notice: This mailbox is ignored: e-mails are set to be deleted on receipt. Please respond to the mailing list if appropriate. For those needing to send personal or professional e-mail, please use appropriate addresses.
On 10/05/17 20:54, Corey Sheldon wrote:
> On 10/4/17 9:14 PM, Ed Greshko wrote:
>> On 10/04/17 23:39, Patrick Dupre wrote:
>>> During the last update, I got:
>>> dnf update
>>> [DRPM 11/13] hplip-3.17.6-1.fc26_3.17.9-1.fc26.x86_64.drpm: done
>>> /var/lib/selinux/targeted/active/policy.kern: read error
>>> (tried to read 398 bytes from offset 3897904)
>>> cannot reconstruct rpm from disk files
>>> [DRPM 12/13] firefox-55.0.3-1.fc26_56.0-2.fc26.x86_64.drpm: done
>>> Is it a serious issue?
>> users mailing list -- users(a)lists.fedoraproject.org
>> To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
> If it repeats and can never be pulled it would be, that on a mirror or two merely
> means it had a partial or your connection during that pull got iffy/squirrel-ly.
It isn't a problem at all since it is a failure of the drpm. Had the OP posted the
rest of the transaction you'd see that it continued on and downloaded the whole rpm.
Fedora Users List - The place to go to speculate endlessly
Because Legacy Software, I need to be able to support SSLv3 on my
Postfix server. From what I can figure, however, this is disabled
in the SSL library itself, as I still cannot get a successful
handshake with the following configuration line, which seems to me
like it should be enough to enable it:
smtpd_tls_mandatory_protocols = !SSLv2
If anyone has any clues, I'd be very appreciative of any help.
// Nelson Crosby
/* nc(a)sourcecomb.com */
During the last update, I got:
[DRPM 11/13] hplip-3.17.6-1.fc26_3.17.9-1.fc26.x86_64.drpm: done
/var/lib/selinux/targeted/active/policy.kern: read error
(tried to read 398 bytes from offset 3897904)
cannot reconstruct rpm from disk files
[DRPM 12/13] firefox-55.0.3-1.fc26_56.0-2.fc26.x86_64.drpm: done
Is it a serious issue?
Patrick DUPRÉ | | email: pdupre(a)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
My Firefox has been upgraded to version 56 (F26) and I cannot use
flash pages any more. I have the addon installed and in click-to-play
mode, but I just get an empty space. Is it a bug? I though flash is
still going to be supported until 2020.
Im' looking for a way to enable evolution with ms-tnef winmail.dat.
Searching the Web I found that a possible solution is to install ytnef.
So i tried that:
# dnf list ytnef
Last metadata expiration check: 0:06:48 ago on Wed 04 Oct 2017 10:18:41
# dnf install ytnef
Last metadata expiration check: 0:08:23 ago on Wed 04 Oct 2017 10:18:41 AM CEST.
Problem: conflicting requests
- nothing provides libytnef.so.0()(64bit) needed by ytnef-2.6-16.fc26.x86_64
# dnf whatprovides libytnef.so
Last metadata expiration check: 0:09:14 ago on Wed 04 Oct 2017 10:18:41 AM CEST.
Error: No Matches found
What can be wrong?
Looking for some feedback and some direction on not only the feasibility
but does it makes sense to do.
The scenario is this, this is Fedora 26 system, running RAID1 on all
disk partitions, there are only 2 disks in the system with 4 raid
/dev/md125 / - md125 : active raid1 sdb1 sda1
/dev/md127 /boot - md127 : active raid1 sdb3 sda3
/dev/md124 /home - md124 : active raid1 sdb5 sda5
/dev/md126 [swap] - md126 : active raid1 sdb2 sda2
The thought is to use flash of some sort to do the initial boot (eg USB
flash) and then continue with the boot using the installed disks. If
this is the case is it the /boot partition that gets moved to flash? is
it grub that gets moved? Or is it both? /boot is currently using about
The thought behind this to protect against a disk failure and being
unable to boot on the remaining good disk, flash being solid state I
would assume it would be more reliable, plus since I'm not looking to
constantly write to the partition "wearing out" the media wouldn't be an
USB device I was thinking about is Z-U130 eUSB SSD, they appear to be
available as 1, 2, 4, & 8 GB modules.
I know this isn't strictly "Fed" related, but the group might have suggestions.
My use case, the process has a number of remote servers. I'd like to
be able to run a bunch of commands on the remote servers as fast as
posible. The initial thought was to loop through the different
IPAddresses, and SSH into each server, to run the commands.
However, this process was still "sequential" in that each SSH session
needs to complete, prior to running the next server/ssh command.
So, my question/need -- is to figure out how to run a ssh as a
background on the local server. This approach would/should allow the
process to quickly fire off commands to the remote ipaddresses/servers
in a much faster/parallel manner.
foreach iplist as ipaddress
ssh user1@ipaddress command & (assuming that the '&' runs the local
ssh in the background -- it doesn't!)
Running "stuff" on the remote can occur in a "Screen" session, which
would allow the ssh process to fire off the remote cmd, but it still
doesn't run the local ssh as a "background" process..
Rick has mentioned/discussed the "Screen" function in past threads.