Re: [jazzplusplus-devel] tex2rtf broken

[Pete S. <pst...@gm...>]

DM = D.B. Moore
DM> Just a question for both Pete & yourself
DM> (seeing as you're both on fedora)...

I think Kevin is using Mandriva.

DM> could you look at your /etc/security/limits.conf
DM> file and let me know if it contains any entries
DM> for your user account?

My Fedora box...
$ uname -a
Linux maggie.toyon.corp 2.6.26.6-79.fc9.x86_64 #1 SMP Fri Oct 17 
14:20:33 EDT 2008 x86_64 x86_64 x86_64 GNU/Linux

has the following entries

## Automatically appended by jack-audio-connection-kit
@jackuser - rtprio 20
@jackuser - memlock 4194304

## Automatically appended by jack-audio-connection-kit
@pulse-rt - rtprio 20
@pulse-rt - nice -20

So anything running in the jackuser group limits the maximum real-time 
priority to 20 and has a maximum locked-in-memory address space of 
4194304 KB.  Anything running as group pulse-rt has the same maximum 
real-time priority limit and a maximum nice priority allowed to raise to 
limit of -20.  The comments indicate this was automatically added by the 
jack package.


The Mandriva I'm running for Kevin...

$ uname -a
Linux localhost 2.6.22.19-desktop-2mdv #1 SMP Mon May 5 20:55:05 EDT 
2008 i686 AMD Athlon(tm) XP 2800+ GNU/Linux

has the following

*               -       rtprio           0
*               -       nice             0
@audio          -       rtprio           50
@audio          -       nice             -10

So the maximum nice priority allowed to raise to limit is 0 and the 
maximum real-time priority limit is 0 for all users and the group audio 
has different limits.

So no entries for my user account.

DM> (and what they read if existent) I've discovered there's a
DM> way to tune user & user run task priorities from this
DM> location, and am interested with what fedora policy here
DM> is -- on a Deb install there are no user entries.

Same for Mandriva and Fedora.  If you use the bash shell, I believe you 
can set some of this using ulimit in your .bash_profile.

<bash man page>
ulimit [-SHacdefilmnpqrstuvx [limit]]
   Provides control over the resources available to the  shell  and
   to  processes started by it, on systems that allow such control.
   The -H and -S options specify that the hard or soft limit is set
   for  the  given resource.  A hard limit cannot be increased once
   it is set; a soft limit may be increased up to the value of  the
   hard  limit.   If  neither -H nor -S is specified, both the soft
   and hard limits are set.  The value of limit can be a number  in
   the unit specified for the resource or one of the special values
   hard, soft, or unlimited,  which  stand  for  the  current  hard
   limit,  the  current soft limit, and no limit, respectively.  If
   limit is omitted, the current value of the  soft  limit  of  the
   resource  is  printed, unless the -H option is given.  When more
   than one resource is specified, the  limit  name  and  unit  are
   printed before the value.  Other options are interpreted as fol-
   lows:
   -a     All current limits are reported
   -c     The maximum size of core files created
   -d     The maximum size of a process’s data segment
   -e     The maximum scheduling priority ("nice")
   -f     The maximum size of files written by the  shell  and  its
          children
   -i     The maximum number of pending signals
   -l     The maximum size that may be locked into memory
   -m     The maximum resident set size (has no effect on Linux)
   -n     The maximum number of open file descriptors (most systems
          do not allow this value to be set)
   -p     The pipe size in 512-byte blocks (this may not be set)
   -q     The maximum number of bytes in POSIX message queues
   -r     The maximum real-time scheduling priority
   -s     The maximum stack size
   -t     The maximum amount of cpu time in seconds
   -u     The maximum number of processes  available  to  a  single
          user
   -v     The  maximum  amount  of  virtual memory available to the
          shell
   -x     The maximum number of file locks

   If limit is given, it is the new value of the specified resource
   (the -a option is display only).  If no option is given, then -f
   is assumed.  Values are in 1024-byte increments, except for  -t,
   which  is  in seconds, -p, which is in units of 512-byte blocks,
   and -n and -u, which are unscaled values.  The return status  is
   0  unless an invalid option or argument is supplied, or an error
   occurs while setting a new limit.
</bash man page>

I have developed on systems that limit the core dump size.  This 
prevented me from debugging a core dump.  i added the following lime to 
my .bash_profile to get a core dump...

#=========================================
# Allow core dump files of unlimited size.
#=========================================
ulimit -S -c unlimited > /dev/null 2>&1

HTH,
Pete