LinuxQuestions.org
Help answer threads with 0 replies.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE
User Name
Password
SUSE / openSUSE This Forum is for the discussion of Suse Linux.

Notices


Reply
  Search this Thread
Old 01-23-2012, 09:57 AM   #1
petelogan
Member
 
Registered: Mar 2003
Location: Luxembourg
Distribution: SuSE 11.4
Posts: 74

Rep: Reputation: 15
CineLerra Shared Memory Patch


Cinelerra gives an irritating but not fatal notification that it wants the shared memory allocation in /proc/sys/kernel/shmmax increased to 0x7fffffff

Doing it by session works, but it should be possible to make the change permanent.

Google gave me this on a Gentoo forum but I have zapped two files of that name under Suse 12.1 and it still loads the default, so I assume it must be defined somewhere else in Suse.

http://forums.gentoo.org/viewtopic-t-792891.html

Does anyone know where the correct .conf file is that will enforce this change ??

Thank you for any help you can give, whether it be the answer, or suggestions where to look.

Pete
 
Old 02-18-2012, 05:25 AM   #2
unSpawn
Moderator
 
Registered: May 2001
Posts: 29,415
Blog Entries: 55

Rep: Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600Reputation: 3600
Quote:
Originally Posted by petelogan View Post
Does anyone know where the correct .conf file is that will enforce this change ??
/etc/sysctl.conf is the right place to have values survive reboots.
How did you test it did not stick or work?
Or maybe you didn't add the right line or the right way?

Code:
]$ su -l
CURVAL=($(/sbin/sysctl kernel.shmmax)); NEWVAL=$[${CURVAL[2]}*2]
sysctl -w kernel.shmmax=${NEWVAL}
echo "kernel.shmmax = $NEWVAL" >> /etc/sysctl.conf
# Test it (after reboot?):
grep -q $NEWVAL /proc/sys/kernel/shmmax && echo "set OK"

//NTLB
 
Old 02-20-2012, 09:39 AM   #3
petelogan
Member
 
Registered: Mar 2003
Location: Luxembourg
Distribution: SuSE 11.4
Posts: 74

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by unSpawn View Post
/etc/sysctl.conf is the right place to have values survive reboots.
How did you test it did not stick or work?
Or maybe you didn't add the right line or the right way?

Code:
]$ su -l
CURVAL=($(/sbin/sysctl kernel.shmmax)); NEWVAL=$[${CURVAL[2]}*2]
sysctl -w kernel.shmmax=${NEWVAL}
echo "kernel.shmmax = $NEWVAL" >> /etc/sysctl.conf
# Test it (after reboot?):
grep -q $NEWVAL /proc/sys/kernel/shmmax && echo "set OK"
//NTLB
Thanks very much. I'll give that a go tomorrow when I get a minute.

Thanks again.
 
  


Reply



Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
How to create a shared memory and some shared objects in linux? jeremy28 Programming 6 06-11-2010 05:21 AM
Linux shared memory segment access problem and x86 Virtual Memory layout. regmee Linux - Kernel 1 08-23-2008 12:11 AM
Difference between resident memory,shared memory and virtual memory in system monitor mathimca05 Linux - Newbie 1 11-11-2007 04:05 AM
Cinelerra Crashes While Rendering - malloc(): memory corruption uryagi Linux - Software 0 02-27-2006 02:07 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > SUSE / openSUSE

All times are GMT -5. The time now is 05:29 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration