script calling another script?












-1















ive written a couple a couple of scripts. are they going to work indefinatly and will them eventually overload the CPU?



firstly this is on a local nas that for some reason the manufacturer does not give root access or su i have an admin account so i cant just call the script with cron



first script



#!/bin/bash
#connect to server download files

rsync -ae "ssh -p 10045 -T -o Compression=no -x" --progress appbox@filebot.witzend007.appboxes.co:/APPBOX_DATA/apps/rutorrent.witzend007.appboxes.co/torrents/completed/toNAS /mnt/md0/User/admin/home/incomingdata/ --delete

wait

#copy files to temp folder
cp -r /mnt/md0/User/admin/home/incomingdata/toNAS /mnt/md0/User/admin/home/incomingdata/temp

wait

#Start Filebot and organise and rename files to plex library
~/filebot-portable/filebot.sh -script fn:amc --output "/mnt/md0/public/Media" --action move -non-strict "/mnt/md0/User/admin/home/incomingdata/temp" --log-file amc.log --def excludeList=amc.txt

wait

#remove temp folder/files

rm -r /mnt/md0/User/admin/home/incomingdata/temp

wait

#start sleep script
( "/mnt/md0/User/admin/home/filebot-portable/martinsleep.sh" )


calls the second script (which waits set time and recalls the first script)



#!/bin/bash

sleep 60
wait
( "/mnt/md0/User/admin/home/filebot-portable/martinsamc.sh" )


and then i exit vssh using




  • ctrl-z

  • bg

  • disown


this method is working the script is continuing to run in the background with vssh closed down



i do plan on changing the sleep time to 30mins my worry is that this is just opening tonnes of scripts and will eventually eat resources



Is there a better way of me achieving this?










share|improve this question









New contributor




Martin Robertson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    What do you think the wait command does? It's currently a no-op because there's nothing to wait for.

    – roaima
    2 hours ago











  • well some of the commands take a while to complete and i thought wait allows the last command to complete before doing the next command

    – Martin Robertson
    2 hours ago






  • 1





    Each command completes before the script progresses to the next item

    – roaima
    2 hours ago











  • lol i did say i was a n00b i must of misunderstood it somewhere my worry is that my second command would start before the rsync had completed and started moving around half downloaded data. thanks

    – Martin Robertson
    2 hours ago
















-1















ive written a couple a couple of scripts. are they going to work indefinatly and will them eventually overload the CPU?



firstly this is on a local nas that for some reason the manufacturer does not give root access or su i have an admin account so i cant just call the script with cron



first script



#!/bin/bash
#connect to server download files

rsync -ae "ssh -p 10045 -T -o Compression=no -x" --progress appbox@filebot.witzend007.appboxes.co:/APPBOX_DATA/apps/rutorrent.witzend007.appboxes.co/torrents/completed/toNAS /mnt/md0/User/admin/home/incomingdata/ --delete

wait

#copy files to temp folder
cp -r /mnt/md0/User/admin/home/incomingdata/toNAS /mnt/md0/User/admin/home/incomingdata/temp

wait

#Start Filebot and organise and rename files to plex library
~/filebot-portable/filebot.sh -script fn:amc --output "/mnt/md0/public/Media" --action move -non-strict "/mnt/md0/User/admin/home/incomingdata/temp" --log-file amc.log --def excludeList=amc.txt

wait

#remove temp folder/files

rm -r /mnt/md0/User/admin/home/incomingdata/temp

wait

#start sleep script
( "/mnt/md0/User/admin/home/filebot-portable/martinsleep.sh" )


calls the second script (which waits set time and recalls the first script)



#!/bin/bash

sleep 60
wait
( "/mnt/md0/User/admin/home/filebot-portable/martinsamc.sh" )


and then i exit vssh using




  • ctrl-z

  • bg

  • disown


this method is working the script is continuing to run in the background with vssh closed down



i do plan on changing the sleep time to 30mins my worry is that this is just opening tonnes of scripts and will eventually eat resources



Is there a better way of me achieving this?










share|improve this question









New contributor




Martin Robertson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1





    What do you think the wait command does? It's currently a no-op because there's nothing to wait for.

    – roaima
    2 hours ago











  • well some of the commands take a while to complete and i thought wait allows the last command to complete before doing the next command

    – Martin Robertson
    2 hours ago






  • 1





    Each command completes before the script progresses to the next item

    – roaima
    2 hours ago











  • lol i did say i was a n00b i must of misunderstood it somewhere my worry is that my second command would start before the rsync had completed and started moving around half downloaded data. thanks

    – Martin Robertson
    2 hours ago














