C-FFS anyone?

2000-02-26 Thread Alex Povolotsky

Hello!

I've just read (well, partially) a whitepaper named "Embedded Inodes and
Explicit Grouping: Exploiting Disk Bandwidth for Small Files" (don't have
URL at hand).

Ideas presented there are QUIT interesting. Did anyone tried to implement
them in BSD?

Alex.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Strange behaviour of loaded system

2000-01-19 Thread Alex Povolotsky

Hello!

I've observed a VERY strange behaviour of a moderately-to-heavy loaded
system (load average about 5.7 on a 2xPII-400 with 512Mb of RAM):

(I have no access to the box right now, and I'm giving only general details;
however, I'll be able to produce more details next morning)

About 200-300 processes (230-280, something always creates and dies), some
swapping (I recall 36% right now), and the most strange thing: always some
(4-14M) of free RAM, and about 100 pageins per second. Most of processes are
modperl'ed Apaches and self-written POP3 readers.

I have no good understanding of such behaviour. Unfortunately I cannot find
my "UNIX Internals: The New Frontier" for several days, so I'm really
limited on books. Maybe some kind soul will tell me how can system behave
that way?

Alex.





To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Problems with FIFO open in non-blocking mode?

1999-09-06 Thread Alex Povolotsky

Hello!

The following program

#include stdio.h
#include fcntl.h

main() {
int control;
if ((control = open("STATUS",O_WRONLY|O_NONBLOCK))0) {
perror("Could not open STATUS ");
exit(1);
}
printf("STATUS ready\n");
close(control);
return(0);
}

fails to run (STATUS is pre-created FIFO file) with error "Device not
configured", which seems kinda odd for me.

However, when FIFO is opened with O_RDWR and O_NONBLOCK, every attempt 
to select(2) its handler for writing doesn't wait until someone opens
FIFO for reading, but instead FIFO is ready to write at every select.

Is it a bug or a feature?

-- 
Alexander B. Povolotsky[ICQ 18277558]
[2:5020/145]  [http://freebsd.svib.ru] [[EMAIL PROTECTED]]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: kern/13593: Problems with FIFO and select

1999-09-06 Thread Alex Povolotsky

 "Bruce" == Bruce Evans writes:

 Description:
 Attempt to open FIFO file with O_WRONLY|O_NONBLOCK results in
 Device not configured error.

Bruce This is because there is no reader when the FIFO is opened for
Bruce writing (O_WRONLY opens of FIFOs normally block waiting for a
Bruce reader, but O_NONBLOCK gives an error instead).

Well, but how do I multiplex on FIFO opening? 

 However, when FIFO is opened with O_RDWR and O_NONBLOCK, every
 attempt to select(2) its handler for writing doesn't wait until
 someone opens FIFO for reading, but instead FIFO is ready to write
 at every select.

Bruce This is because O_RDWR gives both a reader and a writer.

Well again, both things are reasonable, but I wanted to do the
following:

(1) open a control FIFO, for external commands
(2) open a status FIFO, for status reporting
(3) open several sockets for internal usage

and than select() on all of them, waiting for either command to
arrive, request for status, or (some internal event,
select()-multiplexable).

I can implement this using UNIX sockets and external programs, but can 
I make status reporting without external program?

-- 
Alexander B. Povolotsky[ICQ 18277558]
[2:5020/145]  [http://freebsd.svib.ru] [[EMAIL PROTECTED]]


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: kern/13593: Problems with FIFO and select

1999-09-06 Thread Alex Povolotsky
 Bruce == Bruce Evans writes:

 Description:
 Attempt to open FIFO file with O_WRONLY|O_NONBLOCK results in
 Device not configured error.

Bruce This is because there is no reader when the FIFO is opened for
Bruce writing (O_WRONLY opens of FIFOs normally block waiting for a
Bruce reader, but O_NONBLOCK gives an error instead).

Well, but how do I multiplex on FIFO opening? 

 However, when FIFO is opened with O_RDWR and O_NONBLOCK, every
 attempt to select(2) its handler for writing doesn't wait until
 someone opens FIFO for reading, but instead FIFO is ready to write
 at every select.

Bruce This is because O_RDWR gives both a reader and a writer.

Well again, both things are reasonable, but I wanted to do the
following:

(1) open a control FIFO, for external commands
(2) open a status FIFO, for status reporting
(3) open several sockets for internal usage

and than select() on all of them, waiting for either command to
arrive, request for status, or (some internal event,
select()-multiplexable).

I can implement this using UNIX sockets and external programs, but can 
I make status reporting without external program?

-- 
Alexander B. Povolotsky[ICQ 18277558]
[2:5020/145]  [http://freebsd.svib.ru] [tark...@asteroid.svib.ru]


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Problems with FIFO open in non-blocking mode?

1999-09-05 Thread Alex Povolotsky
Hello!

The following program

#include stdio.h
#include fcntl.h

main() {
int control;
if ((control = open(STATUS,O_WRONLY|O_NONBLOCK))0) {
perror(Could not open STATUS );
exit(1);
}
printf(STATUS ready\n);
close(control);
return(0);
}

fails to run (STATUS is pre-created FIFO file) with error Device not
configured, which seems kinda odd for me.

However, when FIFO is opened with O_RDWR and O_NONBLOCK, every attempt 
to select(2) its handler for writing doesn't wait until someone opens
FIFO for reading, but instead FIFO is ready to write at every select.

Is it a bug or a feature?

-- 
Alexander B. Povolotsky[ICQ 18277558]
[2:5020/145]  [http://freebsd.svib.ru] [tark...@asteroid.svib.ru]


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Solution for mail pseudo-users?

1999-07-31 Thread Alex Povolotsky

Hello!

I'm going to implement a large mail-box, with several hundreds of mail-only
users. They should never access anything besides their POP3 mailboxes and
change password via (SSLed) web interface.

So, I don't want to add all of them to /etc/passwd.

I have a hack that requires to change libc to make getpwent access not only
/etc/master.passwd, but also some mySQL database, but it is hard-to-rebuild
and overall dirty hack.

Do not ask me to RTFM on PAM, for PAM does not allow me to add users not
mentioned in passwd.

As far as I understand, LDAP is rather bulky and suited to X.500
integration, and that is not what I want.

Any suggestions, anyone?

Alex.


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Re: Solution for mail pseudo-users?

1999-07-31 Thread Alex Povolotsky

 [EMAIL PROTECTED]Sergey Babkin writes:
 Any suggestions, anyone?

Modify the POP daemon to use your mySQL database in addition to getpwent ?
That seems to be the easiest way that should not break anything else.

And modify sendmail to throw off mail for nonexistent users?

Alex.
-- 
Alexander B. Povolotsky[ICQ 18277558]
[2:5020/145]  [http://freebsd.svib.ru] [[EMAIL PROTECTED]]




To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message



Solution for mail pseudo-users?

1999-07-31 Thread Alex Povolotsky
Hello!

I'm going to implement a large mail-box, with several hundreds of mail-only
users. They should never access anything besides their POP3 mailboxes and
change password via (SSLed) web interface.

So, I don't want to add all of them to /etc/passwd.

I have a hack that requires to change libc to make getpwent access not only
/etc/master.passwd, but also some mySQL database, but it is hard-to-rebuild
and overall dirty hack.

Do not ask me to RTFM on PAM, for PAM does not allow me to add users not
mentioned in passwd.

As far as I understand, LDAP is rather bulky and suited to X.500
integration, and that is not what I want.

Any suggestions, anyone?

Alex.


To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Re: Solution for mail pseudo-users?

1999-07-31 Thread Alex Povolotsky
 37a30852.20e5a...@bellatlantic.netSergey Babkin writes:
 Any suggestions, anyone?

Modify the POP daemon to use your mySQL database in addition to getpwent ?
That seems to be the easiest way that should not break anything else.

And modify sendmail to throw off mail for nonexistent users?

Alex.
-- 
Alexander B. Povolotsky[ICQ 18277558]
[2:5020/145]  [http://freebsd.svib.ru] [tark...@asteroid.svib.ru]




To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message



Booting from vinum?

1999-07-17 Thread Alex Povolotsky
Hello!

Is it possible to have a root partition on vinum'ed disk and benefit from 
mirroring? If yes, how do I do it?

Alex.



To Unsubscribe: send mail to majord...@freebsd.org
with unsubscribe freebsd-hackers in the body of the message