Apache Ant has the bad behavior of deleting all the files in a symlink directory. Although somebody has created a patch for this behaviour, it doesn't seem as if it will ever get into an official release. I suspect the reason for this is that the Delete task should not care about fileset internals.
On the other hand it would be great if the Symlink task would have the ability to use filesets or even recorded symlinks in a delete call.
Once I have time, I'll do something about this...
Monday, November 27, 2006
Saturday, November 25, 2006
Apparently my personality is...
| ISTP - "Engineer". Values freedom of action and following interests and impulses. Independent, concise in speech, master of tools. 5.4% of total population. |
Saturday, November 04, 2006
Some tips for executing remote scripts
It is sometimes useful to execute scripts remotely via ssh, and have those scripts execute other scripts or even other remote scripts via ssh. The following tips might come in handy...
If your script requires any type of terminal interaction, you might need to specify the -t command line option to ssh in order for a pseudo-terminal to be allocated to your session. This way you will be able to enter passwords, etc.
If your script requires access to shell environment variables, add -l to the 'slash bang' (I keep on forgetting the proper name for this) line, e.g. #!/bin/bash -l
If you need to execute certain commands as another user, e.g. root, and you don't want to make the script setuid, then rather create a separate script and execute it with su -c from the first script. Simply using su in the first script will not work.
If your script requires any type of terminal interaction, you might need to specify the -t command line option to ssh in order for a pseudo-terminal to be allocated to your session. This way you will be able to enter passwords, etc.
If your script requires access to shell environment variables, add -l to the 'slash bang' (I keep on forgetting the proper name for this) line, e.g. #!/bin/bash -l
If you need to execute certain commands as another user, e.g. root, and you don't want to make the script setuid, then rather create a separate script and execute it with su -c from the first script. Simply using su in the first script will not work.
Subscribe to:
Posts (Atom)