-1












-1








-1








ive written a couple a couple of scripts. are they going to work indefinatly and will them eventually overload the CPU?



firstly this is on a local nas that for some reason the manufacturer does not give root access or su i have an admin account so i cant just call the script with cron



first script



#!/bin/bash
#connect to server download files

rsync -ae "ssh -p 10045 -T -o Compression=no -x" --progress appbox@filebot.witzend007.appboxes.co:/APPBOX_DATA/apps/rutorrent.witzend007.appboxes.co/torrents/completed/toNAS /mnt/md0/User/admin/home/incomingdata/ --delete

wait

#copy files to temp folder
cp -r /mnt/md0/User/admin/home/incomingdata/toNAS /mnt/md0/User/admin/home/incomingdata/temp

wait

#Start Filebot and organise and rename files to plex library
~/filebot-portable/filebot.sh -script fn:amc --output "/mnt/md0/public/Media" --action move -non-strict "/mnt/md0/User/admin/home/incomingdata/temp" --log-file amc.log --def excludeList=amc.txt

wait

#remove temp folder/files

rm -r /mnt/md0/User/admin/home/incomingdata/temp

wait

#start sleep script
( "/mnt/md0/User/admin/home/filebot-portable/martinsleep.sh" )


calls the second script (which waits set time and recalls the first script)



#!/bin/bash

sleep 60
wait
( "/mnt/md0/User/admin/home/filebot-portable/martinsamc.sh" )


and then i exit vssh using




  • ctrl-z

  • bg

  • disown


this method is working the script is continuing to run in the background with vssh closed down



i do plan on changing the sleep time to 30mins my worry is that this is just opening tonnes of scripts and will eventually eat resources



Is there a better way of me achieving this?










share|improve this question









New contributor




Martin Robertson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












ive written a couple a couple of scripts. are they going to work indefinatly and will them eventually overload the CPU?



firstly this is on a local nas that for some reason the manufacturer does not give root access or su i have an admin account so i cant just call the script with cron



first script



#!/bin/bash
#connect to server download files

rsync -ae "ssh -p 10045 -T -o Compression=no -x" --progress appbox@filebot.witzend007.appboxes.co:/APPBOX_DATA/apps/rutorrent.witzend007.appboxes.co/torrents/completed/toNAS /mnt/md0/User/admin/home/incomingdata/ --delete

wait

#copy files to temp folder
cp -r /mnt/md0/User/admin/home/incomingdata/toNAS /mnt/md0/User/admin/home/incomingdata/temp

wait

#Start Filebot and organise and rename files to plex library
~/filebot-portable/filebot.sh -script fn:amc --output "/mnt/md0/public/Media" --action move -non-strict "/mnt/md0/User/admin/home/incomingdata/temp" --log-file amc.log --def excludeList=amc.txt

wait

#remove temp folder/files

rm -r /mnt/md0/User/admin/home/incomingdata/temp

wait

#start sleep script
( "/mnt/md0/User/admin/home/filebot-portable/martinsleep.sh" )


calls the second script (which waits set time and recalls the first script)



#!/bin/bash

sleep 60
wait
( "/mnt/md0/User/admin/home/filebot-portable/martinsamc.sh" )


and then i exit vssh using




  • ctrl-z

  • bg

  • disown


this method is working the script is continuing to run in the background with vssh closed down



i do plan on changing the sleep time to 30mins my worry is that this is just opening tonnes of scripts and will eventually eat resources



Is there a better way of me achieving this?







linux bash






share|improve this question









New contributor




Martin Robertson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




Martin Robertson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 3 mins ago









Rui F Ribeiro

39.5k1479132




39.5k1479132






New contributor




Martin Robertson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 2 hours ago









Martin RobertsonMartin Robertson

11




11




New contributor




Martin Robertson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Martin Robertson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Martin Robertson is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 1





    What do you think the wait command does? It's currently a no-op because there's nothing to wait for.

    – roaima
    2 hours ago











  • well some of the commands take a while to complete and i thought wait allows the last command to complete before doing the next command

    – Martin Robertson
    2 hours ago






  • 1





    Each command completes before the script progresses to the next item

    – roaima
    2 hours ago











  • lol i did say i was a n00b i must of misunderstood it somewhere my worry is that my second command would start before the rsync had completed and started moving around half downloaded data. thanks

    – Martin Robertson
    2 hours ago














  • 1





    What do you think the wait command does? It's currently a no-op because there's nothing to wait for.

    – roaima
    2 hours ago











  • well some of the commands take a while to complete and i thought wait allows the last command to complete before doing the next command

    – Martin Robertson
    2 hours ago






  • 1





    Each command completes before the script progresses to the next item

    – roaima
    2 hours ago











  • lol i did say i was a n00b i must of misunderstood it somewhere my worry is that my second command would start before the rsync had completed and started moving around half downloaded data. thanks

    – Martin Robertson
    2 hours ago








