On Thu, Nov 13, 2003 at 02:45:18AM -0800, Terry Lambert wrote:
> > Why use pid files at all if you could be using a process supervisor instead?
>
> Who supervises the supervisor?
Heh. The supervisor should be small and robust, like init. Has init died on
you recently? Do you want to solve this pr
Daniel Ellard wrote:
> Can someone point me at some non-marketing documentation about
> hyperthreading on the latest Intel chips? I'm seeing some strange
> performance measurements and I would like to figure out what they
> mean.
Go out to Intel's web site's "developer" section, and look for
"SMT
Jose Kulalapnot <[EMAIL PROTECTED]> writes:
|tnx Vlad. im now running ymessenger. my id is
|buttmanizer. add me if u want.
|
I would, but your ID sounds scary :)
|
|
| --- Vlad Galu <[EMAIL PROTECTED]> wrote: > Vlad
|Galu <[EMAIL PROTECTED]> writes:
|>
|> |Jose Kulalapnot <[EMAIL PROTECTE
Jaromir Dolecek wrote:
> marius aamodt eriksen wrote:
> > in order to be able to preserve consistent semantics across poll,
> > select, and kqueue (EVFILT_READ), i propose the following change: on
> > EVFILT_READ, add an fflag NOTE_EOF which will return when the file
> > pointer *is* at the end of
tnx Vlad. im now running ymessenger. my id is
buttmanizer. add me if u want.
--- Vlad Galu <[EMAIL PROTECTED]> wrote: > Vlad
Galu <[EMAIL PROTECTED]> writes:
>
> |Jose Kulalapnot <[EMAIL PROTECTED]> writes:
> |
> ||my system is running 5.1 and i installed the
> latest
> ||ymessenger from the p
tnx Vlad. im now running ymessenger. my id is
buttmanizer. add me if u want.
--- Vlad Galu <[EMAIL PROTECTED]> wrote: > Vlad
Galu <[EMAIL PROTECTED]> writes:
>
> |Jose Kulalapnot <[EMAIL PROTECTED]> writes:
> |
> ||my system is running 5.1 and i installed the
> latest
> ||ymessenger from the p
Vlad Galu <[EMAIL PROTECTED]> writes:
|Jose Kulalapnot <[EMAIL PROTECTED]> writes:
|
||my system is running 5.1 and i installed the latest
||ymessenger from the ports. when i run it i get this
||message:
||
||/usr/libexec/ld-elf.so.1: Shared object "libintl.so.4"
|
| Reinstall gettext and e
> A PR might be a good idea. The basic details are that ACPI in 4.x needs
> to create a kernel process to service it's private taskqueue and then
> use this taskqueue instead of the system taskqueue to service events.
FYI: PR is kern/59248.
Andre
_
Jose Kulalapnot <[EMAIL PROTECTED]> writes:
|my system is running 5.1 and i installed the latest
|ymessenger from the ports. when i run it i get this
|message:
|
|/usr/libexec/ld-elf.so.1: Shared object "libintl.so.4"
Reinstall gettext and everything that depends on it from scratch.
|no
my system is running 5.1 and i installed the latest
ymessenger from the ports. when i run it i get this
message:
/usr/libexec/ld-elf.so.1: Shared object "libintl.so.4"
not found
how can i fix this?
Want to chat instantly w
* Terry Lambert <[EMAIL PROTECTED]> [20031113 11:46]:
> Jos Backus wrote:
> > On Mon, Oct 27, 2003 at 10:31:18AM -0500, Dan Langille wrote:
> > > 1 - write your PID immediately, and the file is chown root:wheel
> > > 2 - write your PID to /var/run/myapp/myapp.pid w
Perter Pentechv wrote
> Take a look at the kenv(1) utility - its source is in the
> src/usr.bin/kenv/kenv.c file.
Yes this does the job. But in a strange way... It starts at OID 0.3
(kern.environment) and appends small integers to it (0,1,2,3 etc). Why do it
so strange.. Why are the variable name
Jos Backus wrote:
> On Mon, Oct 27, 2003 at 10:31:18AM -0500, Dan Langille wrote:
> > If a process starts up and does a setuid, should it be writing the
> > PID file before or after the setuid?
> >
> > Two methods exists AFAIK:
> >
> > 1 - write your PID immediately, and the file is chown root:whee
> AFAIK yes for sockets, not for file descriptor (i.e. descriptor
> open to a file on filesystem). Would poll() give you read-availability
> event when on end of file on filesystem.
IIRC poll() is required to report that files are always readable.
(So tail -f can't use poll() to avoid looping.)
T
John Baldwin wrote:
Also, as someone else mentioned, setting 'machdep.cpu_idle_hlt=1' can
be useful on some HTT systems. However, p4's have a problem with their
interrupt routing that can leave the second CPU halted for a long time
if you do that.
I have a few quick questions... Searched on
>> I think the difference is in the default behavior. When you're at
>> EOF, I know that poll() will give you a read-availability event, so
>> you'll read the EOF. Will kqueue?
> AFAIK yes for sockets, not for file descriptor (i.e. descriptor open
> to a file on filesystem). Would poll() give yo
Bill Studenmund wrote:
> I think the difference is in the default behavior. When you're at EOF, I
> know that poll() will give you a read-availability event, so you'll read
> the EOF. Will kqueue?
AFAIK yes for sockets, not for file descriptor (i.e. descriptor
open to a file on filesystem). Woul
> Outside the jail, it worked fine. inside the jail, sendto failed with a
> EINVAL error.
See:
http://www.freebsd.org/cgi/query-pr.cgi?pr=kern/26506
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubs
On Wed, Nov 12, 2003 at 10:01:23AM -0800, FB wrote:
+> We patched mijail5 (http://garage.freebsd.pl/mijail.README) against
+> RELENG_5_1. Most of the patch was successful with a little fuzz, except for
+> a couple lines in jls which didn't patch due to cosmetic changes (easily
+> fixed).
+>
19 matches
Mail list logo
