Re: Trouble installing xpdf port in 3.4-stable

[jack]

Today Vivek Khera wrote:

> > "MH" == Matt Heckaman <[EMAIL PROTECTED]> writes:
> 
> MH> I do not know if "should" would be the word I would choose, however it
> MH> fits the situation well. Personally, I cvsup ports every night, but I'm
> MH> a little bit over-obsessed with things being "new" =)
> 
> I do as well, but I find it a bit tedious to scan the updated files
> list to see what is really updated.  Has anyone got a method to say
> typing "make whatsnew" in the top of ports and have it scan my
> existing ports and the current index and tell me what's out of date
> version number wise?

pkg_version(1)

--
Jack O'NeillSystems Administrator / Systems Analyst
[EMAIL PROTECTED] Crystal Wind Communications, Inc.
  Finger [EMAIL PROTECTED] for my PGP key.
   PGP Key fingerprint = F6 C4 E6 D4 2F 15 A7 67   FD 09 E9 3C 5F CC EB CD
   enriched, vcard, HTML messages > /dev/null
--




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

Re: Error: "Maximum file descriptors exceeded"...

[Tom]

Beware of per-user limits.  You don't mention what user you ran "limit"
as, or what user the news server process runs as.  Each could have very
different limits.  See /etc/login.conf.  It might even depend on how the
server server process is started.  Processes started at boot run under the
"daemon" class, for instance.

BTW, the system wide file limit is not static.  You don't need to
re-compile to change it, or even reboot.  Just use sysctl.


Tom
Uniserve



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

Re: Trouble installing xpdf port in 3.4-stable

[Matt Heckaman]

I call cvsup from crontab, with a line like this:

0 8 * * * root cvsup -g -L 2 /usr/local/etc/cvsup/ports-supfile \
| mail -s "epsilon.lucida.qc.ca: ports update output" admin

(formatted so it would read right in email)

The output from cvsup only shows what it's changed, so it's very handy for
tracking what's new, you get it in your e-mail once per day.

Matt
--
Matt Heckaman [[EMAIL PROTECTED]|[EMAIL PROTECTED]] [Please do not send me]
!Powered by FreeBSD/x86! [http://www.freebsd.org] [any SPAM (UCE) e-mail]

On Tue, 29 Feb 2000, Vivek Khera wrote:

: Date: Tue, 29 Feb 2000 11:06:40 -0500
: From: Vivek Khera <[EMAIL PROTECTED]>
: To: Matt Heckaman <[EMAIL PROTECTED]>
: Cc: FreeBSD-STABLE <[EMAIL PROTECTED]>
: Subject: Re: Trouble installing xpdf port in 3.4-stable
: 
: > "MH" == Matt Heckaman <[EMAIL PROTECTED]> writes:
: 
: MH> I do not know if "should" would be the word I would choose, however it
: MH> fits the situation well. Personally, I cvsup ports every night, but I'm
: MH> a little bit over-obsessed with things being "new" =)
: 
: I do as well, but I find it a bit tedious to scan the updated files
: list to see what is really updated.  Has anyone got a method to say
: typing "make whatsnew" in the top of ports and have it scan my
: existing ports and the current index and tell me what's out of date
: version number wise?
: 
: -- 
: =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
: Vivek Khera, Ph.D.Khera Communications, Inc.
: Internet: [EMAIL PROTECTED]   Rockville, MD   +1-301-545-6996
: PGP & MIME spoken herehttp://www.kciLink.com/home/khera/
: 



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

Re: Error: "Maximum file descriptors exceeded"...

[James Housley]

Brad Knowles wrote:
> 
> 
> Unfortunately, none of this seems to be related to my problem of
> having the error message described, or how I can eliminate this error
> message.
> 
housley@cat:~/work/monitors {34} sysctl -a | grep -i file
kern.maxfiles: 2088
kern.bootfile: /kernel
kern.maxfilesperproc: 2088
kern.corefile: %N.core
p1003_1b.mapped_files: 0

