Re: [PATCH] add file position info to proc

2007-03-10 Thread Miklos Szeredi
> >On Sat, Mar 10, 2007 at 03:02:22PM +0100, Jan Engelhardt wrote: > > > >> http://www.mail-archive.com/linux-fsdevel@vger.kernel.org/msg03964.html > > > >to make 'lsof -o' work/happy? > > To make the user happy. lsof is another thing. Yeah, I occasionally come across requests for this feature, a

Re: [PATCH] add file position info to proc

2007-03-10 Thread Jan Engelhardt
>On Sat, Mar 10, 2007 at 03:02:22PM +0100, Jan Engelhardt wrote: > >> http://www.mail-archive.com/linux-fsdevel@vger.kernel.org/msg03964.html > >to make 'lsof -o' work/happy? To make the user happy. lsof is another thing. Jan -- - To unsubscribe from this list: send the line "unsubscribe linux

Re: [PATCH] add file position info to proc

2007-03-10 Thread Chris Wedgwood
On Sat, Mar 10, 2007 at 03:02:22PM +0100, Jan Engelhardt wrote: > http://www.mail-archive.com/linux-fsdevel@vger.kernel.org/msg03964.html to make 'lsof -o' work/happy? is that really worth it? we've managed without it for years... i'n not entirely against the concept, i just work that we too e

Re: [PATCH] add file position info to proc

2007-03-10 Thread Jan Engelhardt
On Mar 9 2007 23:05, Chris Wedgwood wrote: >On Fri, Mar 09, 2007 at 02:54:38PM +0100, Miklos Szeredi wrote: > >> This patch adds support for finding out the current file position, >> open flags and possibly other info in the future. > >who needs this? /proc/ is an ugly beast at the best of times,

Re: [PATCH] add file position info to proc

2007-03-09 Thread Chris Wedgwood
On Fri, Mar 09, 2007 at 02:54:38PM +0100, Miklos Szeredi wrote: > This patch adds support for finding out the current file position, > open flags and possibly other info in the future. who needs this? /proc/ is an ugly beast at the best of times, is this really needed? - To unsubscribe from this

Re: [PATCH] add file position info to proc

2007-03-09 Thread Dave Kleikamp
On Fri, 2007-03-09 at 22:03 +0100, Miklos Szeredi wrote: > > I think this information would be a little easier to access if there > > would be a single file per pid or thread containing something like: > > > > handle flags pos path > > 0 012 1234/dev/pts

Re: [PATCH] add file position info to proc

2007-03-09 Thread Miklos Szeredi
> I think this information would be a little easier to access if there > would be a single file per pid or thread containing something like: > > handle flags pos path > 0012 1234/dev/pts/1 > 1014 5678/tmp/output > etc. > >>

Re: [PATCH] add file position info to proc

2007-03-09 Thread Jan Engelhardt
Hello, first of all, big thanks to Miklos for rebasing the patch to a newer kernel. :-) On Mar 9 2007 17:00, Miklos Szeredi wrote: I think this information would be a little easier to access if there would be a single file per pid or thread containing something like: handle

Re: [PATCH] add file position info to proc

2007-03-09 Thread Miklos Szeredi
> On Fri, 2007-03-09 at 10:23 -0500, Benjamin LaHaise wrote: > > On Fri, Mar 09, 2007 at 09:15:06AM -0600, Dave Kleikamp wrote: > > > I think this information would be a little easier to access if there > > > would be a single file per pid or thread containing something like: > > > > > > handle

Re: [PATCH] add file position info to proc

2007-03-09 Thread Miklos Szeredi
> > > > pos:1234 > > flags: 012 > > Why are the flags in octal? File mode bits are represented in octal in both and , so this is the least "human unreadable" format. Miklos - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [

Re: [PATCH] add file position info to proc

2007-03-09 Thread Miklos Szeredi
> > > > > > pos: 1234 > > > flags:012 > > > > Why are the flags in octal? > > File mode bits are represented in octal in both s/mode/flag/ - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to [EMAIL PROTECTED] More majordomo info a

Re: [PATCH] add file position info to proc

2007-03-09 Thread Dave Kleikamp
On Fri, 2007-03-09 at 10:23 -0500, Benjamin LaHaise wrote: > On Fri, Mar 09, 2007 at 09:15:06AM -0600, Dave Kleikamp wrote: > > I think this information would be a little easier to access if there > > would be a single file per pid or thread containing something like: > > > > handle flags p

Re: [PATCH] add file position info to proc

2007-03-09 Thread Benjamin LaHaise
On Fri, Mar 09, 2007 at 09:15:06AM -0600, Dave Kleikamp wrote: > I think this information would be a little easier to access if there > would be a single file per pid or thread containing something like: > > handleflags pos path > 0 012 1234/dev/pts/1 > 1 014 5678

Re: [PATCH] add file position info to proc

2007-03-09 Thread Jörn Engel
On Fri, 9 March 2007 14:54:38 +0100, Miklos Szeredi wrote: > > pos: 1234 > flags:012 Why are the flags in octal? Jörn -- Happiness isn't having what you want, it's wanting what you have. -- unknown - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the b

Re: [PATCH] add file position info to proc

2007-03-09 Thread Dave Kleikamp
On Fri, 2007-03-09 at 14:54 +0100, Miklos Szeredi wrote: > Comments are welcome. > > > This patch adds support for finding out the current file position, > open flags and possibly other info in the future. > > These new entries are added: > > /proc/PID/fdinfo/FD > /proc/PID/task/TID/fdi