| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 18/07/12 03:49 PM, Peter Stuge wrote: |
| 5 |
> William Hubbs wrote: |
| 6 |
>> /etc/init.d/foo stop start |
| 7 |
>> |
| 8 |
>> would no longer work the way you might expect because there would |
| 9 |
>> be no way to tell whether start is a command or an argument to |
| 10 |
>> stop. |
| 11 |
>> |
| 12 |
>> What are your thoughts about this change? |
| 13 |
> |
| 14 |
> /etc/init.d/foo stop start |
| 15 |
> |
| 16 |
> along with all other commands can work like before. |
| 17 |
> |
| 18 |
> /etc/init.d/foo stop -- start |
| 19 |
> |
| 20 |
> can pass start as an argument to the stop command. |
| 21 |
> |
| 22 |
> |
| 23 |
> //Peter |
| 24 |
|
| 25 |
|
| 26 |
I posted a response about this to the bug, but I don't see why, given |
| 27 |
that all 'commands' are predefined anyways, the commandline couldn't |
| 28 |
be parsed and split between commands.. |
| 29 |
|
| 30 |
|
| 31 |
-----BEGIN PGP SIGNATURE----- |
| 32 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 33 |
|
| 34 |
iF4EAREIAAYFAlAHFCkACgkQ2ugaI38ACPANyAEAnF7ngFvy/lcHPo0A4vEyN0zS |
| 35 |
5QFTRmOiFG+GS8cRkyEBAL3ABkRD9M44sVHGs52ioctce+tsBSfLU9bawmBQuuJf |
| 36 |
=dzvV |
| 37 |
-----END PGP SIGNATURE----- |
Archives