1




1





What do you think the wait command does? It's currently a no-op because there's nothing to wait for.

– roaima
2 hours ago





What do you think the wait command does? It's currently a no-op because there's nothing to wait for.

– roaima
2 hours ago













well some of the commands take a while to complete and i thought wait allows the last command to complete before doing the next command

– Martin Robertson
2 hours ago





well some of the commands take a while to complete and i thought wait allows the last command to complete before doing the next command

– Martin Robertson
2 hours ago




1




1





Each command completes before the script progresses to the next item

– roaima
2 hours ago





Each command completes before the script progresses to the next item

– roaima
2 hours ago













lol i did say i was a n00b i must of misunderstood it somewhere my worry is that my second command would start before the rsync had completed and started moving around half downloaded data. thanks

– Martin Robertson
2 hours ago





lol i did say i was a n00b i must of misunderstood it somewhere my worry is that my second command would start before the rsync had completed and started moving around half downloaded data. thanks

– Martin Robertson
2 hours ago










1 Answer
1






active

oldest

votes


















0














Your scripts keep calling each other, so eventually you'll run out of stack space or memory (but probably not for many years).



As better coding, you should consider using a single script that pauses for a minute before looping:



#!/bin/bash
incoming=/mnt/md0/User/admin/home/incomingdata

while :
do
# connect to server download files
rsync -ae "ssh -p 10045 -T -o Compression=no -x" --progress --delete appbox@filebot.witzend007.appboxes.co:/APPBOX_DATA/apps/rutorrent.witzend007.appboxes.co/torrents/completed/toNAS "$incoming/"

# copy files to temp folder
cp -r "$incoming/toNAS/." "$incoming/temp"

# Start Filebot and organise and rename files to plex library
~/filebot-portable/filebot.sh -script fn:amc --output "/mnt/md0/public/Media" --action move -non-strict "$incoming/temp" --log-file amc.log --def excludeList=amc.txt

# remove temp folder/files
rm -r "$incoming/temp"

# Wait 60 seconds
sleep 60
done





share|improve this answer
























  • thanks for the update i can see now how easy youve made this look. i had seen this method but didnt know how to write it. i couldnt see how it restarts the script so wasnt sure if it would work or not. thanks

    – Martin Robertson
    2 hours ago











  • @MartinRobertson you don't need to restart the script. You start this one off and it loops forever (the while : is a lazy shorthand for while true).

    – roaima
    1 hour ago











  • Out of interest, what make is your NAS that doesn't permit shell access? I've got QNAPs around all of our offices globally and they do allow SSH access to crontab, etc.

    – roaima
    1 hour ago













  • its a tnas terramaster wish i hadnt bothered its been one thing after the other. i have ssh access but only user admin cant sudo, su or access cron cant actually do alot with it.

    – Martin Robertson
    56 mins ago











  • btw thank you after viewing my process with ps auxf i could see my script was just one long line after another. yours works so much better so thanks again.

    – Martin Robertson
    54 mins ago











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});






Martin Robertson is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f495187%2fscript-calling-another-script%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














Your scripts keep calling each other, so eventually you'll run out of stack space or memory (but probably not for many years).



As better coding, you should consider using a single script that pauses for a minute before looping:



#!/bin/bash
incoming=/mnt/md0/User/admin/home/incomingdata

while :
do
# connect to server download files
rsync -ae "ssh -p 10045 -T -o Compression=no -x" --progress --delete appbox@filebot.witzend007.appboxes.co:/APPBOX_DATA/apps/rutorrent.witzend007.appboxes.co/torrents/completed/toNAS "$incoming/"

# copy files to temp folder
cp -r "$incoming/toNAS/." "$incoming/temp"

# Start Filebot and organise and rename files to plex library
~/filebot-portable/filebot.sh -script fn:amc --output "/mnt/md0/public/Media" --action move -non-strict "$incoming/temp" --log-file amc.log --def excludeList=amc.txt

# remove temp folder/files
rm -r "$incoming/temp"

