> "Frank" == Frank Knobbe <[EMAIL PROTECTED]> writes:
Frank> If you nullfs these directories, you loose the ability to
Frank> prune the jail. Pruning is part of system hardening. I'd
May be it's better to use unionfs, so anybody can replace binaries
with their stub version pre jail.
--
DS
Denis Shaposhnikov wrote:
"Frank" == Frank Knobbe <[EMAIL PROTECTED]> writes:
Frank> If you nullfs these directories, you loose the ability to
Frank> prune the jail. Pruning is part of system hardening. I'd
May be it's better to use unionfs, so anybody can replace binaries
with their stub versio
On Sat, Mar 12, 2005 at 06:12:19PM +, Alex Burke wrote:
> Hi,
>
> I am just wondering how I can access either BIOS calls, or preferably
> registers under FreeBSD?
>
> I am trying to write a simple system capable of displaying graphics on
> the screen, and I am pretty sure I can mmap the VGA m
Not a bad 'idea' at all, although I won't comment on semantics. I had
something implemented using fs stacking (in a very hackish way, and I
believe it's lost now, so don't ask to see it...) to implement per-jail
quota's that seemed to work quite well.
Sam
>
> This might be a very stupid idea b
Samuel J. Greear wrote:
Not a bad 'idea' at all, although I won't comment on semantics. I had
something implemented using fs stacking (in a very hackish way, and I
believe it's lost now, so don't ask to see it...) to implement per-jail
quota's that seemed to work quite well.
Sam
Feel free to com
I have a script that works fine from command line.
But when I run it from cron , its not displaying all the info.
Looks like cron is limiting the char length.
example from script ran by cron:
root54313 0.0 0.2 1024 720 ?? S 3:20PM 0:00.00 cron:
running jo
example from script ran
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 13 Mar 2005, junk wrote:
I have a script that works fine from command line.
But when I run it from cron , its not displaying all the info.
Looks like cron is limiting the char length.
example from script ran by cron:
root54313 0.0 0.2 102
On Sunday 13 March 2005 01:23 pm, Chris Hodgins wrote:
> Samuel J. Greear wrote:
> > Not a bad 'idea' at all, although I won't comment on semantics.
> > I had something implemented using fs stacking (in a very hackish
> > way, and I believe it's lost now, so don't ask to see it...) to
> > implemen
Anish Mistry wrote:
On Sunday 13 March 2005 01:23 pm, Chris Hodgins wrote:
Samuel J. Greear wrote:
Not a bad 'idea' at all, although I won't comment on semantics.
I had something implemented using fs stacking (in a very hackish
way, and I believe it's lost now, so don't ask to see it...) to
implem
c0ldbyte wrote:
> On Sun, 13 Mar 2005, junk wrote:
>
> >> I have a script that works fine from command line.
> >> But when I run it from cron , its not displaying all the info.
> >> Looks like cron is limiting the char length.
> >>
> >> example from script ran by cron:
> >>
> >> root54313 0.0
junk wrote:
>c0ldbyte wrote:
>
>
>
>>On Sun, 13 Mar 2005, junk wrote:
>>
>>
>>
I have a script that works fine from command line.
But when I run it from cron , its not displaying all the info.
Looks like cron is limiting the char length.
example from script ran by cron:
Pieter de Boer wrote:
>
>> The script thats being ran by cron does a 'ps x |grep test.pl'. and
>> prases the output from test.pl, but since cron is limiting the char
>> length, its not parsing the output right.
>
> ps -xw ?
>
Yeah. That was the problem.
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sun, 13 Mar 2005, junk wrote:
Pieter de Boer wrote:
The script thats being ran by cron does a 'ps x |grep test.pl'. and
prases the output from test.pl, but since cron is limiting the char
length, its not parsing the output right.
ps -xw ?
Yeah. Tha
c0ldbyte wrote:
> On Sun, 13 Mar 2005, junk wrote:
>
> >> Pieter de Boer wrote:
> >>
> >>>
> The script thats being ran by cron does a 'ps x |grep test.pl'. and
> prases the output from test.pl, but since cron is limiting the char
> length, its not parsing the output right.
> >>>
>
On Fri, Mar 11, 2005 at 10:27:36AM -0500, Jim Rees wrote:
> There are OpenAFS and NFSv4 clients for FreeBSD, but unfortunately neither
> is really production quality. It wouldn't take much to make at least the
> OpenAFS client usable but no one seems to be working on it now.
I may be looking into
15 matches
Mail list logo
