Re: Kernel not booting....Immediate crash
On Thu, 7 Nov 2002, Sidcarter wrote: > Hi Folks, > > I just did a cvsup and installed a kernel. I have been trying this from the past > few days with the same error. I am copying this by hand, since it crashes > immediately after loading the modules. The same is there with 4.7-STABLE > The error message is here > > > Booting [/boot/kernel/kernel]... > /boot/kernel/acpi.ko text=0x30dbc data=0x1a58+0xb48 syms=[0x4+0x5770+0x4+0x73b9/]\ > > Fatal trap 12: page fault while in vm86 mode > fault virtual address = 0x9fdc8 > fault code= user read, page not present > instruction pointer = 0xf000:0x145e > stack pointer = 0x0:0xfb4 > frame pointer = 0x0:0xfca > code segment = base 0x0, limit 0x0, type 0x0 > DPL 0, pres 0, def32, gran 0 > processsor eflags = interrupt enabled, resume, vm86, IOPL=0 > current process = 0 () > kernel: type 12 trap, code=0 > Stopped at0x145e: addb%al,0(%eax) > db> t > (null)(eee06c0,1,e820,fee06c0,9775a707) at 0x145e > db> > > > uname -a > > FreeBSD calvin 5.0-CURRENT FreeBSD 5.0-CURRENT #0: Thu Oct 24 15:46:54 IST 2002 >root@calvin:/usr/obj/usr/src/sys/HOGWARTS i386 > > Any idea what could be wrong ? > -- Dmitry Valdov mailto:dv@;dv.ru CCNP To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Dolby Digital soundcards
Hi! Is support of 5.1 soundcards like Creative Audigy Player will be there in the near future? -- Dmitry Valdov mailto:[EMAIL PROTECTED] CCNP To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: PAM(?) breaks r* and ftpd
Hi! This commit fixes the problem in -stable kris2001/02/17 21:31:16 PST Modified files:(Branch: RELENG_4) lib/libc/net res_init.c Log: My previous commit was overenthusiastic - it does not apply to RELENG_4. Pointy hat to:kris Revision ChangesPath 1.19.2.4 +1 -3 src/lib/libc/net/res_init.c Dmitry. On Thu, 1 Mar 2001, Dmitry Valdov wrote: > Date: Thu, 1 Mar 2001 16:55:18 +0300 (MSK) > From: Dmitry Valdov <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED], [EMAIL PROTECTED] > Subject: PAM(?) breaks r* and ftpd > > Hi! > > Try to make an .rhosts file and rlogin to fresh RELENG_4 or -CURRENT branch. > > rlogin -l dv xxx.xxx.xxx.xxx > > No output until Ctrl-C is pressed > > ftpd is also broken: > > > ftp xxx.xxx.xxx.xxx > Connected to xxx.xxx.xxx.xxx > > also no output. > > ftpd works only when connecting to localhost: > > > ftp localhost > Connected to localhost. > 220 xxx.xxx.xxx.xxx FTP server (Version 6.00LS) ready. > Name (localhost:dv): > > after recompiling with -DNOPAM ftpd starts working. > > -current & -stable as one month before works. > > Dmitry. > > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
PAM(?) breaks r* and ftpd
Hi! Try to make an .rhosts file and rlogin to fresh RELENG_4 or -CURRENT branch. > rlogin -l dv xxx.xxx.xxx.xxx No output until Ctrl-C is pressed ftpd is also broken: > ftp xxx.xxx.xxx.xxx Connected to xxx.xxx.xxx.xxx also no output. ftpd works only when connecting to localhost: > ftp localhost Connected to localhost. 220 xxx.xxx.xxx.xxx FTP server (Version 6.00LS) ready. Name (localhost:dv): after recompiling with -DNOPAM ftpd starts working. -current & -stable as one month before works. Dmitry. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
licq after crt* change
Hi! licq doesn't work since crt* change.. (coredumps) Any workaround? (recompile if licq & qt doesn't help). /usr/ports/net/licq Dmitry. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
rl driver problem in -current
Hi! There is a problem in rl's driver in recent -current kernel. ... rl0: Realtek rl0: couldn't map memory kernel trap 12 with interrupts disabled -current kernel from 20 Oct 2000 works fine. I know I should provide more info about trap, but I can't cut'n'paste boot messages. What information _exactly_ needed to fix it? Dmitry. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
fsck in -current
Hello! fsck tries to run fsck_msdos for MSDOS partition, but there is no fsck_msdos in -current. Also fsck(8) says: SEE ALSO mount(8), fstab(5), fsck_msdos(8), fsck_ffs(8) ... > man fsck_msdos No manual entry for fsck_msdos > Dmitry. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: newfs/fsck problem (bad superblocks)
Hi! I've seen the same problem. And I've lost all content of my second hd. After newfs fsck can't check fs with the same diagnostic. Dmitry. On Sat, 21 Oct 2000, John W. De Boskey wrote: > Date: Sat, 21 Oct 2000 21:16:56 -0700 > From: "John W. De Boskey" <[EMAIL PROTECTED]> > To: [EMAIL PROTECTED] > Cc: Peter Wemm <[EMAIL PROTECTED]> > Subject: newfs/fsck problem (bad superblocks) > > Hi, > >I posted a question concerning fsck yesterday. A number of > people replied with the 'bad harddisk' comment. > >I have followed up some more on the problem, and can now > reproduce it on different filesystems. > >Below, I umount my /usr/obj, newfs it, mount it, unmount > it, and then fsck it. The fsck complains about a bad superblock. > Also, do not remotely reboot after this if the newly newfs'd > filesystem is automounted in /etc/fstab. The boot process > will hang waiting for fsck to be run manually. > >Example: > > + > %umount /usr/obj > %newfs /dev/ccd0a > Warning: 1616 sector(s) in last cylinder unallocated > /dev/ccd0a: 672 sectors in 1628 cylinders of 1 tracks, 4096 sectors > 3255.2MB in 102 cyl groups (16 c/g, 32.00MB/g, 4096 i/g) > super-block backups (for fsck -b #) at: > 32, 65568, 131104, 196640, 262176, 327712, 393248, 458784, 524320, 589856, > 655392, 720928, 786464, 852000, 917536, 983072, 1048608, 1114144, 1179680, > 1245216, 1310752, 1376288, 1441824, 1507360, 1572896, 1638432, 1703968, > 1769504, 1835040, 1900576, 1966112, 2031648, 2097184, 2162720, 2228256, > 2293792, 2359328, 2424864, 2490400, 2555936, 2621472, 2687008, 2752544, > 2818080, 2883616, 2949152, 3014688, 3080224, 3145760, 3211296, 3276832, > 3342368, 3407904, 3473440, 3538976, 3604512, 3670048, 3735584, 3801120, > 3866656, 3932192, 3997728, 4063264, 4128800, 4194336, 4259872, 4325408, > 4390944, 4456480, 4522016, 4587552, 4653088, 4718624, 4784160, 4849696, > 4915232, 4980768, 5046304, 5111840, 5177376, 5242912, 5308448, 5373984, > 5439520, 5505056, 5570592, 5636128, 5701664, 5767200, 5832736, 5898272, > 5963808, 6029344, 6094880, 6160416, 6225952, 6291488, 6357024, 6422560, > 6488096, 6553632, 6619168 > %mount /dev/ccd0a /usr/obj > %df -m /usr/obj > Filesystem 1M-blocks UsedAvail Capacity Mounted on > /dev/ccd0a 32010 2944 0%/usr/obj > %umount /usr/obj > %/sbin/fsck -y /dev/ccd0a > ** /dev/ccd0a > BAD SUPER BLOCK: VALUES IN SUPER BLOCK DISAGREE WITH THOSE IN FIRST ALTERNATE > > LOOK FOR ALTERNATE SUPERBLOCKS? yes > > USING ALTERNATE SUPERBLOCK AT 32 > ** Last Mounted on > ** Phase 1 - Check Blocks and Sizes > ** Phase 2 - Check Pathnames > ** Phase 3 - Check Connectivity > ** Phase 4 - Check Reference Counts > ** Phase 5 - Check Cyl groups > 1 files, 1 used, 1638914 free (18 frags, 204862 blocks, 0.0% fragmentation) > > UPDATE STANDARD SUPERBLOCK? yes > > > * FILE SYSTEM WAS MODIFIED * > % > + > > > > I am wondering about the following patch : > > peter 2000/10/16 17:41:37 PDT > > Modified files: > sbin/newfs mkfs.c > Log: > Implement simple write combining for newfs - this is particularly useful > for large scsi disks with WCE = 0. This yields around a 7 times speedup > on elapsed newfs time on test disks here. 64k clusters seems to be the > sweet spot for scsi disks using our present drivers. > > Revision ChangesPath > 1.30 +38 -1 src/sbin/newfs/mkfs.c > > > > I will revert this patch tomorrow. I also wonder if this is related > to the 'make release' problems. > > > Comments welcome. > > -John > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
ftp client bug
Hi! There is a problem in ftp client in all FreeBSD versions. It isn't dangerous but probably should be fixed. > uname -a FreeBSD work.dv.ru 5.0-CURRENT FreeBSD 5.0-CURRENT #6: Thu Jun 22 19:41:50 MSD 2000 [EMAIL PROTECTED]:/usr/src/sys/compile/WORK i386 > ftp localhost Connected to localhost. 220 work.dv.ru FTP server (Version 6.00LS) ready. Name (localhost:dv): 331 Password required for dv. Password: 230 User dv logged in. Remote system type is UNIX. Using binary mode to transfer files. ftp> site %s Segmentation fault (core dumped) > Dmitry. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: sysinstall mistake
Hello!
Sure, I'm tracking.
There are two lines with USA_RESIDENT. First used when creating new
make.conf. Second one is used when updating existing make.conf.
You've fixed it only in first case.
Please look at the patch properly :)
Dmitry.
On Thu, 2 Mar 2000, Jordan K. Hubbard wrote:
> Date: Thu, 02 Mar 2000 03:12:09 -0800
> From: "Jordan K. Hubbard" <[EMAIL PROTECTED]>
> To: Dmitry Valdov <[EMAIL PROTECTED]>
> Cc: [EMAIL PROTECTED], [EMAIL PROTECTED]
> Subject: Re: sysinstall mistake
>
> You need to track -current. I fixed this on:
>
> revision 1.155
> date: 2000/02/24 08:28:06; author: jkh; state: Exp; lines: +2 -2
> Do USA_RESIDENT properly.
>
>
> > Hi!
> >
> > Please commit it:
> >
> >
> >
> > --- release/sysinstall/config.c.old Tue Feb 29 23:56:47 2000
> > +++ release/sysinstall/config.c Tue Feb 29 23:56:55 2000
> > @@ -386,7 +386,7 @@
> > if (!strncmp(lines[i], "USA_RESIDENT", 12)) {
> > free(lines[i]);
> > lines[i] = malloc(21); /* big enough */
> > - sprintf(lines[i], "USA_RESIDENT=\"%s\"\n", USAResident ? "YES"
> : "NO");
> > + sprintf(lines[i], "USA_RESIDENT=%s\n", USAResident ? "YES" : "N
> O");
> > }
> > }
> > }
> >
> >
> >
>
>
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
is inet6 preffered when resolving names?
Hi! Is it right behavior to try IPv6 address first? work# telnet localhost Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. [...] Only solution for it is to comment out in /etc/hosts: ::1localhost localhost.my.domain myname.my.domain I've tried to switch 127.0.0.1 and ::1 is /etc/hosts but there was no effect. Dmitry. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
sysinstall mistake
Hi!
Please commit it:
--- release/sysinstall/config.c.old Tue Feb 29 23:56:47 2000
+++ release/sysinstall/config.c Tue Feb 29 23:56:55 2000
@@ -386,7 +386,7 @@
if (!strncmp(lines[i], "USA_RESIDENT", 12)) {
free(lines[i]);
lines[i] = malloc(21); /* big enough */
- sprintf(lines[i], "USA_RESIDENT=\"%s\"\n", USAResident ? "YES" : "NO");
+ sprintf(lines[i], "USA_RESIDENT=%s\n", USAResident ? "YES" : "NO");
}
}
}
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
ftp passive modem is on by defaut?
Hello! Why ftp passive mode is on by default? > ftp localhost Connected to localhost. 220 home.dv.ru FTP server (Version 6.00LS) ready. Name (localhost:dv): 331 Password required for dv. Password: 230 User dv logged in. Remote system type is UNIX. Using binary mode to transfer files. ftp> get /bin/sh /tmp/qqq local: /tmp/qqq remote: /bin/sh 229 Entering Extended Passive Mode (|||1049|) [...] ftp> passive Passive mode off. ftp> Manpage shows: passive Toggle passive mode. If passive mode is turned on (default is off), [...] Dmitry. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: options COMPAT_LINUX makes kernel fail to compile
Should it be described in /usr/src/UPDATING ? On Tue, 4 Jan 2000, Matthew Dillon wrote: > Date: Tue, 4 Jan 2000 14:38:45 -0800 (PST) > From: Matthew Dillon <[EMAIL PROTECTED]> > To: Dmitry Valdov <[EMAIL PROTECTED]> > Cc: [EMAIL PROTECTED] > Subject: Re: options COMPAT_LINUX makes kernel fail to compile > > > :Hi! > : > :With option COMPAT_LINUX (which present in LINT) make depend fails with: > :cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes > :-Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual > :-fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include > :-D_KERNEL -include opt_global.h -elf -fno-builtin > :-mpreferred-stack-boundary=2 -UKERNEL -o linux_genassym.o -c > :../../i386/linux/linux_genassym.c > :genassym -o linux_assym.h linux_genassym.o > :genassym:No such file or directory > :*** Error code 1 > : > :Dmitry. > > genassym is now in /usr/src/usr.bin/genassym, compile and install that > then try your make again. The one in the local compile directory is > still being used for other things (and not compatible with the one > in /usr/src/usr.bin/ ) > > -Matt > Matthew Dillon > <[EMAIL PROTECTED]> > > > To Unsubscribe: send mail to [EMAIL PROTECTED] > with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
options COMPAT_LINUX makes kernel fail to compile
Hi! With option COMPAT_LINUX (which present in LINT) make depend fails with: cc -O -Wall -Wredundant-decls -Wnested-externs -Wstrict-prototypes -Wmissing-prototypes -Wpointer-arith -Winline -Wcast-qual -fformat-extensions -ansi -nostdinc -I- -I. -I../.. -I../../../include -D_KERNEL -include opt_global.h -elf -fno-builtin -mpreferred-stack-boundary=2 -UKERNEL -o linux_genassym.o -c ../../i386/linux/linux_genassym.c genassym -o linux_assym.h linux_genassym.o genassym:No such file or directory *** Error code 1 Dmitry. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: DoS from local users (fwd)
On Sat, 10 Apr 1999, Matthew Dillon wrote: > Date: Sat, 10 Apr 1999 14:08:41 -0700 (PDT) > From: Matthew Dillon > To: Kevin Day > Cc: ha...@rah.star-gate.com, d...@dv.ru, gr...@unixhelp.org, > freebsd-current@FreeBSD.ORG > Subject: Re: DoS from local users (fwd) > > A user-run CGI is another example. Say you have a web server which runs > CGI's under a user id. If the web site is loaded down and the user > happens > to run a log processing script, execs of the user's CGIs might slow down > due to the load balancing 'feature'. The web server may now wind up in > the > situation where it is forking CGIs faster then it can retire them. > Leading > to another cascade failure. > Make it configurable then... Dmitry. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DoS from local users (fwd)
On Sat, 10 Apr 1999, Brian Feldman wrote: > Date: Sat, 10 Apr 1999 14:07:27 -0400 (EDT) > From: Brian Feldman > To: Dmitry Valdov > Cc: freebsd-current@freebsd.org > Subject: Re: DoS from local users (fwd) > > On Sat, 10 Apr 1999, Dmitry Valdov wrote: > > > Hi! > > > > Once again - HOW I can limit CPU usage by *kernel* ? > > Also, I've just tried set maxprocesses 5. > > And it helpless. > > With 5 processes limit user was able to slow down P2-450 computer. > > Switching between windows in X was VERY slow. Mouse movements was slow down > > too. > > CPU states: 32.3% user, 0.0% nice, 67.2% system, 0.0% interrupt, 0.5% > > idle > > > > Please, just try it. > > If you want to preempt other tasks, make that user's tasks niced!! > Have You tried it? Please try. I think that it's a system call problem. When (pipe, exec, or something? I dont' known how it syscall named) is called many times at the same time, kernel starts using all CPU time while performing these syscalls. It's just my opinion. But I see no way to prevent users from overloading system by kernel. (hmmm, if not to limit maxproc to one or two ;- > > > > > > On Sat, 10 Apr 1999, Brian Feldman wrote: > > > > > Date: Sat, 10 Apr 1999 09:29:19 -0400 (EDT) > > > From: Brian Feldman > > > To: Dmitry Valdov > > > Cc: ch...@calldei.com, freebsd-current@FreeBSD.ORG, > > > freebsd-questi...@freebsd.org > > > Subject: Re: DoS from local users (fwd) > > > > > > On Sat, 10 Apr 1999, Dmitry Valdov wrote: > > > > > > > > > > > > > > > On Sat, 10 Apr 1999, Chris Costello wrote: > > > > > > > > > Date: Sat, 10 Apr 1999 02:05:33 -0500 > > > > > From: Chris Costello > > > > > Reply-To: ch...@calldei.com > > > > > To: Dmitry Valdov > > > > > Cc: freebsd-current@FreeBSD.ORG, freebsd-questi...@freebsd.org > > > > > Subject: Re: DoS from local users (fwd) > > > > > > > > > > On Sat, Apr 10, 1999, Dmitry Valdov wrote: > > > > > > >You typically want to set a restriction as to how many > > > > > > > processes a user can spawn. This is done by editing > > > > > > > /etc/login.conf and changing the user's login class, see the man > > > > > > > page for 'login.conf'. > > > > > > > > > > > > > > > > > > > I'm about CPU usage, not about many processes. > > > > > > See: > > > > > > CPU states: 17.8% user, 0.0% nice, 81.7% system, 0.5% interrupt, > > > > > > 0.0% > > > > > > idle > > > > > > on any (tested on P2-45) machine. > > > > > > > > > > > > CPU is used by SYSTEM, not by USER. So I can't restrict it with > > > > > > login.conf > > > > > > And load average can be up to 20-40 :( > > > > > > > > > > > > Please don't redirect me to -questions, it's a kernel problem, not > > > > > > just > > > > > > config. > > > > > > > > > >How is it a kernel problem? It's a forkbomb. It spawns many > > > > > processes. You can also limit CPU usage with login.conf, I > > > > > believe. > > > > > > > > Hmm. How I can limit CPU usage by SYSTEM? See top's output below. > > > > > > > > Dmitry. > > > > > > > > PS. I've just tried it. And I'm right - CPU usage limit can't help. > > > > > > > > > > So? Processes that run a while go down in priority [McKusick95 I believe, > > > THE > > > book] so they are preempted easily. Look in top and see if they're all at > > > the top of the list. I bet they're not! Also, you can set per-user > > > niceness > > > levels, and why are you being so liberal giving a standard LUSER 32 > > > processes? > > > This is a system administration problem. > > > > > > > > > > > > > > > To Unsubscribe: send mail to majord...@freebsd.org > > > > with "unsubscribe freebsd-current" in the body of the message > > > > > > > > > > Brian Feldman_ __ ___ ___ ___ ___ > > > gr...@unixhelp.org_ __ ___ | _ ) __| \ > > > FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | > > > http://www.freebsd.org _ |___/___/___/ > > > > > > > > > > > > Brian Feldman_ __ ___ ___ ___ ___ > gr...@unixhelp.org_ __ ___ | _ ) __| \ > FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | > http://www.freebsd.org _ |___/___/___/ > > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DoS from local users (fwd)
Hi! Once again - HOW I can limit CPU usage by *kernel* ? Also, I've just tried set maxprocesses 5. And it helpless. With 5 processes limit user was able to slow down P2-450 computer. Switching between windows in X was VERY slow. Mouse movements was slow down too. CPU states: 32.3% user, 0.0% nice, 67.2% system, 0.0% interrupt, 0.5% idle Please, just try it. On Sat, 10 Apr 1999, Brian Feldman wrote: > Date: Sat, 10 Apr 1999 09:29:19 -0400 (EDT) > From: Brian Feldman > To: Dmitry Valdov > Cc: ch...@calldei.com, freebsd-current@FreeBSD.ORG, > freebsd-questi...@freebsd.org > Subject: Re: DoS from local users (fwd) > > On Sat, 10 Apr 1999, Dmitry Valdov wrote: > > > > > > > On Sat, 10 Apr 1999, Chris Costello wrote: > > > > > Date: Sat, 10 Apr 1999 02:05:33 -0500 > > > From: Chris Costello > > > Reply-To: ch...@calldei.com > > > To: Dmitry Valdov > > > Cc: freebsd-current@FreeBSD.ORG, freebsd-questi...@freebsd.org > > > Subject: Re: DoS from local users (fwd) > > > > > > On Sat, Apr 10, 1999, Dmitry Valdov wrote: > > > > >You typically want to set a restriction as to how many > > > > > processes a user can spawn. This is done by editing > > > > > /etc/login.conf and changing the user's login class, see the man > > > > > page for 'login.conf'. > > > > > > > > > > > > > I'm about CPU usage, not about many processes. > > > > See: > > > > CPU states: 17.8% user, 0.0% nice, 81.7% system, 0.5% interrupt, 0.0% > > > > idle > > > > on any (tested on P2-45) machine. > > > > > > > > CPU is used by SYSTEM, not by USER. So I can't restrict it with > > > > login.conf > > > > And load average can be up to 20-40 :( > > > > > > > > Please don't redirect me to -questions, it's a kernel problem, not just > > > > config. > > > > > >How is it a kernel problem? It's a forkbomb. It spawns many > > > processes. You can also limit CPU usage with login.conf, I > > > believe. > > > > Hmm. How I can limit CPU usage by SYSTEM? See top's output below. > > > > Dmitry. > > > > PS. I've just tried it. And I'm right - CPU usage limit can't help. > > > > So? Processes that run a while go down in priority [McKusick95 I believe, THE > book] so they are preempted easily. Look in top and see if they're all at > the top of the list. I bet they're not! Also, you can set per-user niceness > levels, and why are you being so liberal giving a standard LUSER 32 processes? > This is a system administration problem. > > > > > > > To Unsubscribe: send mail to majord...@freebsd.org > > with "unsubscribe freebsd-current" in the body of the message > > > > Brian Feldman_ __ ___ ___ ___ ___ > gr...@unixhelp.org_ __ ___ | _ ) __| \ > FreeBSD: The Power to Serve! _ __ | _ \__ \ |) | > http://www.freebsd.org _ |___/___/___/ > > To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DoS from local users (fwd)
On Sat, 10 Apr 1999, Chris Costello wrote: > Date: Sat, 10 Apr 1999 02:05:33 -0500 > From: Chris Costello > Reply-To: ch...@calldei.com > To: Dmitry Valdov > Cc: freebsd-current@FreeBSD.ORG, freebsd-questi...@freebsd.org > Subject: Re: DoS from local users (fwd) > > On Sat, Apr 10, 1999, Dmitry Valdov wrote: > > >You typically want to set a restriction as to how many > > > processes a user can spawn. This is done by editing > > > /etc/login.conf and changing the user's login class, see the man > > > page for 'login.conf'. > > > > > > > I'm about CPU usage, not about many processes. > > See: > > CPU states: 17.8% user, 0.0% nice, 81.7% system, 0.5% interrupt, 0.0% > > idle > > on any (tested on P2-45) machine. > > > > CPU is used by SYSTEM, not by USER. So I can't restrict it with login.conf > > And load average can be up to 20-40 :( > > > > Please don't redirect me to -questions, it's a kernel problem, not just > > config. > >How is it a kernel problem? It's a forkbomb. It spawns many > processes. You can also limit CPU usage with login.conf, I > believe. Hmm. How I can limit CPU usage by SYSTEM? See top's output below. Dmitry. PS. I've just tried it. And I'm right - CPU usage limit can't help. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
pipe DOS
Hi! Just tested it with user who has maxproc 32 set. Here is the results: last pid: 58668; load averages: 27.06, 19.94, 12.67up 0+09:40:46 11:06:11 77 processes: 31 running, 46 sleeping CPU states: 14.9% user, 0.0% nice, 85.1% system, 0.0% interrupt, 0.0% idle Mem: 26M Active, 12M Inact, 10M Wired, 5392K Cache, 2371K Buf, 7440K Free Swap: 130M Total, 130M Free CPU usage limit also will not fix it because CPU time is used by system :( Dmitry. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DoS from local users (fwd)
On Fri, 9 Apr 1999, Chris Costello wrote: > Date: Fri, 9 Apr 1999 18:30:31 -0500 > From: Chris Costello > Reply-To: ch...@calldei.com > To: Dmitry Valdov > Cc: freebsd-questi...@freebsd.org > Subject: Re: DoS from local users > > On Fri, Apr 9, 1999, Dmitry Valdov wrote: > > Hi! > > > > Try it: > > > > cat > qqq > > echo $$ > > echo ~/qqq|~/qqq|~/qqq|~/qqq|~/qqq > > > > Ctrl-D > > > > ./qqq > > > > Is there Any way to fix it? > >You typically want to set a restriction as to how many > processes a user can spawn. This is done by editing > /etc/login.conf and changing the user's login class, see the man > page for 'login.conf'. > I'm about CPU usage, not about many processes. See: CPU states: 17.8% user, 0.0% nice, 81.7% system, 0.5% interrupt, 0.0% idle on any (tested on P2-45) machine. CPU is used by SYSTEM, not by USER. So I can't restrict it with login.conf And load average can be up to 20-40 :( Please don't redirect me to -questions, it's a kernel problem, not just config. Dmitry. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: DoS from local users
On Sat, 10 Apr 1999, oZZ!!! wrote: > Date: Sat, 10 Apr 1999 02:27:22 +0400 (MSD) > From: oZZ!!! > To: Dmitry Valdov > Cc: freebsd-current@FreeBSD.ORG > Subject: Re: DoS from local users > > > > Hi! > > Try it: > > > > cat > qqq > > echo $$ > > echo ~/qqq|~/qqq|~/qqq|~/qqq|~/qqq > > > > Ctrl-D > > > > ./qqq > > > > Is there Any way to fix it? > > > > Dmitry. > > > % cat > qqq > echo $$ > echo ~/qqq|~/qqq|~/qqq|~/qqq|~/qqq > % ./qqq > ./qqq: Permission denied. > % > & what fix? > Oh, sorry, chmod 555 qqq. I was drunk a little :) Machine will have load average about 20-40. Dmitry. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
DoS from local users
Hi! Try it: cat > qqq echo $$ echo ~/qqq|~/qqq|~/qqq|~/qqq|~/qqq Ctrl-D ./qqq Is there Any way to fix it? Dmitry. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
-stable problem
Hi! Why this happens? > telnet x.x.x.x nntp Trying x.x.x.x... Connected to x.x.x.x. Escape character is '^]'. assertion "nsegs == 2" failed: file "/usr/src/libexec/rtld-elf/map_object.c", line 158 Connection closed by foreign host. Also machine closes any connection to any port. It happens not too often, but happens. It running 3.1-STABLE. And INN 2.3-current. Dmitry. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
RE: disk quota overriding
On Wed, 17 Mar 1999, Ladavac Marino wrote: > Date: Wed, 17 Mar 1999 14:37:32 +0100 > From: Ladavac Marino > To: 'Dmitry Valdov' , freebsd-current@freebsd.org, > freebsd-secur...@freebsd.org > Subject: RE: disk quota overriding > > > -Original Message- > > From: Dmitry Valdov [SMTP:d...@dv.ru] > > Sent: Wednesday, March 17, 1999 1:37 PM > > To: freebsd-current@freebsd.org; freebsd-secur...@freebsd.org > > Subject:Re: disk quota overriding > > > > Hi! > > > > > > I think that there is only one way to fix it - it's to disable making > > *hard*links to directory with mode 1777. > > > [ML] But only if the quotas have been turned on. Sure. What Core Team thinks about it? Dmitry. To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
Re: disk quota overriding
Hi!
I think that there is only one way to fix it - it's to disable making
*hard*links to directory with mode 1777.
On Wed, 17 Mar 1999, Dmitry Valdov wrote:
> Date: Wed, 17 Mar 1999 14:42:46 +0300 (MSK)
> From: Dmitry Valdov
> To: freebsd-current@freebsd.org, freebsd-secur...@freebsd.org
> Subject: disk quota overriding
>
> Hi!
>
> There is a way to overflow / filesystem even is quota is enabled.
>
> Just make many hard links (for example /bin/sh) to /tmp/
>
> for ($q=0;$q<10;$q++){
> system ("ln /bin/sh /tmp/ln$q");
> }
>
> Because /tmp directory usually owned by root that why quotas has no effect.
> *Directory* size of /tmp can be grown up to available space on / filesystem.
>
> Any way to fix it?
>
> Dmitry.
>
>
>
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: disk quota overriding
On Wed, 17 Mar 1999, Fernando Schapachnik wrote:
> Date: Wed, 17 Mar 1999 08:50:50 -0300 (GMT)
> From: Fernando Schapachnik
> To: Dmitry Valdov
> Cc: freebsd-current@FreeBSD.ORG, freebsd-secur...@freebsd.org
> Subject: Re: disk quota overriding
>
> Are you aware that, due to nature of hardlinks the only extra space is
> same that for an empty file? Due to this, how many empty files do you
> think it takes to eat the whole space of / ?
No. Many empty files can be controlled by INODE QUOTAS.
Hard links can't.
But I can create as many hard links as I need to eat up the whole space of
/...
>
> I'm I loosing something?
>
> Regards.
>
> En un mensaje anterior, Dmitry Valdov escribiС:
> > Hi!
> >
> > There is a way to overflow / filesystem even is quota is enabled.
> >
> > Just make many hard links (for example /bin/sh) to /tmp/
> >
> > for ($q=0;$q<10;$q++){
> > system ("ln /bin/sh /tmp/ln$q");
> > }
> >
> > Because /tmp directory usually owned by root that why quotas has no effect.
> > *Directory* size of /tmp can be grown up to available space on / filesystem.
> >
> > Any way to fix it?
>
>
> Fernando P. Schapachnik
> Administracion de la red
> VIA Net Works Argentina SA
>
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
Re: disk quota overriding
On Wed, 17 Mar 1999, Jay Tribick wrote:
> Date: Wed, 17 Mar 1999 11:49:32 +
> From: Jay Tribick
> To: Dmitry Valdov
> Cc: freebsd-current@FreeBSD.ORG, freebsd-secur...@freebsd.org
> Subject: Re: disk quota overriding
>
> Hi
>
> > There is a way to overflow / filesystem even is quota is enabled.
> >
> > Just make many hard links (for example /bin/sh) to /tmp/
> >
> > for ($q=0;$q<10;$q++){
> > system ("ln /bin/sh /tmp/ln$q");
> > }
> >
> > Because /tmp directory usually owned by root that why quotas has no effect.
> > *Directory* size of /tmp can be grown up to available space on / filesystem.
> >
> > Any way to fix it?
>
> Haven't tested this, but are you sure it fills the filesystem up -
> all a hard link is, is a file with the same inode as the
> original file (correct me if I'm wrong) - therefore it
> doesn't actually use any space other than that required
> to store the file entry.
^
Yes. But /tmp dir is under root filesystem. So *directory* size of /tmp can be
grown up to free space on /. Which will result 0 bytes free on / :) All
available space will be used to store directory entries.
Dmitry.
PS. Sorry for my english.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
disk quota overriding
Hi!
There is a way to overflow / filesystem even is quota is enabled.
Just make many hard links (for example /bin/sh) to /tmp/
for ($q=0;$q<10;$q++){
system ("ln /bin/sh /tmp/ln$q");
}
Because /tmp directory usually owned by root that why quotas has no effect.
*Directory* size of /tmp can be grown up to available space on / filesystem.
Any way to fix it?
Dmitry.
To Unsubscribe: send mail to majord...@freebsd.org
with "unsubscribe freebsd-current" in the body of the message