# Wait 60 seconds
sleep 60
done





share|improve this answer
























  • thanks for the update i can see now how easy youve made this look. i had seen this method but didnt know how to write it. i couldnt see how it restarts the script so wasnt sure if it would work or not. thanks

    – Martin Robertson
    2 hours ago











  • @MartinRobertson you don't need to restart the script. You start this one off and it loops forever (the while : is a lazy shorthand for while true).

    – roaima
    1 hour ago











  • Out of interest, what make is your NAS that doesn't permit shell access? I've got QNAPs around all of our offices globally and they do allow SSH access to crontab, etc.

    – roaima
    1 hour ago













  • its a tnas terramaster wish i hadnt bothered its been one thing after the other. i have ssh access but only user admin cant sudo, su or access cron cant actually do alot with it.

    – Martin Robertson
    56 mins ago











  • btw thank you after viewing my process with ps auxf i could see my script was just one long line after another. yours works so much better so thanks again.

    – Martin Robertson
    54 mins ago
















0














Your scripts keep calling each other, so eventually you'll run out of stack space or memory (but probably not for many years).



As better coding, you should consider using a single script that pauses for a minute before looping:



#!/bin/bash
incoming=/mnt/md0/User/admin/home/incomingdata

while :
do
# connect to server download files
rsync -ae "ssh -p 10045 -T -o Compression=no -x" --progress --delete appbox@filebot.witzend007.appboxes.co:/APPBOX_DATA/apps/rutorrent.witzend007.appboxes.co/torrents/completed/toNAS "$incoming/"

# copy files to temp folder
cp -r "$incoming/toNAS/." "$incoming/temp"

# Start Filebot and organise and rename files to plex library
~/filebot-portable/filebot.sh -script fn:amc --output "/mnt/md0/public/Media" --action move -non-strict "$incoming/temp" --log-file amc.log --def excludeList=amc.txt

# remove temp folder/files
rm -r "$incoming/temp"

# Wait 60 seconds
sleep 60
done





share|improve this answer
























  • thanks for the update i can see now how easy youve made this look. i had seen this method but didnt know how to write it. i couldnt see how it restarts the script so wasnt sure if it would work or not. thanks

    – Martin Robertson
    2 hours ago











  • @MartinRobertson you don't need to restart the script. You start this one off and it loops forever (the while : is a lazy shorthand for while true).

    – roaima
    1 hour ago











  • Out of interest, what make is your NAS that doesn't permit shell access? I've got QNAPs around all of our offices globally and they do allow SSH access to crontab, etc.

    – roaima
    1 hour ago













  • its a tnas terramaster wish i hadnt bothered its been one thing after the other. i have ssh access but only user admin cant sudo, su or access cron cant actually do alot with it.

    – Martin Robertson
    56 mins ago











  • btw thank you after viewing my process with ps auxf i could see my script was just one long line after another. yours works so much better so thanks again.

    – Martin Robertson
    54 mins ago














0












0








0







Your scripts keep calling each other, so eventually you'll run out of stack space or memory (but probably not for many years).



As better coding, you should consider using a single script that pauses for a minute before looping:



#!/bin/bash
incoming=/mnt/md0/User/admin/home/incomingdata

while :
do
# connect to server download files
rsync -ae "ssh -p 10045 -T -o Compression=no -x" --progress --delete appbox@filebot.witzend007.appboxes.co:/APPBOX_DATA/apps/rutorrent.witzend007.appboxes.co/torrents/completed/toNAS "$incoming/"

# copy files to temp folder
cp -r "$incoming/toNAS/." "$incoming/temp"

# Start Filebot and organise and rename files to plex library
~/filebot-portable/filebot.sh -script fn:amc --output "/mnt/md0/public/Media" --action move -non-strict "$incoming/temp" --log-file amc.log --def excludeList=amc.txt

# remove temp folder/files
rm -r "$incoming/temp"

# Wait 60 seconds
sleep 60
done





share|improve this answer













Your scripts keep calling each other, so eventually you'll run out of stack space or memory (but probably not for many years).



As better coding, you should consider using a single script that pauses for a minute before looping:



#!/bin/bash
incoming=/mnt/md0/User/admin/home/incomingdata

while :
do
# connect to server download files
rsync -ae "ssh -p 10045 -T -o Compression=no -x" --progress --delete appbox@filebot.witzend007.appboxes.co:/APPBOX_DATA/apps/rutorrent.witzend007.appboxes.co/torrents/completed/toNAS "$incoming/"