It looks like updating kern.maxfiles and/or kern.maxfilesperproc should
do the trick.  What are the limits set in /etc/login.conf??

Jim
-- 
Unix is very user-friendly.  It's just picky who its friends are.


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

Re: Error: "Maximum file descriptors exceeded"...

[Brad Knowles]

At 8:12 AM -0800 2000/2/29, Tom wrote:

>  Beware of per-user limits.  You don't mention what user you ran "limit"
>  as, or what user the news server process runs as.  Each could have very
>  different limits.  See /etc/login.conf.  It might even depend on how the
>  server server process is started.  Processes started at boot run under the
>  "daemon" class, for instance.

In theory, this is true.  However, my /etc/login.conf does not 
appear to be configured this way:

$ grep -v '^#' /etc/login.conf



default:\
 :copyright=/etc/COPYRIGHT:\
 :welcome=/etc/motd:\
 :setenv=MAIL=/var/mail/$,BLOCKSIZE=K:\
 :path=~/bin /bin /usr/bin /usr/local/bin /usr/X11R6/bin:\
 :nologin=/var/run/nologin:\
 :cputime=unlimited:\
 :datasize=unlimited:\
 :stacksize=unlimited:\
 :memorylocked=unlimited:\
 :memoryuse=unlimited:\
 :filesize=unlimited:\
 :coredumpsize=unlimited:\
 :openfiles=unlimited:\
 :maxproc=unlimited:\
 :priority=0:\
 :ignoretime@:\
 :umask=022:


standard:\
 :tc=default:
xuser:\
 :tc=default:
staff:\
 :tc=default:
daemon:\
 :tc=default:
news:\
 :tc=default:
dialer:\
 :tc=default:

root:\
 :ignorenologin:\
 :tc=default:

russian:Russian Users Accounts:\
 :charset=KOI8-R:\
 :lang=ru_RU.KOI8-R:\
 :tc=default:

>  BTW, the system wide file limit is not static.  You don't need to
>  re-compile to change it, or even reboot.  Just use sysctl.

I guess I'm going to have to read up on that


Thanks!

-- 
  These are my opinions and should not be taken as official Skynet policy
=
Brad Knowles, <[EMAIL PROTECTED]>   Sys. Arch., Mail/News/FTP/Proxy Admin

Note: No Microsoft programs were used in the creation or distribution of
this message. If you are using a Microsoft program to view this message,
be forewarned that I am not responsible for any harm you may encounter as
a result.

See  for
details.


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

Re: Error: "Maximum file descriptors exceeded"...

