[Koha] Koha Digest, Vol 82, Issue 20
Doug Dearden
dearden at sarsf.org
Thu Aug 16 03:09:21 NZST 2012
Hi Joel,
You are probably safe to get rid of some old system logs. I am using a different distro than you but I think these are in the same place. If I look in /var/log on my system, I see a number of files named syslog.N.gz (N being a number). These go back a few days. I believe at one point they were building up on my system and sucking down a lot of disk space, and I did something so they would automatically delete off after a week. Wish I could tell you what that was, I don't remember. Make sure you don't delete the current one named syslog, or the one named syslog.1 but you can probably get rid of older ones just to give you some wiggle room. You should take a look at syslog.1 to get an idea of what is being recorded in there. Mine are full of the cron job entries for Koha.
Something else that might help you is the "du" command. You can find some info about that here: http://www.codecoffee.com/tipsforlinux/articles/22.html or just do "man du" . I have used this in the past to find the directories that were particularly large, then figured out what was being stored there and if it was necessary.
Unfortunately I can't recommend anything else, as I don't know your system. Deleting the wrong file can cause havoc with Linux. Linux will even let you delete the entire file system with one command when you are logged in as root, so be careful. I would suggest you try for some more help on the Redhat forums.
Best,
Doug
-----Original Message-----
From: Joel Buleka [mailto:jbuleka at mra.gov.pg]
Sent: Tuesday, August 14, 2012 6:28 PM
To: Doug Dearden
Subject: RE: Koha Digest, Vol 82, Issue 20
Hi Doug
Below are currently mounted file systems:
/dev/mapper/VolGroup00-LogVol00 on / type ext3 (rw)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
devpts on /dev/pts type devpts (rw,gid=5,mode=620)
/dev/sda1 on /boot type ext3 (rw)
tmpfs on /dev/shm type tmpfs (rw)
none on /proc/sys/fs/binfmt_misc type binfmt_misc (rw)
sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw)
automount(pid2184) on /net type autofs
(rw,fd=4,pgrp=2184,minproto=2,maxproto=4)
-----Original Message-----
From: Doug Dearden [mailto:dearden at sarsf.org]
Sent: Wednesday, August 15, 2012 12:31 AM
To: Joel Buleka
Subject: RE: Koha Digest, Vol 82, Issue 20
100% used on your primary partition. Size 72G, Used 72G. You need to
free up some disk space or add some.
-----Original Message-----
From: Joel Buleka [mailto:jbuleka at mra.gov.pg]
Sent: Monday, August 13, 2012 7:30 PM
To: Doug Dearden
Subject: RE: Koha Digest, Vol 82, Issue 20
Hi Doug
below is the partion details
[root at libserver ~]# df -h
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/VolGroup00-LogVol00
72G 72G 0 100% /
/dev/sda1 99M 15M 80M 16% /boot
tmpfs 220M 0 220M 0% /dev/shm
Joel
-----Original Message-----
From: Doug Dearden [mailto:dearden at sarsf.org]
Sent: Tuesday, August 14, 2012 8:42 AM
To: Joel Buleka; koha at lists.katipo.co.nz
Subject: RE: Koha Digest, Vol 82, Issue 20
Hi Joel,
>From the command line do "df -h" .
It will show you the disk space used and what remains on each partition.
You are probably out of disk space.
Doug
-----Original Message-----
From: koha-bounces at lists.katipo.co.nz
[mailto:koha-bounces at lists.katipo.co.nz] On Behalf Of Joel Buleka
Sent: Monday, August 13, 2012 4:23 PM
To: koha at lists.katipo.co.nz
Subject: Re: [Koha] Koha Digest, Vol 82, Issue 20
Hi
We have Koha 2.2.9 running on Fedora 5, recently the MySQL database is
not starting up and the server is giving us no disk space error.
-----Original Message-----
From: koha-bounces at lists.katipo.co.nz
[mailto:koha-bounces at lists.katipo.co.nz] On Behalf Of
koha-request at lists.katipo.co.nz
Sent: Tuesday, August 14, 2012 8:16 AM
To: koha at lists.katipo.co.nz
Subject: Koha Digest, Vol 82, Issue 20
Send Koha mailing list submissions to
koha at lists.katipo.co.nz
To subscribe or unsubscribe via the World Wide Web, visit
http://lists.katipo.co.nz/mailman/listinfo/koha
or, via email, send a message with subject or body 'help' to
koha-request at lists.katipo.co.nz
You can reach the person managing the list at
koha-owner at lists.katipo.co.nz
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Koha digest..."
Today's Topics:
1. Re: Suggestion on Amazon wish-list look-ups (Liz Rea)
2. Re: Question on Z39.50 cross-format queries (Manos Petridis)
3. Why are our borrowers being restricted? (Tim Hannah)
4. help for debian partition for koha (ramverma)
5. Re: Why are our borrowers being restricted? (Jared Camins-Esakov)
6. Re: Why are our borrowers being restricted? (Chris Cormack)
7. Re: Why are our borrowers being restricted? (Tim Hannah)
----------------------------------------------------------------------
Message: 1
Date: Mon, 13 Aug 2012 09:22:13 -0500
From: Liz Rea <lrea at nekls.org>
To: Manos Petridis <egpetridis at yahoo.com>
Cc: "koha at lists.katipo.co.nz" <koha at lists.katipo.co.nz>
Subject: Re: [Koha] Suggestion on Amazon wish-list look-ups
Message-ID:
<CAKx1OdV3ZoE5=BH-UjKM4-1h=J+Z5YZ8U32=MK0WNzWFtiB=Mw at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
I added this as an enhancement request to bugs.koha-community.org - bug
8631.
Thanks for your idea!
Liz Rea
NEKLS
On Mon, Aug 13, 2012 at 2:10 AM, Manos Petridis
<egpetridis at yahoo.com>wrote:
> Ideas and suggestions for future development:
>
> Add the facility to look-up Amazon wish-lists and add their contents
> (conditionally if possible) as purchase suggestions.
> I don't know if I may be considered the norm, but have set-up several
> wish-lists myself in the various Amazon shops (US, UK, FR, IT, DE,
JP),
> roughly 8-12 lists per shop.
> It would therefore be useful to be able to paste the URLs of the
various
> lists to a window and have koha recurse/run through them, provide the
> aggregated result list for verification, and then add the selected
items as
> purchase suggestions to the library.
> I understand that this could be expanded to cover many other on-line
> shops, it's just that I'm a long-time Amazon customer and keep my
> wish-lists there.
>
> Thank you for your time and cnsideration
> Manos Petridis
> _______________________________________________
> Koha mailing list http://koha-community.org
> Koha at lists.katipo.co.nz
> http://lists.katipo.co.nz/mailman/listinfo/koha
>
--
Northeast Kansas Library System
lrea at nekls.org
785-838-4090
------------------------------
Message: 2
Date: Mon, 13 Aug 2012 12:36:22 -0700 (PDT)
From: Manos Petridis <egpetridis at yahoo.com>
To: "koha at lists.katipo.co.nz" <koha at lists.katipo.co.nz>
Subject: Re: [Koha] Question on Z39.50 cross-format queries
Message-ID:
<1344886582.13600.YahooMailNeo at web110606.mail.gq1.yahoo.com>
Content-Type: text/plain; charset=iso-8859-1
Sorry, seem to have replied by mistake to the poster and not to the
list.
>________________________________
> From: Manos Petridis <egpetridis at yahoo.com>
>To: BWS Johnson <abesottedphoenix at yahoo.com>
>Sent: Monday, August 13, 2012 3:24 PM
>Subject: Re: [Koha] Question on Z39.50 cross-format queries
>
>
>Thank you for your welcome Brooke, and for your prompt reply.
>?
>I do understand that my own installation can be either USMARC/MARC21 or
UNIMARC. What I was enquiring about is Z39.50 look-ups. Why I am
puzzled:
>?
>a) It it were simply a case of either/or, then why can?I select the
MARC flavour of the various Z39.50 origins set up at my installation?
What is the reason to let koha know of the MARC flavour/dialect, if it
not able to use the data that each server sends? There must be some
functionality behind the dropbox selections, even if it only defines the
query statement dialect.
>?
>b) From What I can see in the data presented (in the MARC form window)
it sometimes is just a matter of mapping. For example, it seems that?
>
>in SUTRS, information is stored in the following keys:
>Title:?????????????????????200
>Author:????????????????????700_a, 700_b, 701_a, 701_b...Editon
details????????????210
>Physical descrition:???????215
>DDC*:??????????????????????676_a
>DDC description:???????????676_9
>Subjects:??????????????????606
>
>in USMARC, information is stored in the following keys:
>Title:???????????????????? 245
>Author:????????????????????700
>Editon details???????????? 260
>Physical descrition:?????? 300
>DDC*:??????????????????????082 (revision and Category)
>Subjects:??????????????????650, 505 (fixed and free-form)
>LCCN:??????????????????????010
>?
>in UNIMARC, information is stored in the following keys:
>Title:???????????????????? 200
>Author:??????????????????? 700, 701Editon details?????????????210
>Physical descrition:???????215
>DDC*:??????????????????????676 (revision and
Category)Subjects:??????????????????606, 712 (fixed and free-form)
>?
>This is what I meant when I wrote "I understand that both standards
encode the same more-or-less information, differently" in my original
message. There are bound to be differences, sure, but I'm looking for
the gest in the MARC records, not the?details that frankly I don't even
know what they represent.?
>
>I understand that even the information retrieved via Z39.50 from
same-flavour installations, passes some kind of mapping, from the MARC
record form to the form of the various tables and fields/columns used by
the specific?software/implementation, koha in our case. I expect
therefore that it would be a matter of utilising the appropriate mapping
tables, as dictated by the MARC setting of each Z39.50 origin, so that
koha could make use of "foreign" MARC records.
>kind regards,
>Manos Petridis---
>?
>?
>?From: BWS Johnson <abesottedphoenix at yahoo.com>
>To: "koha at lists.katipo.co.nz" <koha at lists.katipo.co.nz>
>Sent: Monday, August 13, 2012 1:21 PM
>Subject: Re: [Koha] Question on Z39.50 cross-format queries
>
>
>>Salvete!
>>
>>??? Welcome to the Community. :)
>>
>>
>>> Question:
>>> I have selected USMARC/MARC21 as my installation's native format.
This
>>> serves nicely when I perform Z39.50 queries against many
USMARC/MARC21 sources.
>>> On the other hand, when I perform Z39.50 queries against UNIMARC
sources, I
>>> don't get properly formatted results even though I have set-up those
sources
>>> (origins)?as UNIMARC in koha.
>>>
>>> I understand that both standards encode the same more-or-less
information,
>>> differently.
>>> Therefore - if I understand correctly - koha would have to request
from an
>>> UNIMARC-only-capable source that they return UNIMARC-formatted
results, and koha
>>> would need to map them - if and as possible - to the native format
of my
>>> installation, i.e. USMARC/MARC21.
>>>
>>> Apparently this doesn't happen. Is it
normal?
>>
>>
>>??? That is very normal. MARC21/UNIMARC is an either or standard
selection. You may have MARC21 or you may have UNIMARC. To my knowledge,
you may not have both.
>>
>>??? That said, when this last came up, I can see the point of wanting
to be able to run both in parallel if you absolutely MUST have both.
Suggestions for how to do that are here:
>>
>>http://koha.1045719.n5.nabble.com/Software-error-td5114149.html
>>
>>Cheers,
>>Brooke
>>
>>_______________________________________________
>>Koha mailing list? http://koha-community.org
>>Koha at lists.katipo.co.nz
>>http://lists.katipo.co.nz/mailman/listinfo/koha
>>
>>
>>
>
>
------------------------------
Message: 3
Date: Mon, 13 Aug 2012 20:50:38 +0000
From: Tim Hannah <Tim.Hannah at minedu.govt.nz>
To: "'Koha at lists.katipo.co.nz'" <Koha at lists.katipo.co.nz>
Subject: [Koha] Why are our borrowers being restricted?
Message-ID:
<3BAA5789CE50AF49B9F46F32D69187590B9B7376 at akexc10.moe.govt.nz>
Content-Type: text/plain; charset="us-ascii"
On koha 3.6.4 borrowers with overdues are being restricted. We don't
want them to be restricted.
Restrictions are put in place about 5 minutes before emailed overdue
notices are received, so guessing it's the same process.
Overdue notice/status triggers Restrict column is unchecked.
Preference OversBlockCirc is set to Don't block
All fines are set to 0.00, MaxFine is set to 0.00. Maxoutstanding and
Noissuescharge is set to 100.00.
Anyone see any obvious preferences we may have missed that could be
causing this?
Cheers
Tim Hannah
------------------------------------------------------------------------
----
DISCLAIMER:
This e-mail (including attachments) may contain information which is
confidential or legally privileged and may not reflect the Ministry of
Education's view. The Ministry is not responsible for changes made to
this
email after we've sent it. If you have received this e-mail by mistake,
please
reply to the Ministry immediately and delete both messages.
Thank you.
------------------------------
Message: 4
Date: Sun, 12 Aug 2012 22:13:30 -0700 (PDT)
From: ramverma <ram.verma003 at gmail.com>
To: koha at lists.katipo.co.nz
Subject: [Koha] help for debian partition for koha
Message-ID: <1344834809976-5723168.post at n5.nabble.com>
Content-Type: text/plain; charset=us-ascii
Dear All,
I am new to Debian and Koha, Can you guide me for space allocation in
Debian
Partition?
I will be using only one operating System: Debian 6.0.5 (Squeeze); and
the
system is dedicated for Koha 3.8.3; Hard disk space is: 320 GB, RAM:
2GB
Could you please guide me for meaningful partitioning of Debian.
/(root) = ?
/boot =?
/usr =?
/var =?
/opt =?
/tmp =?
/backup for koha-data (manually created) =?
Thank You.
Ram.
--
View this message in context:
http://koha.1045719.n5.nabble.com/help-for-debian-partition-for-koha-tp5
723168.html
Sent from the Koha-general mailing list archive at Nabble.com.
------------------------------
Message: 5
Date: Mon, 13 Aug 2012 17:24:41 -0400
From: Jared Camins-Esakov <jcamins at cpbibliography.com>
To: Tim Hannah <Tim.Hannah at minedu.govt.nz>
Cc: "Koha at lists.katipo.co.nz" <Koha at lists.katipo.co.nz>
Subject: Re: [Koha] Why are our borrowers being restricted?
Message-ID:
<CALVDfQwWTAN56gq3028LXk5MzdgPAwAmD_uCAoV3bUr=7OZNsg at mail.gmail.com>
Content-Type: text/plain; charset=UTF-8
Tim,
Restrictions are put in place about 5 minutes before emailed overdue
> notices are received, so guessing it's the same process.
>
> Overdue notice/status triggers Restrict column is unchecked.
> Preference OversBlockCirc is set to Don't block
> All fines are set to 0.00, MaxFine is set to 0.00. Maxoutstanding and
> Noissuescharge is set to 100.00.
>
> Anyone see any obvious preferences we may have missed that could be
> causing this?
>
It's not exactly "obvious," but could you check the Overdue
notice/status
triggers again, and make sure that you either don't have overdue
triggers
for any libraries other than the default library, or that *none* of them
have the Restrict box checked?
Also, when you say "restricted," what is the exact message you are
getting
when you go to check out books to this patron? (or, if you are noticing
the
restriction in another context, where exactly do you notice the
restrictions)
Regards,
Jared
--
Jared Camins-Esakov
Bibliographer, C & P Bibliography Services, LLC
(phone) +1 (917) 727-3445
(e-mail) jcamins at cpbibliography.com
(web) http://www.cpbibliography.com/
------------------------------
Message: 6
Date: Tue, 14 Aug 2012 09:40:40 +1200
From: Chris Cormack <chrisc at catalyst.net.nz>
To: Jared Camins-Esakov <jcamins at cpbibliography.com>
Cc: "Koha at lists.katipo.co.nz" <Koha at lists.katipo.co.nz>
Subject: Re: [Koha] Why are our borrowers being restricted?
Message-ID: <20120813214040.GS7186 at rorohiko.wgtn.cat-it.co.nz>
Content-Type: text/plain; charset=us-ascii
* Jared Camins-Esakov (jcamins at cpbibliography.com) wrote:
> Tim,
>
> Restrictions are put in place about 5 minutes before emailed overdue
> > notices are received, so guessing it's the same process.
> >
> > Overdue notice/status triggers Restrict column is unchecked.
> > Preference OversBlockCirc is set to Don't block
> > All fines are set to 0.00, MaxFine is set to 0.00. Maxoutstanding
and
> > Noissuescharge is set to 100.00.
> >
> > Anyone see any obvious preferences we may have missed that could be
> > causing this?
> >
>
> It's not exactly "obvious," but could you check the Overdue
notice/status
> triggers again, and make sure that you either don't have overdue
triggers
> for any libraries other than the default library, or that *none* of
them
> have the Restrict box checked?
>
> Also, when you say "restricted," what is the exact message you are
getting
> when you go to check out books to this patron? (or, if you are
noticing the
> restriction in another context, where exactly do you notice the
> restrictions)
>
Ah ha!
Thank you Jared!
Tim, if you go to Overdue notice/status triggers and switch the
library drop down from All, to Ministry of Education.
I bet you have restrict switched on there.
Chris
--
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
------------------------------
Message: 7
Date: Mon, 13 Aug 2012 22:07:46 +0000
From: Tim Hannah <Tim.Hannah at minedu.govt.nz>
To: 'Chris Cormack' <chrisc at catalyst.net.nz>, Jared Camins-Esakov
<jcamins at cpbibliography.com>
Cc: "Koha at lists.katipo.co.nz" <Koha at lists.katipo.co.nz>
Subject: Re: [Koha] Why are our borrowers being restricted?
Message-ID:
<3BAA5789CE50AF49B9F46F32D69187590B9B741A at akexc10.moe.govt.nz>
Content-Type: text/plain; charset="us-ascii"
Ah, I feel slightly silly, but better for having asked.
Thanks Jared, (and Katrin & Chris). It's obvious, when you look at it
right.
Cheers
-----Original Message-----
From: Chris Cormack [mailto:chrisc at catalyst.net.nz]
Sent: Tuesday, 14 August 2012 9:41 a.m.
To: Jared Camins-Esakov
Cc: Tim Hannah; Koha at lists.katipo.co.nz
Subject: Re: [Koha] Why are our borrowers being restricted?
* Jared Camins-Esakov (jcamins at cpbibliography.com) wrote:
> Tim,
>
> Restrictions are put in place about 5 minutes before emailed overdue
> > notices are received, so guessing it's the same process.
> >
> > Overdue notice/status triggers Restrict column is unchecked.
> > Preference OversBlockCirc is set to Don't block
> > All fines are set to 0.00, MaxFine is set to 0.00. Maxoutstanding
and
> > Noissuescharge is set to 100.00.
> >
> > Anyone see any obvious preferences we may have missed that could be
> > causing this?
> >
>
> It's not exactly "obvious," but could you check the Overdue
notice/status
> triggers again, and make sure that you either don't have overdue
triggers
> for any libraries other than the default library, or that *none* of
them
> have the Restrict box checked?
>
> Also, when you say "restricted," what is the exact message you are
getting
> when you go to check out books to this patron? (or, if you are
noticing the
> restriction in another context, where exactly do you notice the
> restrictions)
>
Ah ha!
Thank you Jared!
Tim, if you go to Overdue notice/status triggers and switch the
library drop down from All, to Ministry of Education.
I bet you have restrict switched on there.
Chris
--
Chris Cormack
Catalyst IT Ltd.
+64 4 803 2238
PO Box 11-053, Manners St, Wellington 6142, New Zealand
------------------------------------------------------------------------
----
DISCLAIMER:
This e-mail (including attachments) may contain information which is
confidential or legally privileged and may not reflect the Ministry of
Education's view. The Ministry is not responsible for changes made to
this
email after we've sent it. If you have received this e-mail by mistake,
please
reply to the Ministry immediately and delete both messages.
Thank you.
------------------------------
_______________________________________________
Koha mailing list
Koha at lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha
End of Koha Digest, Vol 82, Issue 20
************************************
_______________________________________________
Koha mailing list http://koha-community.org
Koha at lists.katipo.co.nz
http://lists.katipo.co.nz/mailman/listinfo/koha
More information about the Koha
mailing list