Limiting background processes
Hi there, I know there's a way to limit the number of background processes a user may have, but i don't know how that's done. Anybody who can enlighten me with a few tips? I tried using login classes (with login.conf i believe), but that doesn't work (and i don't know why, there aren't any errors relating to it). I already chmod 700 nohup, and made it root.wheel. Tips would be greatly appreciated! Rick Jansen ** Server Administrator [Linux - FreeBSD] www.tweakers.net - www.fokzine.net E-Mail: [EMAIL PROTECTED] - [EMAIL PROTECTED] ICQ: 37416519 ** To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: libc shlib version
In message [EMAIL PROTECTED] "David O'Brien" writes: : On Wed, Nov 15, 2000 at 12:21:02AM -0700, Warner Losh wrote: : Maybe I'm crazy, but can't we find and kill the API change that caused : this and back it out for 4.x? I suspect it was the per interface stat : changes in the network code, but I could very well be wrong. : : We should not, the API change was one allowed by the way we bump shared : version numbers. Rather than deal with this single case, we should : consider the issue in the large. This makes it harder to deal with mixed environments, but not hugely so. I'm thinking that if is just one thing, and it happened recently, it would be less pain to back out the API change. We're not supposed to have major libc bumps in -stable. If it is a bunch of changes or if the changes happened a long time ago, then we have no choice but to fix the problem now and how the "window" isn't too disruptive. : These sorts of things aren't supposed to impact libc at all. Do we : know which one caused the problem? : : Sure they are. We can add syscalls,etc al. utill the cows come home and : not bump the version number. I can't tell, but it looks like we're agreeing here. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: XDM/CHOOSER Xfree 401 and Xfree 336 on FBSD 4.2
On Wed, 15 Nov 2000, O. Hartmann wrote: :configuration situations the exact same behaviour! So I should exclude any :trouble with IPFW or similar filtering tools or anything with autheticatio :schemes. : :Well, I never read anything about problems or changes in how XDM works in :XFree86 4.0.1, so if there is anybody out here who has some information :he's very welcome to email me. I remember that there was a problem with some early XFree 4.x, where the default configuration was broken. I don't remember the details, but it's possible to fix by recompiling with the correct options. It was discussed here, or maybe in -chat. Maybe this jogs someone's memory? David To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: XDM/CHOOSER Xfree 401 and Xfree 336 on FBSD 4.2
On Wed, 15 Nov 2000, David Scheidt wrote: :On Wed, 15 Nov 2000, O. Hartmann wrote: : ::configuration situations the exact same behaviour! So I should exclude any ::trouble with IPFW or similar filtering tools or anything with autheticatio ::schemes. :: ::Well, I never read anything about problems or changes in how XDM works in ::XFree86 4.0.1, so if there is anybody out here who has some information ::he's very welcome to email me. : :I remember that there was a problem with some early XFree 4.x, where the :default configuration was broken. I don't remember the details, but it's :possible to fix by recompiling with the correct options. It was discussed :here, or maybe in -chat. Maybe this jogs someone's memory? : :David : : : : Thank you for responding. Well, I recompiled XFree 4.0.1_8 with the Makefile that was obtained by the ports collection, so if there were known bugs or problems targeting only the right way to compile it should be fixed by the make routines offered by the ports collection. For the first I downgraded my XDM serving host to XFree 3.3.6, hope to get rid of the older XFree in the future when this nasty and hair-costing problem has been solved. Thank you :-) Wishes, Oliver - MfG O. Hartmann --- [EMAIL PROTECTED] Klimadatenserver-Abteilung des IPA IT Netz- und Systembetreuung Johannes Gutenberg-Universitaet Mainz Becherweg 21 D-55099 Mainz BRD/Germany Tel: +496131/3924662 FAX: +496131/3923532 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
ditching tconv from usr.bin
Hey there -- usr.bin/tconv relies on lib/libmytinfo, which was killed off almost a year ago. Should usr.bin/tconv get killed off as well or no? - ryan To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: Any outstanding soft-updates or FFS bugs (matching this description)?
As I recall, Donn Miller wrote: Matt Dillon wrote: I've had filesystems blow up under test when filling a parition with softupdates turned on. The most recent time was last weekend while I was testing low-memory stuff. It would be nice if the softupdates code (or maybe other kernel code could do this) could detect when filesystem space is running low, and kick into some "fail-safe" mode. For example, when the free space drops below 15%, softupdates could automatically shut itself off, and then turn itself back on when the free space rises above 20% (hysteresis). I might be wrong, but some of the studies I've done leave me suspecting that your filesystem is probably in better shape with softupdates on when the filesystem runs dry, barring bugs of course. -crl -- Chad R. Larson (CRL15) 602-953-1392 Brother, can you paradigm? [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] DCF, Inc. - 14623 North 49th Place, Scottsdale, Arizona 85254-2207 To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
error on install
on install with 4.1.1 , 4.1, and 4.2 ,not 3.x I get ata1: Device timeout.. resetting.. done Over and over again its a fujitsu 4.2 gig hdd and a via motherboard I have tried everything also with my sr trio3d 365 i was wondering if it was fixed up in 4.x so it can actually do above 800x600 Be great if you could get back to me... thanx sincerly Ramon.
Re: Limiting background processes
* Rick Jansen [EMAIL PROTECTED] [001115 12:50] wrote: Hi there, I know there's a way to limit the number of background processes a user may have, but i don't know how that's done. Anybody who can enlighten me with a few tips? I tried using login classes (with login.conf i believe), but that doesn't work (and i don't know why, there aren't any errors relating to it). I already chmod 700 nohup, and made it root.wheel. Tips would be greatly appreciated! You need to run cap_mkdb /etc/login.conf after editing login.conf. -Alfred To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: ftpd from BSDI 4.1
On Wed, Nov 15, 2000 at 12:52:39PM +, Kaltashkin Eugene wrote: When in FreeBSD be ftpd server from BSDI 4.1 ? Him support virtual servers and very customisable config. It is my intention to change FreeBSD's ftpd to the Luke M. version in NetBSD. Luke's ftpd provides a very, very nice alternative to the wu-ftpd one (unless you like security vulnerabilities). Switching also moves us to one very much maintained and shares more code with our BSD brotheren where where is no reason not to. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: libc shlib version
Can we just stop arguing about this and bump the frickin' numbers already? Time is running out! - jordan On Wed, Nov 15, 2000 at 12:21:02AM -0700, Warner Losh wrote: Maybe I'm crazy, but can't we find and kill the API change that caused this and back it out for 4.x? I suspect it was the per interface stat changes in the network code, but I could very well be wrong. We should not, the API change was one allowed by the way we bump shared version numbers. Rather than deal with this single case, we should consider the issue in the large. These sorts of things aren't supposed to impact libc at all. Do we know which one caused the problem? Sure they are. We can add syscalls,etc al. utill the cows come home and not bump the version number. -- -- David ([EMAIL PROTECTED]) GNU is Not Unix / Linux Is Not UniX To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: libc shlib version
In message [EMAIL PROTECTED] Jordan Hubbard writes: : Can we just stop arguing about this and bump the frickin' numbers already? : Time is running out! That's your call as RE. Since we don't know what change caused it, that's likely the least bad thing we can do. Warner To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
Re: mergemaster wishlist
An awesome piece of work. I have but two wishes, saving one for later :) 1) a log 2) an option that says in effect overwrite all the files I did not modify. My reasons for wanting (2) are I was updating a 4.1 system I had just installed from the CD to 4.2-BETA and nothing really had changed, certainly not the periodic scripts and defaults. I have not looked at this enough to have an opinion on how to determine/tag "unmodified" files. Editing something in the file would be fine with me. The log would serve to address an "oop's. On Wed, 23 Aug 2000, Doug Barton wrote: On Tue, 22 Aug 2000, Francisco Reyes wrote: On Thu, 17 Aug 2000 23:53:51 -0700, Doug Barton wrote: Yes, thanks. This is close to the top of the wishlist. Where is the wishlist for mergemaster? Is it kept anywhere visible? Define visible. :) I have a project list of things that people have asked for that I plan to include. It's not very long, but see below. I have one thing I have been thinking on giving it a try in a few weeks. Changing mergemaster to indicate files to be either ignored or copied. Kind of an exception file. Haven't looked at the code so I don't know how difficult it would be. [cut] To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