[Sean O'Connell]

James Housley stated:
> Brad Knowles wrote:
> > 
> > 
> > Unfortunately, none of this seems to be related to my problem of
> > having the error message described, or how I can eliminate this error
> > message.
> > 
> housley@cat:~/work/monitors {34} sysctl -a | grep -i file
> kern.maxfiles: 2088
> kern.bootfile: /kernel
> kern.maxfilesperproc: 2088
> kern.corefile: %N.core
> p1003_1b.mapped_files: 0
> 
> It looks like updating kern.maxfiles and/or kern.maxfilesperproc should
> do the trick.  What are the limits set in /etc/login.conf??

I thought this too, but if I run

sysctl -w kern.maxfiles=4096
sysctl -w kern.maxfilesperproc=4096

Now:

% sysctl kern.maxfiles
kern.maxfiles: 4096
% sysctl kern.maxfilesperproc
kern.maxfilesperproc: 4096

However, limit -h (tcsh builtin) and limits -H still report 

descriptors 2088
openfiles2088

respectively.

Even the manpage for sysctl implies this

 NameType  Changeable
 kern.maxfiles   integer   yes
 kern.maxfilesperprocinteger   yes

Am I missing something obvious?  Are these values really updated?

S
---
Sean O'ConnellEmail: [EMAIL PROTECTED]
Institute of Statistics and Decision Sciences Phone: (919) 684-5419
Duke University   Fax:   (919) 684-8594


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

Re: Error: "Maximum file descriptors exceeded"...

[Vivek Khera]

> "SO" == Sean O'Connell <[EMAIL PROTECTED]> writes:

SO> I thought this too, but if I run

SO> sysctl -w kern.maxfiles=4096
SO> sysctl -w kern.maxfilesperproc=4096

SO> Now:

SO> % sysctl kern.maxfiles
SO> kern.maxfiles: 4096
SO> % sysctl kern.maxfilesperproc
SO> kern.maxfilesperproc: 4096

SO> However, limit -h (tcsh builtin) and limits -H still report 

SO> descriptors 2088
SO> openfiles2088

 [ ... ]

SO> Am I missing something obvious?  Are these values really updated?

Did you logout and back in?  I don't think upping the system-wide
limits will dynamically update the limits given to processes that are
already started.  Logging in again will cause your process (ie, the
shell) to have its resource limits set to the current hard limits.

ps: Go Duke!!!  I really miss the place. ;-(

-- 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D.Khera Communications, Inc.
Internet: [EMAIL PROTECTED]   Rockville, MD   +1-301-545-6996
PGP & MIME spoken herehttp://www.kciLink.com/home/khera/


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

Re: Error: "Maximum file descriptors exceeded"...

[James Housley]

Sean O'Connell wrote:
> 
> % sysctl kern.maxfiles
> kern.maxfiles: 4096
> % sysctl kern.maxfilesperproc
> kern.maxfilesperproc: 4096
> 
> However, limit -h (tcsh builtin) and limits -H still report
> 
> descriptors 2088
> openfiles2088
> 
> respectively.
> 
> Even the manpage for sysctl implies this
> 
>  NameType  Changeable
>  kern.maxfiles   integer   yes
>  kern.maxfilesperprocinteger   yes
> 
> Am I missing something obvious?  Are these values really updated?
> 

Logout and back in the shell probably gets the value when spawned/login.

Jim

-- 
Unix is very user-friendly.  It's just picky who its friends are.


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

Re: Error: "Maximum file descriptors exceeded"...

[James Housley]

Sean O'Connell wrote:
>  kern.maxfilesperprocinteger   yes
> 
> Am I missing something obvious?  Are these values really updated?
> 

Logout and back in the shell probably gets the value when spawned/login.

And if that fixes it you will need to either kill -1 your problem
program or kill and restart it so it has the new limits.

Jim


-- 
Unix is very user-friendly.  It's just picky who its friends are.


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

Re: Error: "Maximum file descriptors exceeded"...

[Sean O'Connell]

Vivek Khera stated:
> > "SO" == Sean O'Connell <[EMAIL PROTECTED]> writes:
> 
> SO> I thought this too, but if I run
> 
> SO> sysctl -w kern.maxfiles=4096
> SO> sysctl -w kern.maxfilesperproc=4096
> 
> SO> Now:
> 
> SO> % sysctl kern.maxfiles
> SO> kern.maxfiles: 4096
> SO> % sysctl kern.maxfilesperproc
> SO> kern.maxfilesperproc: 4096
> 
> SO> However, limit -h (tcsh builtin) and limits -H still report 
> 
> SO> descriptors 2088
> SO> openfiles2088
> 
>  [ ... ]
> 
> SO> Am I missing something obvious?  Are these values really updated?
> 
> Did you logout and back in?  I don't think upping the system-wide
> limits will dynamically update the limits given to processes that are
> already started.  Logging in again will cause your process (ie, the
> shell) to have its resource limits set to the current hard limits.
> 
> ps: Go Duke!!!  I really miss the place. ;-(

Vivek-

D'oh.  Sean gets the proverbial pointy hat on that.  I did a login
from an xterm -ls and it worked.  I have too many open windows at
the moment.

So for the matter at hand, I would suppose that stopping and restarting
innd would be all that is needed.

S

PS. And to think I give people a "hard time" about group membership
and the need to logout and log back in.

---
Sean O'ConnellEmail: [EMAIL PROTECTED]
Institute of Statistics and Decision Sciences Phone: (919) 684-5419
Duke University   Fax:   (919) 684-8594


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

Re: Error: "Maximum file descriptors exceeded"...

[Brad Knowles]

At 11:34 AM -0500 2000/2/29, Sean O'Connell wrote:

>  % sysctl kern.maxfiles
>  kern.maxfiles: 4096
>  % sysctl kern.maxfilesperproc
>  kern.maxfilesperproc: 4096
>
>  However, limit -h (tcsh builtin) and limits -H still report
>
>  descriptors 2088
>  openfiles2088

Have you started a new tcsh since the sysctl?  I think that these 
sorts of things tend to be set by the program when it starts up, and 
it does not interactively detect an increase.  So, you'd need to stop 
and restart whatever program it is that needs the increased limits.

This isn't a problem in my case, since I have repeatedly stopped 
and restarted the daemon in question.

-- 
  These are my opinions and should not be taken as official Skynet policy
=
Brad Knowles, <[EMAIL PROTECTED]>   Sys. Arch., Mail/News/FTP/Proxy Admin

Note: No Microsoft programs were used in the creation or distribution of
this message. If you are using a Microsoft program to view this message,
be forewarned that I am not responsible for any harm you may encounter as
a result.

See  for
details.


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

Re: Error: "Maximum file descriptors exceeded"...

[Brad Knowles]

At 11:16 AM -0500 2000/2/29, James Housley wrote:

>  housley@cat:~/work/monitors {34} sysctl -a | grep -i file

Any my results:

$ sysctl -a | grep -i file
kern.maxfiles: 32768
kern.bootfile: /kernel
kern.maxfilesperproc: 16384
kern.corefile: %N.core
p1003_1b.mapped_files: 0

>  It looks like updating kern.maxfiles and/or kern.maxfilesperproc should
>  do the trick.  What are the limits set in /etc/login.conf??

I would think so too, but this doesn't seem to be the case.  The 
non-comment lines from my /etc/login.conf were previously posted, and 
don't set any limits for any user that are any different from what 
root gets.

-- 
  These are my opinions and should not be taken as official Skynet policy
=
Brad Knowles, <[EMAIL PROTECTED]>   Sys. Arch., Mail/News/FTP/Proxy Admin

Note: No Microsoft programs were used in the creation or distribution of
this message. If you are using a Microsoft program to view this message,
be forewarned that I am not responsible for any harm you may encounter as
a result.

See  for
details.


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

Re: Error: "Maximum file descriptors exceeded"...

[Brad Knowles]

At 11:46 AM -0500 2000/2/29, Sean O'Connell wrote:

>  So for the matter at hand, I would suppose that stopping and restarting
>  innd would be all that is needed.

My problem is with Diablo (not innd), and I've already stopped 
and restarted it several times.  No change.


Anyone got any other ideas?

-- 
  These are my opinions and should not be taken as official Skynet policy
=
Brad Knowles, <[EMAIL PROTECTED]>   Sys. Arch., Mail/News/FTP/Proxy Admin

Note: No Microsoft programs were used in the creation or distribution of
this message. If you are using a Microsoft program to view this message,
be forewarned that I am not responsible for any harm you may encounter as
a result.

See  for
details.


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

Re: Error: "Maximum file descriptors exceeded"...

[Brad Knowles]

At 11:46 AM -0500 2000/2/29, Sean O'Connell wrote:

>  So for the matter at hand, I would suppose that stopping and restarting
>  innd would be all that is needed.

Sigh  The problem turns out to have been a hard-coded limit 
in Diablo.  I've recompiled/stopped/restarted and I'll wait to see if 
the problem recurs

Sean, when you're done with it, would you please pass the pointy 
hat over this way?


Thanks everyone!

-- 
  These are my opinions and should not be taken as official Skynet policy
=
Brad Knowles, <[EMAIL PROTECTED]>   Sys. Arch., Mail/News/FTP/Proxy Admin

Note: No Microsoft programs were used in the creation or distribution of
this message. If you are using a Microsoft program to view this message,
be forewarned that I am not responsible for any harm you may encounter as
a result.

See  for
details.


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