I’ve just started receiving low disk space warnings from my server.
"Inodes: /dev/sda8 (/home) is 98% full -- 3.7M of 3.8M used, 99K remain”
df -h "/dev/sda8 60G 53G 3.9G 94% /home”
Does anyone have any idea what could be up?
Latest version of Fedora, all up to date.
I have had issues with batti for quite a while, and I came across battray as a replacement (and it works). So, I was trying to put it together as a rpm and perhaps and get it approved for Fedora.
I have created the following spec file available here:
It compiles without error. However, when I try to install the rpm using
$sudo dnf install ../RPMS/noarch/battray-2.2-1.fc24.noarch.rpm
Last metadata expiration check: 0:15:05 ago on Mon Oct 3 08:21:04 2016.
Error: nothing provides /bin/python3 needed by battray-2.2-1.fc24.noarch
(try to add '--allowerasing' to command line to replace conflicting packages)
The addition of '--allowerasing' does not change anything other than to remove the suggestion.
Any suggestions as to what is wrong with my spec file?
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.
We have a CentOS 6 system that is running an LDAP server for users, groups,
and autofs maps. After applying updates to a couple of Fedora 23 systems and
rebooting, they could no longer get the autofs maps from the server.
After poking around a bit and turning on all the logging features in sssd, it
turns out that some of the LDAP objects that sssd is looking for in the autofs
maps have changed in v1.4.1. Since we are using the LDAP server to feed
systems other than Fedora, we can't change the name of the objects in the LDAP
server, and fortunately sssd helpfully told you want object names it was
looking for in the autofs maps, so after comparing before v1.4.1 and after
1.4.1, I was able to determine what names had changed. After adding the
following lines to /etc/sssd/sssd.conf in the "[domain/default]" section,
automounts are working again in Fedora 23:
ldap_autofs_map_object_class = automountMap
ldap_autofs_map_name = ou
ldap_autofs_entry_object_class = automount
ldap_autofs_entry_key = cn
ldap_autofs_entry_value = automountInformation
Mike Iglesias Email: iglesias(a)uci.edu
University of California, Irvine phone: 949-824-6926
Office of Information Technology FAX: 949-824-2270
I am wondering why since f23 the boot messages display stops at "switch
on f21 all thee messages are displayed...
UFR de mathématiques et informatique
Laboratoire CNRS MAP5, UMR 8145
Université Paris Descartes
45, rue des Saints Pères
F-75270 Paris Cedex 06
Tél. +33 (0)1 8394 5849
> On F25 x86_64 as user "fedora" with default environment I get:
> grep Cock application.html.erb
> Provider for the National Disability Insurance Trial Site in Kwinana/
> grep Cock *
> grep: *: No such file or directory
This behaviour generally means that the file is in a directory that is
readable but not searchable. But root does not have that restriction and
can expand the pattern.
I don't think this is normal but I will like to know if anyone is
experiencing high memory usage from gnome-shell, a week ago was the first
time I saw it and to be honest, I can't say it this is something recent of
if it has always been this memory hungry.
After having my laptop with Fedora 24 on for three days I can see that the
memory consumed by gnome-shell is over 2GB and a week ago it was consuming
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+
2028 eramirez 20 0 4281540 2.169g 92676 S 10.9 13.9 59:43.98
Is anyone experiencing this problem?
I can connect to ftp server but the listing fails if firewalld and iptables services
are running. Turning them off would make it work just fine?
Was able to save the iptables config file and after going thru it found the line
that is causing the issue on line 138?
-A INPUT -j REJECT --reject-with icmp-host-prohibited
If I comment out that line, and restart the iptables, the ftp connection and list
would work just fine. I'm not clear on what would be adding this line to the
iptables? Not sure if that rule should be there, and if so, why would it reject
the ftp listing? Had been working before I had upgraded lab machines to
Michael D. Setzer II - Computer Science Instructor
Guam Community College Computer Center
Guam - Where America's Day Begins
G4L Disk Imaging Project maintainer
Number of Seti Units Returned: 19,471
Processing time: 32 years, 290 days, 12 hours, 58 minutes
(Total Hours: 287,489)
ABC 16613838.513356 | EINSTEIN 114625025.788695
ROSETTA 49468446.751024 | SETI 92870386.897682
I have a network printer (that I can see on the computer server browser at
When I try to use it, the jobs are not processed... - and I get the
* " the printer is not responding".*
I fund this information at link ;
All jobs are "The printer is not responding"
On networked printers, you should check that the name that CUPS uses as its
connection URI resolves to the printer's IP via DNS, e.g. If your printer's
connection looks like this:
then the hostname 'BRN_020554' needs to resolve to the printer's IP from
the server running CUPS
I understand what this means...
but I don't know how to accomplice the task*: *
* resolve that the IP from the server running CUPS *
Any help to do this will be appreciated.