On 05/17/2012 02:51 PM, Bryan Drewery wrote:
> Yeah it's what I get for mashing a pseudo example up and not testing it!
S'ok, I screwed up ${service##*/} in mine. :)
___
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/f
On 5/17/2012 4:37 PM, Doug Barton wrote:
> On 05/14/2012 06:35, Bryan Drewery wrote:
>
>
>> On 5/13/2012 6:15 PM, Doug Barton wrote:
>>> On 5/12/2012 8:23 PM, Bryan Drewery wrote:
Hi,
I found service(8) to be inconsistent that it listed files with
`service -e`, but plain ser
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 05/14/2012 06:35, Bryan Drewery wrote:
>
>
> On 5/13/2012 6:15 PM, Doug Barton wrote:
>> On 5/12/2012 8:23 PM, Bryan Drewery wrote:
>>> Hi,
>>>
>>> I found service(8) to be inconsistent that it listed files with
>>> `service -e`, but plain serv
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 5/13/2012 6:15 PM, Doug Barton wrote:
> On 5/12/2012 8:23 PM, Bryan Drewery wrote:
>> Hi,
>>
>> I found service(8) to be inconsistent that it listed files with `service
>> -e`, but plain services with `service -l`
>
> That behavior is by design.
On 5/12/2012 8:23 PM, Bryan Drewery wrote:
> Hi,
>
> I found service(8) to be inconsistent that it listed files with `service
> -e`, but plain services with `service -l`
That behavior is by design.
Thanks for your interest,
Doug
--
This .signature sanitized for your protection
__
Hi,
I found service(8) to be inconsistent that it listed files with `service
-e`, but plain services with `service -l`
My patch makes the default just list *service names*, and specifying -F
will show the full path to the file.
Patch:
http://www.shatow.net/freebsd/patch-service.txt
Regards,
Br
