Re: USB 2.0 with bogus Data Rate
On Mon, Mar 21, 2005 at 11:42:40PM +, Carlos Silva aka|Danger_Man| wrote: Julian Elischer wrote: Carlos Silva aka|Danger_Man| wrote: Hi hackers, I have a little problem with my external disk drive, my data transfer rate is 1.000MB/s. I have USB 2.0 so the rate is larger, right? Somebody has an idea how to enlarge the rate? the data rate is bogus because it is printed by the scsi/cam code which doesn't know about USB speeds. This has been improved in 6.x and may flow back to 5.4.. in the meantime, ignore that number and use dd if=/dev/da0 of=/dev/null bs=64k to see what your rate really is.. Here is the rate: osiris# dd if=/dev/da0 of=/dev/null bs=64k ^C16+0 records in 16+0 records out 1048576 bytes transferred in 14.741515 secs (71131 bytes/sec) osiris# Are you shure that the device is really a high speed one? USB 2.0 doesn't explizitly mean this. In the list below it looks like the device is handled by an VIA uhci controller - that is definitivley full speed only. usbdevs -v will show you details about the current detection. Moreover VIA controllers are known to cause problems. But it's even much too slow for full speed. There must be something elese - e.g. an IRQ problem. The best choise would be to replace the controller with an NEC based one. osiris# dmesg | grep usb dmesg | grep da0 usb0: Intel 82371AB/EB (PIIX4) USB controller on uhci0 usb0: USB revision 1.0 usb1: VIA 83C572 USB controller on uhci1 usb1: USB revision 1.0 usb2: VIA 83C572 USB controller on uhci2 usb2: USB revision 1.0 ehci_pci_attach: companion usb1 ehci_pci_attach: companion usb2 usb3: EHCI version 0.95 usb3: companion controllers, 2 ports each: usb1 usb2 usb3: EHCI (generic) USB 2.0 controller on ehci0 usb3: USB revision 2.0 GEOM: create disk da0 dp=0xc2d96850 da0 at umass-sim0 bus 0 target 0 lun 0 da0: USB 2.0 Storage Device 0100 Fixed Direct Access SCSI-0 device da0: 1.000MB/s transfers da0: 190782MB (390721968 512 byte sectors: 255H 63S/T 24321C) osiris# osiris# usbdevs addr 1: UHCI root hub, Intel addr 1: UHCI root hub, VIA addr 1: UHCI root hub, VIA addr 2: USB 2.0 Storage Device, Acer Labs addr 1: EHCI root hub, (0x1106) osiris# osiris# camcontrol devlist USB 2.0 Storage Device 0100 at scbus0 target 0 lun 0 (da0,pass0) osiris# -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC detected, but won't DHCP or configure
On Tue, 22 Mar 2005 17:30, Andrew Robinson wrote: thanks for the suggestion! I tried that and it didn't seem to change anything: the relevant output of pciconf -lv is still Try if_rl.ko/rl0 -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C pgpA2Fl9ZlCjn.pgp Description: PGP signature
Re: USB 2.0 with bogus Data Rate
Bernd Walter writes: On Mon, Mar 21, 2005 at 11:42:40PM +, Carlos Silva aka|Danger_Man| wrote: Here is the rate: osiris# dd if=/dev/da0 of=/dev/null bs=64k ^C16+0 records in 16+0 records out 1048576 bytes transferred in 14.741515 secs (71131 bytes/sec) osiris# Are you shure that the device is really a high speed one? USB 2.0 doesn't explizitly mean this. In the list below it looks like the device is handled by an VIA uhci controller - that is definitivley full speed only. usbdevs -v will show you details about the current detection. Moreover VIA controllers are known to cause problems. But it's even much too slow for full speed. There must be something elese - e.g. an IRQ problem. The best choise would be to replace the controller with an NEC based one. Could also be a setting in the BIOS. Mine lets you choose between USB 1 and USB 2 speeds for the EHCI controller. I have: ehci0: VIA VT6202 USB 2.0 controller --- Gary Jennejohn / garyj[at]jennejohn.org gj[at]freebsd.org garyj[at]denx.de ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: USB 2.0 with bogus Data Rate
On Tue, Mar 22, 2005 at 10:13:57AM +0100, Gary Jennejohn wrote: Bernd Walter writes: On Mon, Mar 21, 2005 at 11:42:40PM +, Carlos Silva aka|Danger_Man| wrote: Here is the rate: osiris# dd if=/dev/da0 of=/dev/null bs=64k ^C16+0 records in 16+0 records out 1048576 bytes transferred in 14.741515 secs (71131 bytes/sec) osiris# Are you shure that the device is really a high speed one? USB 2.0 doesn't explizitly mean this. In the list below it looks like the device is handled by an VIA uhci controller - that is definitivley full speed only. usbdevs -v will show you details about the current detection. Moreover VIA controllers are known to cause problems. But it's even much too slow for full speed. There must be something elese - e.g. an IRQ problem. The best choise would be to replace the controller with an NEC based one. Could also be a setting in the BIOS. Mine lets you choose between USB 1 and USB 2 speeds for the EHCI controller. The ehci can only do high-speed and the uhci companion only full and low speed. The BIOS is broken if it speaks about full (or low) speed on EHCI. I have: ehci0: VIA VT6202 USB 2.0 controller Yes - but you device is not attached to your ehci controller. -- B.Walter BWCThttp://www.bwct.de [EMAIL PROTECTED] [EMAIL PROTECTED] ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC detected, but won't DHCP or configure
Dan, thanks for your suggestion. I have now tried that, and, sadly, it does not change the output of pciconf or ifconfig. So, to sum up my understanding: the OS seems to detect the NIC correctly, but does not load the drivers. The NIC should be covered by the re drivers. What ought I do next? I would appreciate any further advice or thoughts. Thanks, Andrew On Tue, 22 Mar 2005 17:30, Andrew Robinson wrote: thanks for the suggestion! I tried that and it didn't seem to change anything: the relevant output of pciconf -lv is still Try if_rl.ko/rl0 -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au The nice thing about standards is that there are so many of them to choose from. -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC detected, but won't DHCP or configure
Daniel O'Connor [EMAIL PROTECTED] writes:
On Tue, 22 Mar 2005 17:30, Andrew Robinson wrote:
thanks for the suggestion! I tried that and it didn't seem to change
anything: the relevant output of pciconf -lv is still
Try if_rl.ko/rl0
No, if_rl will not attach to 8169 cards.
Andrew, it seems you have a chip revision which isn't currently
supported. Try applying the attached patch, and see if loading
if_re.ko results in something like this:
re_probe(): vid 10ec did 8169 hwrev 0080
the first two numbers should be exactly as shown, but the last number
should be different; let me know what it is.
DES
--
Dag-Erling Smørgrav - [EMAIL PROTECTED]
Index: sys/dev/re/if_re.c
===
RCS file: /home/ncvs/src/sys/dev/re/if_re.c,v
retrieving revision 1.42
diff -u -p -r1.42 if_re.c
--- sys/dev/re/if_re.c 13 Mar 2005 01:54:41 - 1.42
+++ sys/dev/re/if_re.c 22 Mar 2005 18:09:34 -
@@ -819,6 +819,7 @@ re_probe(dev)
t = re_devs;
sc = device_get_softc(dev);
+ hwrev = 0;
while (t-rl_name != NULL) {
if ((pci_get_vendor(dev) == t-rl_vid)
(pci_get_device(dev) == t-rl_did)) {
@@ -847,6 +848,9 @@ re_probe(dev)
}
t++;
}
+ if (hwrev != 0)
+ printf(%s(): vid %04x did %04x hwrev %08x\n, __func__,
+ pci_get_vendor(dev), pci_get_device(dev), hwrev);
return (ENXIO);
}
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC detected, but won't DHCP or configure
On Mon, Mar 21, 2005 at 11:00:57PM -0800, Andrew Robinson wrote: Hi Jason, thanks for the suggestion! I tried that and it didn't seem to change anything: the relevant output of pciconf -lv is still [EMAIL PROTECTED]:3:0:class=0x02 card=0x09001558 chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' class= network subclass = ethernet Can you give us the output of pciconf -r pci10:3:0 0:0xff ? Joerg ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC detected, but won't DHCP or configure.
thanks for the suggestion! I tried that and it didn't seem to change anything: the relevant output of pciconf -lv is still [EMAIL PROTECTED]:3:0: class=0x02 card=0x09001558 chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' class= network subclass = ethernet Andrew, it seems you have a chip revision which isn't currently supported. Try applying the attached patch, and see if loading if_re.ko results in something like this: Interestingly, i encountered the very same behaviour as explained by Andrew, with a side note: it works sometimes for me. Despite the fact that my ethernet seems correctly handled (ifconfig shows the 're' entry), almost all the time i boot on my notebook (D480V) the state of the media is no carrier. So, all services which use the network fail inevitably: dhcp, ntpdate and ntpd. In order to be able to use the network, sometimes i just must wait some dozens minutes... or totally reboot and wait some other dozens minutes. I can't remember of one boot wich went without a hitch. Here is some (useful?) information: # uname -a FreeBSD boboche.thilelli.net 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #1: Tue Mar 22 20:04:20 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BOBOCHE i386 # pciconf -lv [EMAIL PROTECTED]:10:0: class=0x02 card=0x08001558 chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' class= network subclass = ethernet = note: it seems that the chip revision, which is the same as Andrew, is recognized here. # pciconf -r pci0:10:0 0:0xff 816910ec 02b00017 0210 4004 2001 e8005000 08001558 00dc 40200113 f7c20001 # ifconfig re0 re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING inet6 fe80::290:f5ff:fe28:cfa8%re0 prefixlen 64 scopeid 0x2 inet 192.168.1.20 netmask 0xff00 broadcast 192.168.1.255 ether 00:90:f5:28:cf:a8 media: Ethernet autoselect (100baseTX full-duplex) status: active = note: here is the status after waiting a long time or rebooting. As for Andrew, it may be noted that i do not encountered this kind of problem under GNU/Linux (i tested with two live CDs), NetBSD (1.6.2 through 2.0.2) and Windows Server 2003 Ent-Ed. Because of this particular problem, i can't currently use this machine in a usefull way, so any advice are welcome too ! :) It wants to say i can test and apply patch(es) without problem, if any. Thanks, -- -jpeg. ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
ip_reass() - possibly incorrect goto
Hi hackers, I am looking at the ip_reass() routine. In case of the 1st fragment we create the reassembly queue. After the queue has been inserted in the hash bucket, the if () code does a goto inserted. Should this be changed to goto done instead? Any code that is executed for the 1st fragment, like frag per packet limiting and complete reassembly are not valid. Am I mistaken? br vijay ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Process Control
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, Someone recently asked me the best way to control the number of foreground and background processes a user can run on the system. I had a prod around in a few places and pondered the concept of getting the kernel to limit the max number of processes in login.conf, as sort of sub-limits of maxproc. The best way I could come up with doing this kernel-side is by watching a process' P_CONTROLT flag when a process is created (or tries to fork). If the process had the flag, I assumed it to be foreground, if not, background. If anyone has any other suggestions on how to distinguish fg/bg apart, or on the concept in general, I'd appreciate some feedback! Regards, Alan - -- Alan 'alz' Milford email: [EMAIL PROTECTED] -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.0 (MingW32) iD8DBQFCQIdjq48BsFB7OgARAm5JAKDARB5qlommW29kibdG3M9fvGNs4gCgiFbt hEJfK4ZmzP9UgCTXtQsV8Vo= =o7lf -END PGP SIGNATURE- ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC detected, but won't DHCP or configure.
On Tue, 22 Mar 2005, Julien Gabel wrote: thanks for the suggestion! I tried that and it didn't seem to change anything: the relevant output of pciconf -lv is still [EMAIL PROTECTED]:3:0: class=0x02 card=0x09001558 chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' class= network subclass = ethernet Andrew, it seems you have a chip revision which isn't currently supported. Try applying the attached patch, and see if loading if_re.ko results in something like this: Interestingly, i encountered the very same behaviour as explained by Andrew, with a side note: it works sometimes for me. Despite the fact that my ethernet seems correctly handled (ifconfig shows the 're' entry), almost all the time i boot on my notebook (D480V) the state of the media is no carrier. So, all services which use the network fail inevitably: dhcp, ntpdate and ntpd. In order to be able to use the network, sometimes i just must wait some dozens minutes... or totally reboot and wait some other dozens minutes. I can't remember of one boot wich went without a hitch. Here is some (useful?) information: # uname -a FreeBSD boboche.thilelli.net 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #1: Tue Mar 22 20:04:20 CET 2005 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/BOBOCHE i386 # pciconf -lv [EMAIL PROTECTED]:10:0: class=0x02 card=0x08001558 chip=0x816910ec rev=0x10 hdr=0x00 vendor = 'Realtek Semiconductor' device = 'RTL8169 Gigabit Ethernet Adapter' class= network subclass = ethernet = note: it seems that the chip revision, which is the same as Andrew, is recognized here. # pciconf -r pci0:10:0 0:0xff 816910ec 02b00017 0210 4004 2001 e8005000 08001558 00dc 40200113 f7c20001 # ifconfig re0 re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500 options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING inet6 fe80::290:f5ff:fe28:cfa8%re0 prefixlen 64 scopeid 0x2 inet 192.168.1.20 netmask 0xff00 broadcast 192.168.1.255 ether 00:90:f5:28:cf:a8 media: Ethernet autoselect (100baseTX full-duplex) status: active = note: here is the status after waiting a long time or rebooting. As for Andrew, it may be noted that i do not encountered this kind of problem under GNU/Linux (i tested with two live CDs), NetBSD (1.6.2 through 2.0.2) and Windows Server 2003 Ent-Ed. Because of this particular problem, i can't currently use this machine in a usefull way, so any advice are welcome too ! :) It wants to say i can test and apply patch(es) without problem, if any. Thanks, Could you try this patch: http://lists.freebsd.org/pipermail/freebsd-stable/2005-March/013107.html -- Oleg. === Oleg Bulyzhin -- OBUL-RIPN -- OBUL-RIPE -- [EMAIL PROTECTED] === ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC detected, but won't DHCP or configure.
thanks for the suggestion! I tried that and it didn't seem to change
anything: the relevant output of pciconf -lv is still
[EMAIL PROTECTED]:3:0: class=0x02 card=0x09001558 chip=0x816910ec
rev=0x10 hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8169 Gigabit Ethernet Adapter'
class= network
subclass = ethernet
Andrew, it seems you have a chip revision which isn't currently
supported. Try applying the attached patch, and see if loading
if_re.ko results in something like this:
Interestingly, i encountered the very same behaviour as explained by
Andrew, with a side note: it works sometimes for me. Despite the fact
that my ethernet seems correctly handled (ifconfig shows the 're'
entry),
almost all the time i boot on my notebook (D480V) the state of the
media is no carrier. So, all services which use the network fail
inevitably: dhcp, ntpdate and ntpd.
In order to be able to use the network, sometimes i just must wait some
dozens minutes... or totally reboot and wait some other dozens minutes.
I can't remember of one boot wich went without a hitch.
Here is some (useful?) information:
# uname -a
FreeBSD boboche.thilelli.net 5.4-PRERELEASE FreeBSD 5.4-PRERELEASE #1:
Tue Mar 22 20:04:20 CET 2005
[EMAIL PROTECTED]:/usr/obj/usr/src/sys/BOBOCHE i386
# pciconf -lv
[EMAIL PROTECTED]:10:0: class=0x02 card=0x08001558 chip=0x816910ec
rev=0x10
hdr=0x00
vendor = 'Realtek Semiconductor'
device = 'RTL8169 Gigabit Ethernet Adapter'
class= network
subclass = ethernet
= note: it seems that the chip revision, which is the same as Andrew,
is recognized here.
# pciconf -r pci0:10:0 0:0xff
816910ec 02b00017 0210 4004
2001 e8005000
08001558
00dc 40200113
f7c20001
# ifconfig re0
re0: flags=8843UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST mtu 1500
options=1bRXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING
inet6 fe80::290:f5ff:fe28:cfa8%re0 prefixlen 64 scopeid 0x2
inet 192.168.1.20 netmask 0xff00 broadcast 192.168.1.255
ether 00:90:f5:28:cf:a8
media: Ethernet autoselect (100baseTX full-duplex)
status: active
= note: here is the status after waiting a long time or rebooting.
As for Andrew, it may be noted that i do not encountered this kind of
problem under GNU/Linux (i tested with two live CDs), NetBSD (1.6.2
through 2.0.2) and Windows Server 2003 Ent-Ed.
Because of this particular problem, i can't currently use this machine
in a usefull way, so any advice are welcome too ! :) It wants to say i
can test and apply patch(es) without problem, if any.
Could you try this patch:
http://lists.freebsd.org/pipermail/freebsd-stable/2005-March/013107.html
Ok, just tried it. As i can see there is some improvement here, along
with the following comments:
1/ When rebooting the system, the bad/old behaviour seems to happen
systematically;
2/ When powered-off then powered-on, the behaviour seems to be more
correct. Nevertheless, i encountered the old problem more than
*one* time... roughly ~40% to 50% :(
--
-jpeg.
___
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to [EMAIL PROTECTED]
firewall
Hi all, I just build a web server, with apache-2.xx w/ php and mysql-1.4xx. How to configure firewall in my web server ? Must I download kernel source and recompile ? If I must download kernel source, where I can found it ? I'm using freebsd 5.1-RELEASE. Thanks. == Sanata Dharma University http://www.usd.ac.id -- ICT Supported by BAPSI USD http://www.bapsi.usd.ac.id == ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
NIC 1 gigabit
Hi, I have trouble with my NIC. I'm using Server Mainboard Intel (I forgot the model), there is 2 NICs; the one is 100Mbps other is 1 gigabit. I use this for my web server with freeBSD 5.1-RELEASE. NIC 1 gigabit is not detected and recognised neither by freeBSD the other is fine and working. What should I do ? Should I recompile kernel ? And How ? Sorry, my English is bad. Thanks. == Sanata Dharma University http://www.usd.ac.id -- ICT Supported by BAPSI USD http://www.bapsi.usd.ac.id == ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: NIC 1 gigabit
On Wed, Mar 23, 2005 at 07:47:22AM +0700, [EMAIL PROTECTED] wrote: Hi, I have trouble with my NIC. I'm using Server Mainboard Intel (I forgot the model), there is 2 NICs; the one is 100Mbps other is 1 gigabit. I use this for my web server with freeBSD 5.1-RELEASE. NIC 1 gigabit is not detected and recognised neither by freeBSD the other is fine and working. What should I do ? Should I recompile kernel ? And How ? First, you need upgrade to at least 5.3-RELEASE, possiably 5.3-STABLE. 5.1 is truly ancient. -- Brooks -- Any statement of the form X is the one, true Y is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 pgpcV0TrOGLDT.pgp Description: PGP signature
Re: firewall
Thanks alot. On 2005-03-23 07:41, [EMAIL PROTECTED] wrote: I just build a web server, with apache-2.xx w/ php and mysql-1.4xx. How to configure firewall in my web server ? - The FreeBSD Handbook has several sections devoted to firewalls and their configuration. - The archives of this mailing list have dozens of suggestions for firewall setups. - The articles at O'Reilly's OnLamp site have even more firewall setup examples. You can find a lot of material online. Just start looking at pages like: http://www.FreeBSD.org/docs.html http://lists.freebsd.org/pipermail/freebsd-questions/ http://www.onlamp.com/pub/ct/13 http://ezine.daemonnews.org/ Must I download kernel source and recompile ? Nope. If I must download kernel source, where I can found it ? The sources for the FreeBSD base system are in /usr/src. The kernel is under /usr/src/sys. The Handbook contains detailed instructions about rebuilding everything from source. I'm using freebsd 5.1-RELEASE. Thanks. That's a very old and experimental release of the 5.X branch. You should really consider upgrading to (or reinstalling with) a more recent 5.X release. 5.3-RELEASE is teh latest release that is available on the mirrors right now, and if you can wait a few days, 5.4-RELEASE is scheduled to be out sometime during the first days of April. - Giorgos == Sanata Dharma University http://www.usd.ac.id -- ICT Supported by BAPSI USD http://www.bapsi.usd.ac.id == ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Process Control
On Tue, 2005-Mar-22 21:00:19 +, Alan Milford wrote: [Separate per-user limits on foreground and background processes] The best way I could come up with doing this kernel-side is by watching a process' P_CONTROLT flag when a process is created (or tries to fork). If the process had the flag, I assumed it to be foreground, if not, background. I don't think this will achieve what you want. Consider a standard user shell which will be in the foreground attached to the user's TTY (and therefore have P_CONTROLT). Irrespective of whether the user enters foo or foo, the shell will call fork(). The just controls what happens _after_ the fork() - if it's a foreground process then the child exec's foo and the parent (normally]) just does a wait(). If it's a background process, the child will (normally) juggle termios TTIN and TTOUT parameters then exec foo, the parent writes another prompt and waits for input. Unfortunately, I can't think of any way to do what you want. -- Peter Jeremy ___ freebsd-hackers@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to [EMAIL PROTECTED]
