{"action":"created","issue":{"url":"https://api.github.com/repos/grke/burp/issues/298","labels_url":"https://api.github.com/repos/grke/burp/issues/298/labels{/name}","comments_url":"https://api.github.com/repos/grke/burp/issues/298/comments","events_url":"https://api.github.com/repos/grke/burp/issues/298/events","html_url":"https://github.com/grke/burp/issues/298","id":89530242,"number":298,"title":"In 2.0.20 starting `burp -a s` doesnt work","user":{"login":"laapsaap","id":2487212,"avatar_url":"https://avatars.githubusercontent.com/u/2487212?v=3","gravatar_id":"","url":"https://api.github.com/users/laapsaap","html_url":"https://github.com/laapsaap","followers_url":"https://api.github.com/users/laapsaap/followers","following_url":"https://api.github.com/users/laapsaap/following{/other_user}","gists_url":"https://api.github.com/users/laapsaap/gists{/gist_id}","starred_url":"https://api.github.com/users/laapsaap/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/laapsaap/subscriptions","organizations_url":"https://api.github.com/users/laapsaap/orgs","repos_url":"https://api.github.com/users/laapsaap/repos","events_url":"https://api.github.com/users/laapsaap/events{/privacy}","received_events_url":"https://api.github.com/users/laapsaap/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-06-19T10:37:51Z","updated_at":"2015-06-19T14:21:13Z","closed_at":null,"body":"I would imagine in 2.0.20 I can also start `burp -a s` on the server to see status of all the clients like in burp 1.\r\n\r\nBut I am getting this error;\r\n```\r\n2015-06-19 12:34:18: burp[22888] Could not get lockfile.              \r\n2015-06-19 12:34:18: burp[22888] Another process is probably running, \r\n```\r\n\r\nIt wants to run as a daemon but I just want it to connect to the status port."},"comment":{"url":"https://api.github.com/repos/grke/burp/issues/comments/113529602","html_url":"https://github.com/grke/burp/issues/298#issuecomment-113529602","issue_url":"https://api.github.com/repos/grke/burp/issues/298","id":113529602,"user":{"login":"laapsaap","id":2487212,"avatar_url":"https://avatars.githubusercontent.com/u/2487212?v=3","gravatar_id":"","url":"https://api.github.com/users/laapsaap","html_url":"https://github.com/laapsaap","followers_url":"https://api.github.com/users/laapsaap/followers","following_url":"https://api.github.com/users/laapsaap/following{/other_user}","gists_url":"https://api.github.com/users/laapsaap/gists{/gist_id}","starred_url":"https://api.github.com/users/laapsaap/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/laapsaap/subscriptions","organizations_url":"https://api.github.com/users/laapsaap/orgs","repos_url":"https://api.github.com/users/laapsaap/repos","events_url":"https://api.github.com/users/laapsaap/events{/privacy}","received_events_url":"https://api.github.com/users/laapsaap/received_events","type":"User","site_admin":false},"created_at":"2015-06-19T14:21:13Z","updated_at":"2015-06-19T14:21:13Z","body":"Yes I did, but it was a bit confusing.\r\nI mean I understand that from a client, its a nice feature to be able to see his own backup status.  But from the server I cant imagine not being able to burp -a s to see status for all my clients.\r\n\r\n```\r\nOnce the burp server is running, the ncurses status monitor client can be run\r\nwith a command like this:\r\n\r\nburp -a s\r\n```\r\n\r\nIts not clear whether this is possible on server and/or on the client."}}