Re: Sticky/sgid/suid bits safe on regular files?

2004-06-23 Thread Nikita Danilov
Dan Strick writes: > Daniel O'Connor wrote: > >> > > I think he wanted to use sticky/sgid/suid because they get removed > > when the file is changed. > >> > > and Dag-Erling S?rgrav responded: > >> > > no they don't. > >> > > Actually, they do. (just the sgid/suid bits) > > I beli

regarding psignal()

2004-06-23 Thread pradeep reddy punnam
Hi, i am modifing my ../netinet/ip_input.c code so that kernel can inform a user process about the arrival of a packet, i want to use signaling mechanism for this , i know the pid of the process to which the signal should be send, i am looing for exact function that can help me in sending SIGI

A few technical items on UFS2 and snapshots...

2004-06-23 Thread Joe Schmoe
(posted to -questions a few days back, but with no response) Hi - a few questions about UFS2 and snapshots: 1. Is it dangerous to mount all 20 possible filesystem snapshots and _leave them mounted_ to use at any time ? What about automatically mounting all 20 snapshots at boot time ? 2. Rela

waiting on sbwait

2004-06-23 Thread Danny Braniss
Hi, We have a host running samba under -stable 4.10, and quiet frequently it becomes uresponsive, hitting ^T gives load: 0.00 cmd: ls 12807 [sbwait] 0.00u 0.00s 0% 160k so my guess is that we are running out of some resource (socket buffer). so, if this is true, is there some sysctl to

Re: waiting on sbwait

2004-06-23 Thread Matt Freitag
I'm not sure if it's what you're hitting, but Perhaps the sysctl "kern.ipc.maxsockets" needs to be raised, though it seems like you'd need a decent amount of concurrent active sessions to reach this ceiling. Also it's read-only, so you'll want to tune it in loader.conf. -mpf Danny Braniss wrote

Re: waiting on sbwait

2004-06-23 Thread Danny Braniss
> Danny Braniss wrote: > > >Hi, > > We have a host running samba under -stable 4.10, and quiet frequently > >it becomes uresponsive, hitting ^T gives > > > >load: 0.00 cmd: ls 12807 [sbwait] 0.00u 0.00s 0% 160k > > > >so my guess is that we are running out of some resource (socket buffer).