I'm trying to execute a shell script with binkd on a file receive but
it doesn't work. :(
The config is this:
exec "/home/husky/bin/netsegments.sh" net33?.???
I'm trying to execute a shell script with binkd on a file receive
but it doesn't work. :(
The config is this:
exec "/home/husky/bin/netsegments.sh" net33?.???
Would a target of net33* do any better?
BTW I did it at last, I've had to add the full path of the received file. It sounds a bit strange because the other exec statements works without the full path added. :/
This Works:
exec "/home/husky/bin/netsegments.sh" /home/husky/in.sec/net33?.???
This Works:
exec "/home/husky/bin/netsegments.sh" /home/husky/in.sec/net33?.???
This doesent work:
exec "/home/husky/bin/netsegments.sh" net33?.???
This always works:
exec "/home/husky/bin/mailin.sh" *.su? *.mo? *.tu? *.we? *.th? *.fr? *.sa? *.tic *.pkt
This doesent work:
exec "/home/husky/bin/netsegments.sh" net33?.???
This always works:
exec "/home/husky/bin/mailin.sh" *.su? *.mo? *.tu? *.we? *.th?
*.fr? *.sa? *.tic *.pkt
Those files have wildcard that includes the full path
*/net33?.??? should work as well.
08 Nov 19 00:17, you wrote to me:
This doesent work:
exec "/home/husky/bin/netsegments.sh" net33?.???
This always works:
exec "/home/husky/bin/mailin.sh" *.su? *.mo? *.tu? *.we? *.th?
*.fr? *.sa? *.tic *.pkt
Those files have wildcard that includes the full path
*/net33?.??? should work as well.
So the facing asterisk in the working example has a double meaning:
1) Every file name before the dot.
2) Every path.
It sounds a bit odd. :) Usually in *nix shells the wildcard limits it influence only on the file name and doesn't touch the path.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,033 |
Nodes: | 15 (0 / 15) |
Uptime: | 124:50:50 |
Calls: | 529 |
Calls today: | 23 |
Files: | 95,154 |
D/L today: |
4,453 files (643M bytes) |
Messages: | 298,898 |
Posted today: | 12 |