Date: Tue, 12 Jun 2007 23:35:12 -0700 From: Garrett Cooper <youshi10@u.washington.edu> To: Alexander Leidinger <Alexander@Leidinger.net> Cc: hackers@freebsd.org Subject: Re: Using shell commands versus C equivalents Message-ID: <466F9020.9050306@u.washington.edu> In-Reply-To: <20070613083046.atl5dyq3s488s0o8@webmail.leidinger.net> References: <466F86C6.7010006@u.washington.edu> <20070613083046.atl5dyq3s488s0o8@webmail.leidinger.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexander Leidinger wrote:
> Quoting Garrett Cooper <youshi10@u.washington.edu> (from Tue, 12 Jun
> 2007 22:55:18 -0700):
>
>> Another simple question (I hope):
>> Is there any reason why shell commands should be used in place of a
>> C command (in this case chmod via vsystem instead of the chmod(2)
>> function)? It seems like the fork / exec would be more expensive with
>> the shell command, but any area where code could be optimized is more
>> than welcome I would think.
>
> If it is just one file, I don't see the reason to use the shell
> command, but if you need to reinvent "chmod -R", I don't see a reason
> to forbid the use of the shell command (pragmatic programming).
>
> Bye,
> Alexander.
>
Exactly my thinking (ch{own,mod} for one file, not reinventing the
-R 'wheel'). After looking over style(7) I don't see anything about not
doing that.
Thanks for the reply :).
-Garrett
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?466F9020.9050306>