# Pbs\_release\_nodes: No jobid given

**URL:** <https://community.openpbs.org/t/pbs-release-nodes-no-jobid-given/1686>\
**Category:** Developers\
**Created:** [July 2, 2019, 5:06am UTC](https://community.openpbs.org/t/pbs-release-nodes-no-jobid-given/1686 "2019-07-02T05:06:58Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![scc](https://yyz2.discourse-cdn.com/flex030/user_avatar/community.openpbs.org/scc/32/234_2.png) [@scc](https://community.openpbs.org/u/scc)\
**Post date:** [July 3, 2019, 5:47pm UTC](https://community.openpbs.org/t/pbs-release-nodes-no-jobid-given/1686/6 "2019-07-03T17:47:26Z")

</div>

Setting flatuid=true is one way to allow this, but it does introduce a security situation as now any user who can connect a system to the network and control the user name space on that system can submit a job as any other user. Everything I said in my post at “[Where to submit a job instead of pbs server](http://community.openpbs.org/t/where-to-submit-a-job-instead-of-pbs-server/513/10)” would also apply here, since the server does the same check of the remote user’s authorization to submit a job (as discussed in that post) as to act on an existing job (such as releasing nodes from it).

---

_[View the full topic](https://community.openpbs.org/t/pbs-release-nodes-no-jobid-given/1686)._