# copy files to temp folder
cp -r "$incoming/toNAS/." "$incoming/temp"

# Start Filebot and organise and rename files to plex library
~/filebot-portable/filebot.sh -script fn:amc --output "/mnt/md0/public/Media" --action move -non-strict "$incoming/temp" --log-file amc.log --def excludeList=amc.txt

# remove temp folder/files
rm -r "$incoming/temp"

# Wait 60 seconds
sleep 60
done






share|improve this answer












share|improve this answer



share|improve this answer










answered 2 hours ago









roaimaroaima

43.4k553116




43.4k553116













  • thanks for the update i can see now how easy youve made this look. i had seen this method but didnt know how to write it. i couldnt see how it restarts the script so wasnt sure if it would work or not. thanks

    – Martin Robertson
    2 hours ago











  • @MartinRobertson you don't need to restart the script. You start this one off and it loops forever (the while : is a lazy shorthand for while true).

    – roaima
    1 hour ago











  • Out of interest, what make is your NAS that doesn't permit shell access? I've got QNAPs around all of our offices globally and they do allow SSH access to crontab, etc.

    – roaima
    1 hour ago













  • its a tnas terramaster wish i hadnt bothered its been one thing after the other. i have ssh access but only user admin cant sudo, su or access cron cant actually do alot with it.

    – Martin Robertson
    56 mins ago











  • btw thank you after viewing my process with ps auxf i could see my script was just one long line after another. yours works so much better so thanks again.

    – Martin Robertson
    54 mins ago



















  • thanks for the update i can see now how easy youve made this look. i had seen this method but didnt know how to write it. i couldnt see how it restarts the script so wasnt sure if it would work or not. thanks

    – Martin Robertson
    2 hours ago











  • @MartinRobertson you don't need to restart the script. You start this one off and it loops forever (the while : is a lazy shorthand for while true).

    – roaima
    1 hour ago











  • Out of interest, what make is your NAS that doesn't permit shell access? I've got QNAPs around all of our offices globally and they do allow SSH access to crontab, etc.

    – roaima
    1 hour ago













  • its a tnas terramaster wish i hadnt bothered its been one thing after the other. i have ssh access but only user admin cant sudo, su or access cron cant actually do alot with it.

    – Martin Robertson
    56 mins ago











  • btw thank you after viewing my process with ps auxf i could see my script was just one long line after another. yours works so much better so thanks again.

    – Martin Robertson
    54 mins ago

















thanks for the update i can see now how easy youve made this look. i had seen this method but didnt know how to write it. i couldnt see how it restarts the script so wasnt sure if it would work or not. thanks

– Martin Robertson
2 hours ago





thanks for the update i can see now how easy youve made this look. i had seen this method but didnt know how to write it. i couldnt see how it restarts the script so wasnt sure if it would work or not. thanks

– Martin Robertson
2 hours ago













@MartinRobertson you don't need to restart the script. You start this one off and it loops forever (the while : is a lazy shorthand for while true).

– roaima
1 hour ago





@MartinRobertson you don't need to restart the script. You start this one off and it loops forever (the while : is a lazy shorthand for while true).

– roaima
1 hour ago













Out of interest, what make is your NAS that doesn't permit shell access? I've got QNAPs around all of our offices globally and they do allow SSH access to crontab, etc.

– roaima
1 hour ago







Out of interest, what make is your NAS that doesn't permit shell access? I've got QNAPs around all of our offices globally and they do allow SSH access to crontab, etc.

– roaima
1 hour ago















its a tnas terramaster wish i hadnt bothered its been one thing after the other. i have ssh access but only user admin cant sudo, su or access cron cant actually do alot with it.

– Martin Robertson
56 mins ago





its a tnas terramaster wish i hadnt bothered its been one thing after the other. i have ssh access but only user admin cant sudo, su or access cron cant actually do alot with it.

– Martin Robertson
56 mins ago













btw thank you after viewing my process with ps auxf i could see my script was just one long line after another. yours works so much better so thanks again.

– Martin Robertson
54 mins ago





btw thank you after viewing my process with ps auxf i could see my script was just one long line after another. yours works so much better so thanks again.

– Martin Robertson
54 mins ago










Martin Robertson is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















Martin Robertson is a new contributor. Be nice, and check out our Code of Conduct.













Martin Robertson is a new contributor. Be nice, and check out our Code of Conduct.












Martin Robertson is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f495187%2fscript-calling-another-script%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

宮崎県

濃尾地震

シテ島