Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Dev Shell

    Scheduled Pinned Locked Moved Development
    6 Posts 4 Posters 1.8k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • N
      NOYB
      last edited by

      After running playback gitsync, attempting to run it again dev shell exits back to the console menu instead.

      Is this a known issue?  If not what might cause that?

      
      Fatal error: Cannot redeclare post_cvssync_commands() (previously declared in /usr/local/sbin/pfSsh.php(335) : eval()'d code:429) in /usr/local/sbin/pfSsh.php(335) : eval()'d code on line 466
      
      Call Stack:
          0.0013     111956   1\. {main}() /usr/local/sbin/pfSsh.php:0
         82.6440     343496   2\. playback_file() /usr/local/sbin/pfSsh.php:221
         82.6440     359972   3\. playback_text() /usr/local/sbin/pfSsh.php:340
      
      
      1 Reply Last reply Reply Quote 0
      • P
        phil.davis
        last edited by

        I just always exit back to the menu after gitsync, then select option 12 again when it is time to "playback gitsync" again.

        As the Greek philosopher Isosceles used to say, "There are 3 sides to every triangle."
        If I helped you, then help someone else - buy someone a gift from the INF catalog http://secure.inf.org/gifts/usd/

        1 Reply Last reply Reply Quote 0
        • N
          NOYB
          last edited by

          Yeah I realize that's the typical process to do.  But if you try to run again does it work or fail and exit back to the console menu?  Wondering if it's just me.

          The reason I'd like to be able to run multiple times without exiting is because it would be handy to use the command recall during testing.

          1 Reply Last reply Reply Quote 0
          • H
            heper
            last edited by

            everyone gets that error.

            the only way to avoid the error is to exit dev shell and go into it again

            1 Reply Last reply Reply Quote 0
            • N
              NOYB
              last edited by

              Bummer!

              1 Reply Last reply Reply Quote 0
              • D
                doktornotor Banned
                last edited by

                I think it used to auto-exit for a reason. The relevant stuff appears to be in /etc/phpshellsessions/gitsync in case someone's bored.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post
                Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.